Kalliguddi, Hema hem...@ti.com writes:
http://focus.ti.com/pdfs/wtbu/SWPU223D_Final_EPDF_06_07_2010.pdf
[HK] The errata is applicable to OMAP3430 only. But this sequence
applicable for omap4 as well. So for submitting the changes we need to
have the HWMOD api to be changed to enaforce the
I wanted to close on the introduction of two new
OMAP device APIs
omap_device_enable_wakeup ()
omap_device_disable_wakeup() in
omap_device layer.
What's the relationship between these
and the sysfs attribute which manages
the per-device wakeup enable?
Should there be driver model
Kevin,
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Friday, June 18, 2010 8:29 PM
To: Kalliguddi, Hema
Cc: Cousson, Benoit; Basak, Partha; p...@pwsan.com; Nayak,
Rajendra; linux-omap@vger.kernel.org
Subject: Re: On the APIs for Enabling and Disabling
Kevin,
Replying on top of latest chin.
Thanks,
Hema
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Thursday, June 24, 2010 2:01 AM
To: Basak, Partha
Cc: Kalliguddi, Hema; Cousson, Benoit; p...@pwsan.com; Nayak,
Rajendra; linux-omap@vger.kernel.org
Kevin,
Thanks
Partha
-Original Message-
From: Kalliguddi, Hema
Sent: Thursday, June 24, 2010 8:25 PM
To: Kevin Hilman; Basak, Partha
Cc: Cousson, Benoit; p...@pwsan.com; Nayak, Rajendra; linux-
o...@vger.kernel.org; Gadiyar, Anand; Kamat, Nishant
Subject: RE: On the APIs for
Basak, Partha p-bas...@ti.com writes:
Benoit/Kevin,
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Friday, June 18, 2010 8:29 PM
To: Kalliguddi, Hema
Cc: Cousson, Benoit; Basak, Partha; p...@pwsan.com; Nayak, Rajendra;
linux-omap@vger.kernel.org
Benoit/Kevin,
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Friday, June 18, 2010 8:29 PM
To: Kalliguddi, Hema
Cc: Cousson, Benoit; Basak, Partha; p...@pwsan.com; Nayak, Rajendra;
linux-omap@vger.kernel.org
Subject: Re: On the APIs for Enabling
Hi Benoit,
I have 2 cases in usb for the need of separate API for setting the auto idle
bit.
1. Below the link for omap3430TRM. Please refer 24.1.5.4.2 and 24.1.5.4.3 there
is note not to set smart
idle and autoidle bit simultaneously. Suggestion is to set the auto idle 0
before setting smart
Kalliguddi, Hema hem...@ti.com writes:
Hi Benoit,
I have 2 cases in usb for the need of separate API for setting the auto idle
bit.
1. Below the link for omap3430TRM. Please refer 24.1.5.4.2 and 24.1.5.4.3
there is note not to set smart
idle and autoidle bit simultaneously. Suggestion
Hi Hema,
From: linux-omap-ow...@vger.kernel.org
Kevin,
There is no errata in the USB which needs the Enable/Disable
wakeup to be done
Seperately. If it can be handled with omap_devie_enable/idle
Apis it is sufficient.
But there is a need of setting the Auto idle bit seperately as
for the
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Basak, Partha
Sent: Wednesday, June 16, 2010 8:10 PM
To: p...@pwsan.com
Cc: khil...@deeprootsystems.com; Kalliguddi, Hema; Nayak, Rajendra; linux-
o...@vger.kernel.org
Basak, Partha p-bas...@ti.com writes:
I wanted to close on the introduction of two new OMAP device APIs
omap_device_enable_wakeup () omap_device_disable_wakeup() in
omap_device layer.
These APIs are potentially needed by the USB driver (via function
pointers) to work around some USB
Kevin,
Kevin,
There is no errata in the USB which needs the Enable/Disable wakeup to be done
Seperately. If it can be handled with omap_devie_enable/idle Apis it is
sufficient.
But there is a need of setting the Auto idle bit seperately as for the USBOTG
there is a need to set the Autoidle
13 matches
Mail list logo
