* Samuel Ortiz [110701 04:32]:
> Hi Tony,
>
> On Fri, Jul 01, 2011 at 12:35:58AM -0700, Tony Lindgren wrote:
> > Samuel,
> >
> > * gr...@linuxhacker.ru [110614 08:42]:
> > > From: Oleg Drokin
> > >
> > > Very similar to TPS65920
> > > List of differences: http://www.ti.com/litv/pdf/swcu066b
>
Hong,
On Sat, Jul 2, 2011 at 04:45, hong zhang wrote:
> --- On Fri, 7/1/11, Jon Hunter wrote:
>
>> From: Jon Hunter
>> Subject: Re: gpio interrupt is not invoked on Panda board
>> To: "hong zhang"
>> Cc: linux-omap@vger.kernel.org
>> Date: Friday, July 1, 2011, 4:17 PM
>> Hi Henry
>>
>> On 7/1
Add OMAP4460 OPP definitions for voltage and frequencies based on
OMAP4460 ES1.0 DM Operating Condition Addendum Version 0.1
The following exceptions are present:
* Smartreflex support is still on experimental mode: the gains and min
limits are currently pending characterization data. Currently
On Sat, Jul 2, 2011 at 10:07 PM, Paul Walmsley wrote:
> On Sat, 2 Jul 2011, Govindraj.R wrote:
>
>> +int omap_hmwod_pad_get_wakeup_status(struct omap_hwmod *oh)
> ^
>
> should be "hwmod"
corrected and re-posted both patches.
http://permalink.gmane.org/gmane.linux.ports.arm.omap/60
>-Original Message-
>From: Alan Stern [mailto:st...@rowland.harvard.edu]
>Sent: Saturday, July 02, 2011 12:37 AM
>To: Keshava Munegowda
>Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org; linux-
>ker...@vger.kernel.org; ba...@ti.com; gadi...@ti.com;
>sa...@linux.intel.com; part...@i
Add API to determine IO-PAD wakeup event status for a given
hwmod dynamic_mux pad.
Signed-off-by: Govindraj.R
---
arch/arm/mach-omap2/mux.c| 30 ++
arch/arm/mach-omap2/mux.h| 13 +++
arch/arm/mach-omap2/omap_hwmod.c
Add API to determine IO-PAD wakeup event status for a given
hwmod dynamic_mux pad.
Signed-off-by: Govindraj.R
---
arch/arm/mach-omap2/mux.c| 30 ++
arch/arm/mach-omap2/mux.h| 13 +++
arch/arm/mach-omap2/omap_hwmod.c
Add API to enable IO pad wakeup capability based on mux dynamic pad and
wake_up enable flag available from hwmod_mux initialization.
Use the wakeup_enable flag and enable wakeup capability
for the given pads. Wakeup capability will be enabled/disabled
during hwmod idle transition based on whether
On Fri, 1 Jul 2011 at 10:52:28 Jarkko Nikula wrote:
> There is no need to have separate register definitions for OMAP1
> since they are ordered similarly than in OMAP2+ and thus register
> address offsets can be calculated from OMAP2+ register address
> offsets.
Hi Jarkko,
This patch is missing a