[PATCH 2/4] mfd: twl-core: switch over to defines in twl.h

From: Felipe Balbi felipe.ba...@nokia.com use the new definitions on twl header for code consistency. Signed-off-by: Felipe Balbi felipe.ba...@nokia.com --- drivers/mfd/twl-core.c | 21 + 1 files changed, 9 insertions(+), 12 deletions(-) diff --git

[PATCH 4/4] usb: otg: twl4030-usb: switch over to defines in twl.h

From: Felipe Balbi felipe.ba...@nokia.com use the new definitions on twl header for code consistency. Signed-off-by: Felipe Balbi felipe.ba...@nokia.com --- drivers/usb/otg/twl4030-usb.c | 13 + 1 files changed, 9 insertions(+), 4 deletions(-) diff --git

[PATCH 0/4] twl PROTECT_KEY usage cleanup

From: Felipe Balbi felipe.ba...@nokia.com Hi all, the following patches are cleaning up the usage of PROTECT_KEY register. Boot-tested on custom OMAP3 board. Felipe Balbi (4): i2c: twl: add register defines for pm master module mfd: twl-core: switch over to defines in twl.h mfd:

[PATCH 1/4] i2c: twl: add register defines for pm master module

From: Felipe Balbi felipe.ba...@nokia.com Some modules already need to talk to at least PROTECT_KEY register, while at that, add defines to the entire register space. Signed-off-by: Felipe Balbi felipe.ba...@nokia.com --- include/linux/i2c/twl.h | 46

[PATCH 3/4] mfd: twl4030-power: switch over to defines in twl.h

From: Felipe Balbi felipe.ba...@nokia.com use the new definitions on twl header for code consistency. Signed-off-by: Felipe Balbi felipe.ba...@nokia.com --- drivers/mfd/twl4030-power.c | 30 -- 1 files changed, 16 insertions(+), 14 deletions(-) diff --git

RE: [PATCH 2/4] mfd: twl-core: switch over to defines in twl.h

-Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of felipe.ba...@nokia.com Sent: Wednesday, August 18, 2010 11:50 AM To: Samuel Ortiz Cc: linux-ker...@vger.kernel.org; linux-omap@vger.kernel.org; Tony Lindgren; Andrew Morton;

Re: [PATCH v4 1/3] ARM: OMAP: Beagle: revision detection

On Tue, 17 Aug 2010 15:10:35 -0500 Robert Nelson robertcnel...@gmail.com wrote: Do you have any preference if the gpio allocation fails? Right now it'll just halts, we could just return as Cx based board.. Which would be the route the current kernel would take without this patch... I think

OMAP2PLUS dpll rate calculation.

Hello Paul/Kevin, Recently I noticed that the dpll rate calculation code in arch/arm/mach-omap2/clkt_dpll.c is as follows dpll_clk = (long long)dd-clk_ref-rate * dpll_mult; do_div(dpll_clk, dpll_div + 1); But the actual trm for both OMAP3 and OMAP4 (I believe this is true for

RE: [PATCH 2/4] mfd: twl-core: switch over to defines in twl.h

-Original Message- From: Felipe Balbi [mailto:felipe.ba...@nokia.com] Sent: Wednesday, August 18, 2010 12:29 PM To: Gopinath, Thara Cc: Balbi Felipe (Nokia-MS/Helsinki); Samuel Ortiz; linux-ker...@vger.kernel.org; linux- o...@vger.kernel.org; Tony Lindgren; Andrew Morton Subject: Re:

Re: [PATCH 2/4] mfd: twl-core: switch over to defines in twl.h

On Wed, Aug 18, 2010 at 08:32:57AM +0200, ext Gopinath, Thara wrote: R_PROTECT_KEY offset is 0xE where as the new TWL4030_PM_MASTER_PROTECT_KEY is defined as 0xd. I have not checked the trm to see which is correct. But you can use either 0xc0|0x0c or 0xce|0xec, both will work are unlock keys.

RE: [PATCH 2/4] mfd: twl-core: switch over to defines in twl.h

-Original Message- From: Gopinath, Thara Sent: Wednesday, August 18, 2010 12:33 PM To: 'felipe.ba...@nokia.com' Cc: Samuel Ortiz; linux-ker...@vger.kernel.org; linux-omap@vger.kernel.org; Tony Lindgren; Andrew Morton Subject: RE: [PATCH 2/4] mfd: twl-core: switch over to defines in

Re: [PATCH 2/4] mfd: twl-core: switch over to defines in twl.h

Hi, On Wed, Aug 18, 2010 at 09:03:44AM +0200, ext Gopinath, Thara wrote: No I am not talking about the key values. I was talking about the register offset for TWL4030_PM_MASTER_PROTECT_KEY. My question is, is it ok for it to be 0xd or 0xe. Earlier we were using 0xd and in the new

Re: [PATCH 2/4] mfd: twl-core: switch over to defines in twl.h

Hi, On Wed, Aug 18, 2010 at 09:10:22AM +0200, Balbi Felipe (Nokia-MS/Helsinki) wrote: On Wed, Aug 18, 2010 at 09:03:44AM +0200, ext Gopinath, Thara wrote: No I am not talking about the key values. I was talking about the register offset for TWL4030_PM_MASTER_PROTECT_KEY. My question is, is

RE: [PATCH] OMAP:DSS:Add support for Additional color modes supported by OMAP4

Hi Tomi, -Original Message- From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com] Sent: Tuesday, August 17, 2010 4:31 PM To: K, Mythri P Cc: linux-omap@vger.kernel.org Subject: RE: [PATCH] OMAP:DSS:Add support for Additional color modes supported by OMAP4 Hi, On Wed, 2010-08-11 at

RE: [PATCH] OMAP:DSS:Add support for Additional color modes supported by OMAP4

Hi, On Wed, 2010-08-18 at 09:56 +0200, ext K, Mythri P wrote: Hi Tomi, -Original Message- From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com] Sent: Tuesday, August 17, 2010 4:31 PM To: K, Mythri P Cc: linux-omap@vger.kernel.org Subject: RE: [PATCH] OMAP:DSS:Add support for

[PATCH] omap: usb: fix build warning

Fix this and similar build warnings when building with omap_4430sdp_defconfig. CC arch/arm/mach-omap2/board-4430sdp.o In file included from arch/arm/mach-omap2/board-4430sdp.c:36: arch/arm/plat-omap/include/plat/usb.h:109: warning: return type defaults to 'int' Signed-off-by: Anand

[PATCH 00/10] OMAP4: Smartreflex and Voltage layer support

From: thara gopinath th...@ti.com This patch series adds support for OMAP4 support in the smartreflex and voltage layer. The series involves extensions to voltage layer and smartreflex layer for supporting OMAP4. In addition it involves changes to pm debugfs layer to support OMAP4 so that

[PATCH 02/10] OMAP4: OPP framework support

This patch allows the compilation of the generic opp layer for OMAP4 also. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/plat-omap/Makefile |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/arch/arm/plat-omap/Makefile b/arch/arm/plat-omap/Makefile index

[PATCH 01/10] OMAP4: PM debugfs support

This patch extends pm debugfs to support OMAP4 debug entries also. Currently for register dumps only CM1 and PRM modules are added. CM2 is not added as the clockdomain read write APIs assume CM1 base. Once this is fixed CM2 can also be added in the OMAP4 register module table. Signed-off-by:

[PATCH 03/10] OMAP4: Add the new voltage to vsel calculation formula

TWL6030 the power IC used along with OMAP4 in OMAP4 SDPs, blaze boards and panda boards has a different formula from that of TWL4030 for voltage to vsel and vsel to voltage calculation. This patch implements the new formula depending on the PMIC type. Signed-off-by: Thara Gopinath th...@ti.com

[PATCH 04/10] OMAP4: Extend clock data.

This patch extends the OMAP4 clock data to include various x2 clockc nodes as the clock framework skips a *2 whie calculating the dpll locked frequency. Signed-off-by: Thara Gopinath th...@ti.com --- This patch has a checkpatch.pl warning due to the clock data base omap44xx_clks having all the

[PATCH 07/10] OMAP4: Adding dev atrributes to OMAP4 smartreflex hwmod data

This patch adds dev attributes for smartreflex modules in the OMAP4 hwmod database. This patch also updates the smartreflex rev in the smartreflex class data structure in the OMAP4 hwmod database. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 56

[PATCH 10/10] OMAP4: Add opp tables.

This patch adds OPP tables for OMAP4. A new file opp44xx.c has been added to keep the OMAP4 opp tables and the registeration of these tables with the generic opp framework. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/mach-omap2/Makefile |2 +- arch/arm/mach-omap2/opp44xx.h

[PATCH 06/10] OMAP4: hwmod: Add inital data for smartreflex modules.

From: Benoit Cousson b-cous...@ti.com This patch adds the hwmod details to OMAP4 smartreflex modules. Signed-off-by: Benoit Cousson b-cous...@ti.com --- arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 164 1 files changed, 164 insertions(+), 0 deletions(-) diff --git

[PATCH 05/10] OMAP4: Adding voltage driver support

This patch adds voltage driver support for OMAP4. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/mach-omap2/Makefile |2 +- arch/arm/mach-omap2/voltage.c | 246 - arch/arm/plat-omap/include/plat/voltage.h | 20 +++- 3 files

[PATCH 09/10] OMAP4: Enabling smartrefles class 3 driver.

This patch enables smartreflex class3 mode of operation for OMAP4430 SDP board. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/mach-omap2/board-4430sdp.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-omap2/board-4430sdp.c

[PATCH 00/13] OMAP: Basic DVFS framework

From: thara gopinath th...@ti.com This patch series introduces support for support of Dynamic Voltage and Frequency Scaling (DVFS) for OMAP devices. DVFS is a technique that uses the optimal operating frequency and voltage to allow a task to be performed in the required amount of time. OMAP

[PATCH 01/13] OMAP: Introduce a user list for each voltage domain instance in the voltage driver.

This patch introduces a user list of devices associated with each voltage domain instance. The user list is implemented using plist structure with priority node populated with the voltage values. This patch also adds an API which will take in a device and requested voltage as parameters, adds the

[PATCH 02/13] OMAP: Introduce API in the OPP layer to find the opp entry corresponding to a voltage.

This patch adds an API in the opp layer to get the opp table entry corresponding to the voltage passed as the parameter. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/plat-omap/include/plat/opp.h |8 arch/arm/plat-omap/opp.c | 28

[PATCH 03/13] OMAP: Introduce voltage domain information in the hwmod structures

This patch extends the device hwmod structure to contain info about the voltage domain to which the device belongs to. This is needed to support a device based DVFS where the device knows which voltage domain it belongs to. Signed-off-by: Thara Gopinath th...@ti.com ---

[PATCH 04/13] OMAP: Introduce API to return a device list associated with a voltage domain

This patch adds an API in the opp layer that can be used by the voltage layer to get a list of all the scalable devices belonging to a particular voltage domain. This API is to be typically called only once by the voltage layer per voltage domain instance and the device list should be stored. This

[PATCH 08/13] OMAP: Introduce device set_rate and get_rate.

This patch adds omap_device_set_rate and omap_device_get_rate API's which can be used to generic device rate scaling. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/plat-omap/include/plat/omap_device.h |3 + arch/arm/plat-omap/omap_device.c | 74

[PATCH 09/13] OMAP: Disable smartreflex across DVFS

This patch disables smartreflex for a particular voltage domain when the the voltage domain and the devices belonging to it is being scaled and re-enables it back once the scaling is done. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/mach-omap2/voltage.c |7 +++ 1 files

[PATCH 07/13] OMAP: Introduce dependent voltage domain support.

There could be dependencies between various voltage domains for maintaining system performance or hardware limitation reasons like VDDX should be at voltage v1 when VDDY is at voltage v2. This patch introduce dependent vdd information structures in the voltage layer which can be used to populate

[PATCH 13/13] OMAP3: Add voltage dependency table for VDD1.

In OMAP3, for perfomrance reasons when VDD1 is at voltage above 1.075V, VDD2 should be at 1.15V for perfomrance reasons. This patch introduce this cross VDD dependency for OMAP3 VDD1. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/mach-omap2/voltage.c | 19 +++ 1 files

[PATCH 12/13] OMAP3: Introduce voltage domain info in the hwmod structures.

This patch adds voltage domain info in the relevant device hwmod structures so as to enable OMAP3 DVFS support. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/mach-omap2/omap_hwmod_3xxx_data.c |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git

[PATCH 11/13] OMAP3: Update cpufreq driver to use the new set_rate API

This patch updates the cpufreq driver to use the device set rate API to scale the mpu frequency for OMAP3. Signed-off-by: Thara Gopinath th...@ti.com --- arch/arm/plat-omap/cpu-omap.c |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/arm/plat-omap/cpu-omap.c

[PATCH 10/13] OMAP3: Introduce custom set rate and get rate APIs for scalable devices

This patch also introduces omap3_mpu_set_rate, omap3_iva_set_rate, omap3_l3_set_rate, omap3_mpu_get_rate, omap3_iva_get_rate, omap3_l3_get_rate as device specific set rate and get rate APIs for OMAP3 mpu, iva and l3_main devices. This patch also calls into opp_populate_rate_fns during system init

[PATCH 06/13] OMAP: Voltage layer changes to support DVFS.

This patch introduces a list of scalable devices associated with a particular voltage domain instance. This list is obtained from the opp layer during init. This patch also introduces an API to take in the voltage domain and the new voltage as parameter and to scale all the scalable devices

[PATCH 05/13] OMAP: Introduce device specific set rate and get rate in device opp structures.

This patch extends the device opp structure to contain pointers to scale the operating rate of the device and to retrieve the operating rate of the device. This patch also adds the three new APIs in the opp layer namely opp_set_rate that can be called to set a new operating rate for a device,

RE: [PATCH] OMAP:DSS:Add support for Additional color modes supported by OMAP4

Hi Tomi, Sorry I configured my email client :). Here is the link for OMAP4 TRM : http://focus.ti.com/pdfs/wtbu/SWPU223D_Final_EPDF_06_07_2010.pdf -Original Message- From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com] Sent: Wednesday, August 18, 2010 2:32 PM To: K,

[PATCH] power_supply: add isp1704 charger detection driver

From: Heikki Krogerus ext-heikki.kroge...@nokia.com NXP ISP1704 is Battery Charging Specification 1.0 compliant USB transceiver. This adds a power supply driver for ISP1704 and ISP1707 USB transceivers. Signed-off-by: Heikki Krogerus ext-heikki.kroge...@nokia.com --- drivers/power/Kconfig

RE: [PATCH] OMAP:DSS:Add support for Additional color modes supported by OMAP4

Hi, On Wed, 2010-08-18 at 14:52 +0200, ext K, Mythri P wrote: Hi Tomi, Sorry I configured my email client :). Here is the link for OMAP4 TRM : http://focus.ti.com/pdfs/wtbu/SWPU223D_Final_EPDF_06_07_2010.pdf That is for OMAP34xx... Tomi -- To unsubscribe from this list: send

Re: [PATCH] power_supply: add isp1704 charger detection driver

On Wed, Aug 18, 2010 at 04:01:05PM +0300, Krogerus Heikki (EXT-Teleca/Helsinki) wrote: From: Heikki Krogerus ext-heikki.kroge...@nokia.com NXP ISP1704 is Battery Charging Specification 1.0 compliant USB transceiver. This adds a power supply driver for ISP1704 and ISP1707 USB transceivers.

RE: [PATCH] OMAP:DSS:Add support for Additional color modes supported by OMAP4

Hi Tomi, I shall check if the OMAP4 TRM is public and get back to you. Here is the excerpt of the TRM , for the color modes. DISPC_VID1_ATTRIBUTES Bits Field Name Description Type Reset 4:1 FORMAT Video Format. RW 0x0 It defines the pixel format when fetching the video #1 picture into memory.

[PATCH 0/8 v2]usb: musb: hwmod and runtime pm support for musb

Cc: Felipe Balbi felipe.ba...@nokia.com Cc: Tony Lindgren t...@atomide.com Cc: Kevin Hilman khil...@deeprootsystems.com Cc: Cousson, Benoit b-cous...@ti.com Cc: Paul Walmsley p...@pwsan.com This patch series makes OMAP2PLUS musb Module implemented in HWMOD FW way. It also implements musb driver

[PATCH 2/8 v2] usb: musb: Remove board_data parameter from musb_platform_init()

Removed the board_data parameter being passed to musb_platform_init function as board data can be extracted from device structure which is already member of musb structure. Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi felipe.ba...@nokia.com Cc: Tony Lindgren t...@atomide.com Cc: Kevin

[PATCH 3/8 v2] usb: musb: HWMOD database structures addition for OMAP3

OMAP3 hwmod data stuctures are populated with base address, L3 and L4 interface clocks, IRQs,and sysconfig register details. Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi felipe.ba...@nokia.com Cc: Tony Lindgren t...@atomide.com Cc: Kevin Hilman khil...@deeprootsystems.com Cc: Cousson,

[PATCH 4/8 v2] usb: musb: HWMOD database structures addition for OMAP4

From: Cousson, Benoit b-cous...@ti.com OMAP3 hwmod data stuctures are populated with base address, L3 and L4 interface clocks, IRQs,and sysconfig register details. Signed-off-by: Cousson, Benoit b-cous...@ti.com Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi felipe.ba...@nokia.com Cc:

[PATCH 5/8 v2] usb: musb: Using omap_device_build for musb device registration

Using omap_device_build api instead of platform_device_register for musb device registration.The device specific resources defined in centralized database will be used. So removed the resource definitions from the musb platform file. Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi

[PATCH 6/8 v2] usb: musb: Offmode fix for idle path

With OMAP core-off support musb was not functional as context was getting lost after wakeup from core-off. And also musb was blocking the core-off after loading the gadget driver even with no cable connected sometimes. Added the conext save/restore api in the platform layer which will be called

[PATCH 7/8 v2] OMAP: Hwmod api changes

OMAP USBOTG modules has a requirement to set the auto idle bit only after setting smart idle bit. Modified the _sys_enable api to set the smart idle first and then the autoidle bit. Setting this will not have any impact on the other modules. Added 2 wrapper APIs in the omap device layer for

[PATCH 8/8 v2] usb : musb: Using runtime pm apis for musb.

Calling runtime pm APIs pm_runtime_put_sync() and pm_runtime_get_sync() for enabling/disabling the clocks,sysconfig settings. used omap_hwmod_enable_wakeup omap_hwmod_disable_wakeup apis to set/clear the wakeup enable bit. Also need to put the USB in force standby and force idle mode when usb

RE: [PATCH 2/4] mfd: twl-core: switch over to defines in twl.h

-Original Message- From: Felipe Balbi [mailto:felipe.ba...@nokia.com] Sent: Wednesday, August 18, 2010 12:46 PM To: Balbi Felipe (Nokia-MS/Helsinki) Cc: Gopinath, Thara; Samuel Ortiz; linux-ker...@vger.kernel.org; linux-omap@vger.kernel.org; Tony Lindgren; Andrew Morton Subject: Re:

Re: [PATCH] power_supply: add isp1704 charger detection driver

Hi, On 08/18/2010 04:01 PM, Krogerus Heikki (EXT-Teleca/Helsinki) wrote: From: Heikki Krogerusext-heikki.kroge...@nokia.com NXP ISP1704 is Battery Charging Specification 1.0 compliant USB transceiver. This adds a power supply driver for ISP1704 and ISP1707 USB transceivers. Signed-off-by:

[PATCH 0/5] usb: omap: prepare for OMAP4 EHCI and OHCI support

This series does minor code cleanup in preparation of an upcoming series to add support for EHCI and OHCI on the OMAP4 SoC. The changes are: - Rename clock names to be consistent across OMAP3 and OMAP4 - Remove hardcoding of the number of TLL channels - Move PHY reset earlier in the init sequence

[PATCH 1/5] usb: ehci: omap: Update clock names to be same across OMAP3 and OMAP4

Rename usbhost2_120m_fck to usbhost_hs_fck and usbhost1_48m_fck to usbhost_fs_fck, so that we can reuse the names across OMAP3 and OMAP4. OMAP3 and OMAP4 have similar clocks, with different frequencies. The driver should not need to care about these. Signed-off-by: Keshava Munegowda

[PATCH 2/5] usb: ehci: don't hard-code TLL channel count.

Make TLL channel count a parameter instead of a hardcoded value. This allows us to be flexible with future OMAP revisions which could have a different number of channels. Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com Signed-off-by: Anand Gadiyar gadi...@ti.com ---

[PATCH 3/5] usb: ehci: relocate PHY reset code

The PHY reset code is moved at the begining and end of the function omap_start_ehc. This simplfies the writing clocks enabling code for OMAP4 later. Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com Signed-off-by: Anand Gadiyar gadi...@ti.com --- drivers/usb/host/ehci-omap.c | 52

[PATCH 4/5] usb: ohci: omap: Update clock names to be same across OMAP3 and OMAP4

Rename usbhost2_120m_fck to usbhost_hs_fck and usbhost1_48m_fck to usbhost_fs_fck, so that we can reuse the names across OMAP3 and OMAP4. OMAP3 and OMAP4 have similar clocks, with different frequencies. The driver should not need to care about these. Signed-off-by: Keshava Munegowda

[PATCH 5/6] usb: ohci: don't hard-code TLL channel count

Make TLL channel count a parameter instead of a hardcoded value. This allows us to be flexible with future OMAP revisions which could have a different number of channels. Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com Signed-off-by: Anand Gadiyar gadi...@ti.com ---

[PATCH 5/5] usb: ohci: don't hard-code TLL channel count

Make TLL channel count a parameter instead of a hardcoded value. This allows us to be flexible with future OMAP revisions which could have a different number of channels. Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com Signed-off-by: Anand Gadiyar gadi...@ti.com ---

Re: [PATCH 3/3] OMAP: hwmod: Force a softreset during _setup

Hi Partha, On 8/17/2010 2:46 PM, Basak, Partha wrote: From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Cousson, Benoit Sent: Thursday, August 05, 2010 3:43 AM Force the softreset of every IPs during the _setup phase. IPs that cannot support

RE: [PATCH 5/6] usb: ohci: don't hard-code TLL channel count

It is [PATCH 5/5] not [PATCH 5/6]. I have resent this mail with this subject correction. Regards, Keshava Munegowda -Original Message- From: Munegowda, Keshava Sent: Wednesday, August 18, 2010 8:26 AM To: linux-...@vger.kernel.org; linux-omap@vger.kernel.org Cc: Munegowda,

Re: NAND ECC in linux-omap

On Wed, Aug 18, 2010 at 12:14 AM, Ghorai, Sukumar s-gho...@ti.com wrote: [Ghorai] 1. Can you send the git tree link and branch you are referring? git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git branch: pm 95e42b92313f229cbc9fc81bf68fe60aaee515aa I'm pretty sure this

[PATCH v5 1/3] ARM: OMAP: Beagle: revision detection

Due to the omap3530 ES3.0 Silicon being used on both the B5/B6 and C1/2/3 Beagle we can't use the cpu_is_omap34xx() routines to differentiate the Beagle Boards. However gpio pins 171,172,173 where setup for this prupose, so lets use them. Changes: for older U-Boot's, use omap_mux_init_gpio()

[PATCH v5 2/3] ARM: OMAP: Beagle: only Cx boards use pin 23 for write protect

system_rev comes from u-boot and is a constant 0x20, so Bx boards also fall in this 'if' and will get setup with the wrong gpio_wp pin. Switch to using the Beagle revision routine to correcly set pin 23 only for C1/2/3 and C4 Boards. Bx boards will then use the correct default pin setting.

[PATCH v5 3/3] ARM: OMAP: Beagle: no gpio_wp pin connection on xM

The omap3630 based BeagleBoard xM uses a MicroSD card slot with no write protection. Signed-off-by: Robert Nelson robertcnel...@gmail.com --- arch/arm/mach-omap2/board-omap3beagle.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git

RE: [PATCH 1/3] RTC:s35390a: Add Alarm interrupt support

-Original Message- From: Felipe Balbi [mailto:felipe.ba...@nokia.com] Sent: Tuesday, August 17, 2010 2:59 PM To: Hiremath, Vaibhav Cc: linux-ker...@vger.kernel.org; a...@linux-foundation.org; byron.bbrad...@gmail.com; linux-omap@vger.kernel.org Subject: Re: [PATCH 1/3] RTC:s35390a: