Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

Hi, Оригинално писмо От: Pavel Machek Относно: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround До: Pali Rohár Изпратено на: Събота, 2013, Март 30 20:36:54 EET Hi! +u32 rx51_secure_dispatcher(u32 idx, u32 flag, u32 nargs, u32 arg1, u32 arg2, +

Re: [PATCH] OMAP3 ROM Random Number Generator support

Hi Pali, Yep, the code looks almost identical, I guess with some tweaks all SMC code from that patch could be removed and instead used the one from SMC PPA API. What I don't get, is why one needs to disable/enable fiqs/irqs: +static int call_sec_rom(u32 appl_id, u32 proc_id, u32 flag, ...)

Re: [PATCH] OMAP3 ROM Random Number Generator support

It could be that I am misreading something, but RX51 is OMAP3. Regards, Ivo Оригинално писмо От: Tony Lindgren Относно: Re: [PATCH] OMAP3 ROM Random Number Generator support До: Ивайло Димитров Изпратено на: Понеделник, 2013, Април 1 19:59:50 EEST * Ивайло

Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

Tony, Who do you expect to make that code merge? Do you expect us to mechanically merge RX51 PPA API patch with the existing generic OMAP PPA API code putting #ifdefs all over the place? Not that it is impossible, but the only real piece of HW I have here is n900, so I just can't be sure the

Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

Оригинално писмо От: Aaro Koskinen Относно: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround До: Ивайло Димитров Изпратено на: Събота, 2013, Март 2 01:51:39 EET On Fri, Mar 01, 2013 at 12:09:12PM +0200, Ивайло Димитров wrote: Unfortunately

Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

They look similar, but they are not equivalent :). The first major difference is here (code taken from omap-smc.S) ENTRY(omap_smc2) stmfd sp!, {r4-r12, lr} mov r3, r2 mov r2, r1 mov r1, #0x0@ Process ID mov r6,

Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

Unfortunately it is necessary, on RX-51 PPA/NOLO leaves IBE bit unset. Оригинално писмо От: Peter De Schrijver Относно: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround До: Pali Rohár Изпратено на: Петък, 2013, Март 1 11:43:14 EET On Thu, Feb 28, 2013

Re: [PATCH v2 1/2] ARM: OMAP: Add secure function omap_smc3() which calling instruction smc #1

Оригинално писмо От: Dave Martin Относно: Re: [PATCH v2 1/2] ARM: OMAP: Add secure function omap_smc3() which calling instruction smc #1 До: Pali Rohár Изпратено на: Сряда, 2013, Юли 10 20:45:26 EEST On Wed, Jul 10, 2013 at 02:59:04PM +0200, Pali Rohár wrote:

Re: OMAPFB: CMA allocation failures

Оригинално писмо От: Tomi Valkeinen Относно: Re: OMAPFB: CMA allocation failures До: Ивайло Димитров Изпратено на: Сряда, 2013, Октомври 30 14:19:32 EET I really dislike the idea of adding the omap vram allocator back. Then again, if the CMA doesn't work

Re: OMAPFB: CMA allocation failures

Hi Tomi, I think we should somehow find out what the pages are that cannot be migrated, and where they come from. So there are quot;anonymous pages without mappingquot; with page_count(page) != 1. I have to say I don't know what that means =). I need to find some time to study the mm.

Re: [PATCH v2 2/3] bq2415x_charger: Use power_supply notifier for automode

Оригинално писмо От: Pavel Machek Относно: Re: [PATCH v2 2/3] bq2415x_charger: Use power_supply notifier for automode До: Pali Rohár Изпратено на: Понеделник, 2013, Ноември 25 17:18:39 EET On Mon 2013-11-25 15:10:00, Pali Rohár wrote: On Monday 25 November

Re: [PATCH v2 2/3] bq2415x_charger: Use power_supply notifier for automode

Оригинално писмо От: Sebastian Reichel Относно: Re: [PATCH v2 2/3] bq2415x_charger: Use power_supply notifier for automode До: Ивайло Димитров Изпратено на: Понеделник, 2013, Ноември 25 19:14:21 EET On Mon, Nov 25, 2013 at 07:01:54PM +0200, Ивайло Димитров wrote

Re: [patch] Staging: tidspbridge: make mmap root-only so it is not a security problem

I can (and will) test whatever patches is needed. Also will try to get rid of uuid helpers and send a patch today. On Sun Dec  1 11:41:39 2013 Pali Rohár pali.ro...@gmail.com wrote: On Saturday 30 November 2013 23:58:23 Pavel Machek wrote: On Sat 2013-11-30 14:05:53, Greg KH wrote: On

OMAPFB: CMA allocation failures

Hi Tomi, patch http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/131269.html modifies omapfb driver to use DMA API to allocate framebuffer memory instead of preallocating VRAM. With this patch I see a lot of: Jan 1 06:33:27 Nokia-N900 kernel: [ 2054.879577] cma:

Re: OMAPFB: CMA allocation failures

Hi Оригинално писмо От: Tomi Valkeinen Относно: Re: OMAPFB: CMA allocation failures До: Ивайло Димитров Изпратено на: Понеделник, 2013, Октомври 14 09:04:35 EEST Hi, On 12/10/13 17:43, Ивайло Димитров wrote: Hi Tomi, patch http

Re: OMAPFB: CMA allocation failures

Hi, Оригинално писмо От: Minchan Kim Относно: Re: OMAPFB: CMA allocation failures До: Ивайло Димитров Изпратено на: Понеделник, 2013, Октомври 28 09:37:48 EET Hello, On Tue, Oct 15, 2013 at 09:49:51AM +0300, Ивайло Димитров wrote: Hi

Re: OMAPFB: CMA allocation failures

Hi, I wonder if there is any progress on the issue? Do you need me to send more data? Or should I raise the issue with the CMA maintainer? Regards, Ivo Оригинално писмо От: Ивайло Димитров Относно: Re: OMAPFB: CMA allocation failures До: Tomi Valkeinen Изпратено на

Re: [PATCH v2 01/16] wl1251: fix scan behaviour while not associated

Оригинално писмо От: Pali Rohár Относно: Re: [PATCH v2 01/16] wl1251: fix scan behaviour while not associated До: Kalle Valo , Pavel Machek Изпратено на: Вторник, 2013, Декември 10 19:08:44 EET On Tuesday 10 December 2013 16:41:04 Kalle Valo wrote: Pavel Machek

Re: [PATCH v3 1/2] ARM: OMAP: Add secure function omap_smc3() which calling instruction smc #1

Оригинално писмо От: Dave Martin Относно: Re: [PATCH v3 1/2] ARM: OMAP: Add secure function omap_smc3() which calling instruction smc #1 До: Pali Rohár Изпратено на: Понеделник, 2013, Август 5 16:29:44 EEST On Sun, Aug 04, 2013 at 10:45:00AM +0200, Pali Rohár

Re: [PATCH] OMAP3 ROM Random Number Generator support

It could be that I am misreading something, but RX51 is OMAP3. Regards, Ivo > Оригинално писмо >От: Tony Lindgren >Относно: Re: [PATCH] OMAP3 ROM Random Number Generator support >До: Ивайло Димитров >Изпратено на: Понеделник, 2013, Април

Re: [PATCH v3 1/2] ARM: OMAP: Add secure function omap_smc3() which calling instruction smc #1

> Оригинално писмо >От: Dave Martin >Относно: Re: [PATCH v3 1/2] ARM: OMAP: Add secure function omap_smc3() which calling instruction smc #1 >До: Pali Rohár >Изпратено на: Понеделник, 2013, Август 5 16:29:44 EEST > > >On Sun, Aug 04, 2013 at 10:45:00AM +0200, Pali

Re: OMAPFB: CMA allocation failures

> Оригинално писмо >От: Tomi Valkeinen >Относно: Re: OMAPFB: CMA allocation failures >До: Ивайло Димитров >Изпратено на: Сряда, 2013, Октомври 30 14:19:32 EET > >I really dislike the idea of adding the omap vram allocator back. Then >again,

Re: OMAPFB: CMA allocation failures

Hi Tomi, >I think we should somehow find out what the pages are that cannot be >migrated, and where they come from. > >So there are anonymous pages without mapping with >page_count(page) != >1. I have to say I don't know what that means =). I need to find some >time to study the mm. I

Re: [PATCH v2 2/3] bq2415x_charger: Use power_supply notifier for automode

> Оригинално писмо >От: Pavel Machek >Относно: Re: [PATCH v2 2/3] bq2415x_charger: Use power_supply notifier for automode >До: Pali Rohár >Изпратено на: Понеделник, 2013, Ноември 25 17:18:39 EET > > >On Mon 2013-11-25 15:10:00, Pali Rohár wrote: >> On Monday 25

Re: [PATCH v2 2/3] bq2415x_charger: Use power_supply notifier for automode

> Оригинално писмо >От: Sebastian Reichel >Относно: Re: [PATCH v2 2/3] bq2415x_charger: Use power_supply notifier for automode >До: Ивайло Димитров >Изпратено на: Понеделник, 2013, Ноември 25 19:14:21 EET > > >On Mon, Nov 25, 2013 at 07:01:54P

Re: [patch] Staging: tidspbridge: make mmap root-only so it is not a security problem

I can (and will) test whatever patches is needed. Also will try to get rid of uuid helpers and send a patch today. On Sun Dec  1 11:41:39 2013 Pali Rohár wrote: > On Saturday 30 November 2013 23:58:23 Pavel Machek wrote: > > On Sat 2013-11-30 14:05:53, Greg KH wrote: > > > On Sat, Nov 30, 2013

Re: OMAPFB: CMA allocation failures

Hi, > Оригинално писмо >От: Minchan Kim >Относно: Re: OMAPFB: CMA allocation failures >До: Ивайло Димитров >Изпратено на: Понеделник, 2013, Октомври 28 09:37:48 EET > > >Hello, > >On Tue, Oct 15, 2013 at 09:49:51AM +0300,

Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

They look similar, but they are not equivalent :). The first major difference is here (code taken from omap-smc.S) > ENTRY(omap_smc2) > stmfd sp!, {r4-r12, lr} > mov r3, r2 > mov r2, r1 > mov r1, #0x0@ Process ID > mov

Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

Unfortunately it is necessary, on RX-51 PPA/NOLO leaves IBE bit unset. > Оригинално писмо >От: Peter De Schrijver >Относно: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround >До: Pali Rohár >Изпратено на: Петък, 2013, Март 1 11:43:14 EET > > >On Thu, Feb

OMAPFB: CMA allocation failures

Hi Tomi, patch http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/131269.html modifies omapfb driver to use DMA API to allocate framebuffer memory instead of preallocating VRAM. With this patch I see a lot of: Jan 1 06:33:27 Nokia-N900 kernel: [ 2054.879577] cma:

Re: OMAPFB: CMA allocation failures

Hi > Оригинално писмо >От: Tomi Valkeinen >Относно: Re: OMAPFB: CMA allocation failures >До: Ивайло Димитров >Изпратено на: Понеделник, 2013, Октомври 14 09:04:35 EEST > > >Hi, > >On 12/10/13 17:43, Ивайло Димитров wrote

Re: OMAPFB: CMA allocation failures

Hi, I wonder if there is any progress on the issue? Do you need me to send more data? Or should I raise the issue with the CMA maintainer? Regards, Ivo > Оригинално писмо >От: Ивайло Димитров >Относно: Re: OMAPFB: CMA allocation failures >До: Tomi Valkeinen

Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

> Оригинално писмо >От: Aaro Koskinen >Относно: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround >До: Ивайло Димитров >Изпратено на: Събота, 2013, Март 2 01:51:39 EET > > >On Fri, Mar 01, 2013 at 12:09:12PM +0200, Ивайло Димитров

Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

Tony, Who do you expect to make that code merge? Do you expect us to mechanically merge RX51 PPA API patch with the existing generic OMAP PPA API code putting #ifdefs all over the place? Not that it is impossible, but the only real piece of HW I have here is n900, so I just can't be sure the

Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround

Hi, > Оригинално писмо >От: Pavel Machek >Относно: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround >До: Pali Rohár >Изпратено на: Събота, 2013, Март 30 20:36:54 EET > > >Hi! > >> +u32 rx51_secure_dispatcher(u32 idx, u32 flag, u32 nargs, u32 arg1, u32

Re: [PATCH] OMAP3 ROM Random Number Generator support

Hi Pali, Yep, the code looks almost identical, I guess with some tweaks all SMC code from that patch could be removed and instead used the one from SMC PPA API. What I don't get, is why one needs to disable/enable fiqs/irqs: +static int call_sec_rom(u32 appl_id, u32 proc_id, u32 flag, ...)

Re: [PATCH v2 01/16] wl1251: fix scan behaviour while not associated

> Оригинално писмо >От: Pali Rohár >Относно: Re: [PATCH v2 01/16] wl1251: fix scan behaviour while not associated >До: Kalle Valo , Pavel Machek >Изпратено на: Вторник, 2013, Декември 10 19:08:44 EET > > >On Tuesday 10 December 2013 16:41:04 Kalle Valo wrote: >>

Re: Nokia N900 - audio TPA6130A2 problems

Hi On Fri Mar 18 12:33:14 2016 Peter Ujfalusi wrote: > > But enabling the pull via DT for the i2c2 works? > No :(. I even migrated the driver to regmap - no gain. Maybe i2c bus is blocked by another device held in reset. The next thing I am going to try is to deassert

Re: Nokia N900 - audio TPA6130A2 problems

Hi On Fri Mar 18 12:33:14 2016 Peter Ujfalusi wrote: > > But enabling the pull via DT for the i2c2 works? > No :(. I even migrated the driver to regmap - no gain. Maybe i2c bus is blocked by another device held in reset. The next thing I am going to try is to deassert reset/power gpios on

Re: [PATCH v2 1/2] ARM: OMAP: Add secure function omap_smc3() which calling instruction smc #1

> Оригинално писмо >От: Dave Martin >Относно: Re: [PATCH v2 1/2] ARM: OMAP: Add secure function omap_smc3() which calling instruction smc #1 >До: Pali Rohár >Изпратено на: Сряда, 2013, Юли 10 20:45:26 EEST > > >On Wed, Jul 10, 2013 at 02:59:04PM +0200, Pali Rohár