Re: [PATCH 3/9] ARM: OMAP2+: PM: Remove bogus fiq_[enable/disable] tuple

2013-03-28 Thread Santosh Shilimkar
On Thursday 28 March 2013 12:32 AM, Santosh Shilimkar wrote: > On Thursday 28 March 2013 12:06 AM, Kevin Hilman wrote: >> Santosh Shilimkar writes: >> >>> On OMAP platform, FIQ is reserved for secure environment only. If at all >>> the FIQ needs to be disabled, it involves going through security >

Re: [PATCH 3/9] ARM: OMAP2+: PM: Remove bogus fiq_[enable/disable] tuple

2013-03-27 Thread Santosh Shilimkar
On Thursday 28 March 2013 12:06 AM, Kevin Hilman wrote: > Santosh Shilimkar writes: > >> On OMAP platform, FIQ is reserved for secure environment only. If at all >> the FIQ needs to be disabled, it involves going through security >> API call. Hence the local_fiq_[enable/disable]() in the OMAP cod

Re: [PATCH 3/9] ARM: OMAP2+: PM: Remove bogus fiq_[enable/disable] tuple

2013-03-27 Thread Kevin Hilman
Santosh Shilimkar writes: > On OMAP platform, FIQ is reserved for secure environment only. If at all > the FIQ needs to be disabled, it involves going through security > API call. Hence the local_fiq_[enable/disable]() in the OMAP code is bogus. > > So just get rid of it. What about GP devices?

[PATCH 3/9] ARM: OMAP2+: PM: Remove bogus fiq_[enable/disable] tuple

2013-02-20 Thread Santosh Shilimkar
On OMAP platform, FIQ is reserved for secure environment only. If at all the FIQ needs to be disabled, it involves going through security API call. Hence the local_fiq_[enable/disable]() in the OMAP code is bogus. So just get rid of it. Signed-off-by: Santosh Shilimkar --- arch/arm/mach-omap2/c