[PATCH/RFC 3/2] OMAP: PM noop: implement context loss count for non-omap_devices

For devices which have not (yet) been converted to use omap_device, implement the context loss counter using the brutal method as originally proposed by Paul Walmsley[1]. The dummy context loss counter is incremented every time it is checked, but only when off-mode is enabled. When off-mode is

RE: [PATCH 1/2] ARM: Thumb-2: Make CONFIG_THUMB2_KERNEL depend on !CPU_V6

-Original Message- From: Dave Martin [mailto:dave.mar...@linaro.org] Sent: Thursday, December 09, 2010 5:30 PM To: linux-arm-ker...@lists.infradead.org Cc: Dave Martin; Santosh Shilimkar; linux-omap@vger.kernel.org Subject: [PATCH 1/2] ARM: Thumb-2: Make CONFIG_THUMB2_KERNEL depend

RE: [PATCH 2/2] ARM: Make CONFIG_FPE_NWFPE depend on !CONFIG_THUMB2_KERNEL

-Original Message- From: Dave Martin [mailto:dave.mar...@linaro.org] Sent: Thursday, December 09, 2010 5:30 PM To: linux-arm-ker...@lists.infradead.org Cc: Dave Martin; Santosh Shilimkar; linux-omap@vger.kernel.org Subject: [PATCH 2/2] ARM: Make CONFIG_FPE_NWFPE depend on

[PATCH 0/7 V2] usb: otg: TWL6030: OMAP4430: musb transceiver driver support for OMAP4

This patch series has the support for TWL6030-usb transceiver driver and changes in the musb driver to make it functional with OMAP4430. OMAP4 musb support UTMI and ULPI transceiver interfaces. In UTMI mode, the transceiver functionality is split between the TWL6030 PMIC chip and OMAP4 embedded

[PATCH 1/7 V2] mfd: TWL6030: USBOTG VBUS event generation on

With TWL6030-usb, VBUS SESS_VLD and SESS_END events are not generated as expected. When these interrupts are enabled, charger VBUS detection interrupt does not get generated. So USBOTG has to be dependent on charger VBUS interrupts. So added one bit for USBOTG and changed the handler to call the

[PATCH 2/7 V2] usb: otg: Adding twl6030-usb transceiver driver for

Adding the twl6030-usb transceiver support for OMAP4 musb driver. OMAP4 supports 2 types of transceiver interface. 1. UTMI: The PHY is embedded within OMAP4. The transceiver functionality is split between the twl6030 PMIC chip and OMAP4430. The VBUS, ID pin sensing and OTG SRP generation part

[PATCH 3/7 V2] usb: otg: Kconfig: Add Kconfig option for TWL6030 transceiver.

Added the TWL6030-usb transceiver option in the Kconfig Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi ba...@ti.com Cc: David Brownell dbrown...@users.sourceforge.net --- drivers/usb/otg/Kconfig | 12 1 file changed, 12 insertions(+) Index: usb/drivers/usb/otg/Kconfig

[PATCH 4/7 V2] mfd: TWL6030: OMAP4: Registering the TWL6030-usb device

Registering the twl6030-usb transceiver device as a child to twl6030 core. Removed the NOP transceiver init call from board file. Populated twl4030_usb_data platform data structure with the function pointers for OMAP4430 internal PHY operation to be used by twl630-usb driver. Signed-off-by:

[PATCH 5/7 V2] usb: musb: TWL6030: Selecting TWL6030_USB transceiver

Selecting the twl6030-usb for OMAP4430SDP and OMAP4PANDA boards and adding OMAP4 internal phy code for compilation Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi ba...@ti.com Cc: Tony Lindgren t...@atomide.com --- arch/arm/mach-omap2/Makefile |6 -- drivers/usb/musb/Kconfig |

[PATCH 6/7 V2] usb: musb: Adding musb support for OMAP4430

OMAP4430 supports UTMI and ULPI types of transceiver interface. In UTMI mode: The PHY is embedded within OMAP4430. The transceiver functionality is split between the twl6030 PMIC chip and OMAP4430. The VBUS, ID pin sensing and OTG SRP generation part is integrated in TWL6030 and UTMI PHY

[PATCH 7/7 V2] arm: OMAP4430: musb: Configure musb to OTG mode

Enabling the musb OTG mode for SDP and PANDA boards. Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi ba...@ti.com Cc: Tony Lindgren t...@atomide.com --- arch/arm/mach-omap2/board-4430sdp.c|2 +- arch/arm/mach-omap2/board-omap4panda.c |2 +- 2 files changed, 2 insertions(+), 2

RE: RFC: hwmod, iclks, auto-idle and autodeps

Hello Partha On Tue, 23 Nov 2010, Basak, Partha wrote: -Original Message- From: Paul Walmsley [mailto:p...@pwsan.com] Sent: Tuesday, November 23, 2010 9:31 AM The rest of the time, if the GPIO driver wants to use idle-mode wakeups (presumably higher wakeup latency, but

Re: [PATCH 0/5] OMAP4: hwmod data fixes and update

On 12/10/2010 1:36 AM, Kevin Hilman wrote: Benoit Coussonb-cous...@ti.com writes: Hi Paul, Here is a small set of OMAP4 hwmod data updates. Re-order properly the data that were a little bit shuffled during the previous merge window. Add the new reset flags introduced in 2.6.37 and that were

<    1   2