RE: [PATCH 1/2] ads7846: fix gpio free without requesting

2011-02-03 Thread Anand Gadiyar
Varadarajan, Charulatha wrote: Sourav, On Wed, Feb 2, 2011 at 21:00, Sourav Poddar sourav.pod...@ti.com wrote: gpio_pendown in ads7846_probe is not getting initalized (defaulted to 0) resulting in gpio_free being called without a gpio_request. This results in the following backtrace in

Re: [PATCH] ARM: omap1/nokia770: mark some functions __init

2011-02-03 Thread Uwe Kleine-König
Hey Tony, this patch below is now 4 months old and I didn't get any feedback. (Though I somehow missed to cc linux-omap@vger.kernel.org before, sorry for that.) There are two more patches in this thread that are not yet applied/commented. Should I resend? Best regards Uwe On Thu, Sep 02,

RE: [PATCH] omap4: Fix ULPI PHY init for ES1.0 SDP (Re: 4430SDP boot failure)

2011-02-03 Thread Santosh Shilimkar
-Original Message- From: Tony Lindgren [mailto:t...@atomide.com] Sent: Thursday, February 03, 2011 1:19 AM To: Santosh Shilimkar Cc: Anand Gadiyar; Russell King - ARM Linux; linux-arm- ker...@lists.infradead.org; linux-omap@vger.kernel.org; Keshava Munegowda; Felipe Balbi Subject:

RE: [PATCH 1/6] omap4: powerdomain: Add supported INACTIVE power state

2011-02-03 Thread Santosh Shilimkar
-Original Message- From: Paul Walmsley [mailto:p...@pwsan.com] Sent: Thursday, February 03, 2011 3:11 AM To: Santosh Shilimkar Cc: linux-omap@vger.kernel.org; Kevin Hilman; Benoit Cousson; Rajendra Nayak; linux-arm-ker...@lists.infradead.org Subject: RE: [PATCH 1/6] omap4:

RE: [PATCH 1/6] omap4: powerdomain: Add supported INACTIVE power state

2011-02-03 Thread Santosh Shilimkar
-Original Message- From: Kevin Hilman [mailto:khil...@ti.com] Sent: Thursday, February 03, 2011 2:58 AM To: Rajendra Nayak Cc: Santosh Shilimkar; linux-omap@vger.kernel.org; p...@pwsan.com; Benoit Cousson; linux-arm-ker...@lists.infradead.org Subject: Re: [PATCH 1/6] omap4:

Re: [PATCH 1/2] ads7846: fix gpio free without requesting

2011-02-03 Thread Varadarajan, Charulatha
snip diff --git a/drivers/input/touchscreen/ads7846.c b/drivers/input/touchscreen/ads7846.c index 14ea54b..036f245 100644 --- a/drivers/input/touchscreen/ads7846.c +++ b/drivers/input/touchscreen/ads7846.c @@ -1221,6 +1221,7 @@ static int __devinit ads7846_probe(struct spi_device

Re: [PATCH 1/5 v5] OMAP2430: hwmod data: Add USBOTG

2011-02-03 Thread Felipe Balbi
Hi, On Thu, Feb 03, 2011 at 11:24:48AM +0530, Hema Kalliguddi wrote: Any comments? For me these are ok, Tony/Kevin, do you want me to prepare a pull request when we're closer to .39 merge window for one of you guys to pull from and get this part in mainline ? pm_runtime parts (which only touch

[PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread Sourav Poddar
gpio_pendown in ads7846_probe is not getting initalized (defaulted to 0) resulting in gpio_free to be called without a gpio_request. This results in the following backtrace in bootup. [ cut here ] WARNING: at drivers/gpio/gpiolib.c:1258 gpio_free+0x100/0x12c() Modules

[PATCHv2 2/2] Input: ads7846 - configure pendown gpio as input

2011-02-03 Thread Sourav Poddar
The ads7846 driver requests a gpio to detect pendown events, but does not configure its direction. Configure this gpio as an input after requesting it. Signed-off-by: Sourav Poddar sourav.pod...@ti.com --- changes between v2 and v1: Added return error support in v2.

[PATCH 1/7] usb: otg: enable regulator only on cable/device connect

2011-02-03 Thread Hema HK
Remove the regulator enable while driver loading and enable it only when the cable/device is connected and disable it when disconnected. Remove the configuration of config_state and config_trans register configuration as these registers are programmed when regulator enable/disable is called.

[PATCH 2/7] usb: otg: Remove one unnecessary I2C read request.

2011-02-03 Thread Hema HK
To get the ID status there was an I2C read transfer. Removed this I2C read transfer as this info can be used from existing variable(linkstat). Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi ba...@ti.com --- drivers/usb/otg/twl6030-usb.c |7 ++- 1 file changed, 2 insertions(+), 5

[PATCH 3/7] usb: otg: OMAP4430: Introducing suspend function for power management

2011-02-03 Thread Hema HK
Introduced the suspend/resume function for the OMAP4430 internal PHY. This will be used by the twl6030-usb transceiver driver. Moved the clock enable/disable function calls and power on/off of the PHY code from power on/off functions to suspend/resume function. Signed-off-by: Hema HK

[PATCH 5/7] usb: otg: TWL6030: Introduce the twl6030_phy_suspend function.

2011-02-03 Thread Hema HK
Introduce the twl6030_phy_suspend function and assign to otg.set_suspend function pointer. This function is used by the musb-omap2430 platform driver during suspend/resume. Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi ba...@ti.com --- drivers/usb/otg/twl6030-usb.c | 16

[PATCH 4/7] usb: otg: OMAP4430: Add phy_suspend function pointer to twl4030_usb_data

2011-02-03 Thread Hema HK
Introduce the .phy_suspend function pointer to twl4030_usb_data structure. assign the function to it for both sdp board and panda boards. This will be used by the twl6030-usb transceiver driver. Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi ba...@ti.com Cc: Tony Lindgren t...@atomide.com

[PATCH 6/7] usb: otg: TWL6030 Save the last event in otg_transceiver

2011-02-03 Thread Hema HK
Save the last event in the otg_transceiver so that it can used in the musb driver and gadget driver to configure the musb and enable the vbus for host mode and OTG mode, if the device is connected during boot. Signed-off-by: Hema HK hem...@ti.com Cc: Felipe Balbi ba...@ti.com --- [Reusing some

[PATCH 7/7] usb: musb: OMAP4430: Fix usb device detection if connected during boot

2011-02-03 Thread Hema HK
OMAP4430 is embedded with UTMI PHY. This PHY does not support the OTG features like ID pin detection and VBUS detection. This function is exported to an external companion chip TWL6030. Software must retrieve the OTG HNP and SRP status from the TWL6030 and configure the bits inside the control

Re: [PATCHv2 2/2] Input: ads7846 - configure pendown gpio as input

2011-02-03 Thread Felipe Balbi
On Thu, Feb 03, 2011 at 03:18:50PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio to detect pendown events, but does not configure its direction. Configure this gpio as an input after requesting it. Signed-off-by: Sourav Poddar sourav.pod...@ti.com --- changes between v2

Re: [PATCHv2 2/2] Input: ads7846 - configure pendown gpio as input

2011-02-03 Thread Varadarajan, Charulatha
Sourav, On Thu, Feb 3, 2011 at 15:28, Felipe Balbi ba...@ti.com wrote: On Thu, Feb 03, 2011 at 03:18:50PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio to detect pendown events, but does not configure its direction. Configure this gpio as an input after requesting it.

Re: [PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread Igor Grinberg
Hi, On 02/03/11 11:48, Sourav Poddar wrote: gpio_pendown in ads7846_probe is not getting initalized (defaulted to 0) resulting in gpio_free to be called without a gpio_request. This results in the following backtrace in bootup. [ cut here ] WARNING: at

Re: [PATCHv2 2/2] Input: ads7846 - configure pendown gpio as input

2011-02-03 Thread Wolfram Sang
On Thu, Feb 03, 2011 at 11:58:45AM +0200, Felipe Balbi wrote: On Thu, Feb 03, 2011 at 03:18:50PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio to detect pendown events, but does not configure its direction. Configure this gpio as an input after requesting it.

Re: [PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread Igor Grinberg
Hi again, On 02/03/11 12:10, Igor Grinberg wrote: Hi, On 02/03/11 11:48, Sourav Poddar wrote: gpio_pendown in ads7846_probe is not getting initalized (defaulted to 0) resulting in gpio_free to be called without a gpio_request. This results in the following backtrace in bootup.

[RFT/RFC/PATCH 01/13] cbus: retu: get rid of retu-user.c

2011-02-03 Thread Felipe Balbi
Drop that non-standard of accessing Retu as it's bypassing all the correct layers. Signed-off-by: Felipe Balbi ba...@ti.com --- drivers/cbus/Kconfig |7 - drivers/cbus/Makefile|1 - drivers/cbus/retu-user.c | 424 --

[RFT/RFC/PATCH 02/13] cbus: retu: give it a context structure

2011-02-03 Thread Felipe Balbi
This is pretty much a cleanup patch just adding a context structure for Retu, to avoid all the globals it had. Note that this breaks retu-user.c due to moving the lock around, but that retu-user.c has to go anyway as it's completely non-standard way of accessing Retu children. Signed-off-by:

[RFT/RFC/PATCH 03/13] cbus: retu: move module_* close to the matching symbol

2011-02-03 Thread Felipe Balbi
Just to make checkpatch.pl a bit happier, move subsys_initcall() and module_exit() closer to the init and exit functions of the driver. Signed-off-by: Felipe Balbi ba...@ti.com --- drivers/cbus/retu.c | 11 +-- 1 files changed, 1 insertions(+), 10 deletions(-) diff --git

[RFT/RFC/PATCH 04/13] cbus: retu: cleanup error path

2011-02-03 Thread Felipe Balbi
Trivial cleanup patch shuffling error path around. Signed-off-by: Felipe Balbi ba...@ti.com --- drivers/cbus/retu.c | 29 + 1 files changed, 17 insertions(+), 12 deletions(-) diff --git a/drivers/cbus/retu.c b/drivers/cbus/retu.c index 0053d43..7e67e1a 100644 ---

[RFT/RFC/PATCH 05/13] arm: omap: irqs: add CBUS_RETU_IRQ_BASE and CBUS_RETU_IRQ_END

2011-02-03 Thread Felipe Balbi
those two will be used to pass down irq_base and irq_end to retu platform_driver. Signed-off-by: Felipe Balbi ba...@ti.com --- arch/arm/plat-omap/include/plat/irqs.h | 10 +- 1 files changed, 9 insertions(+), 1 deletions(-) diff --git a/arch/arm/plat-omap/include/plat/irqs.h

[RFT/RFC/PATCH 06/13] arm: omap: cbus: pass irq_base and irq_end via platform_data

2011-02-03 Thread Felipe Balbi
Pass CBUS_RETU_IRQ_BASE and CBUS_RETU_IRQ_END via platform_data to retu platform_driver. Signed-off-by: Felipe Balbi ba...@ti.com --- arch/arm/mach-omap1/board-nokia770.c |8 arch/arm/mach-omap2/board-n8x0.c |8 arch/arm/plat-omap/include/plat/cbus.h |5

[RFT/RFC/PATCH 07/13] cbus: retu: move to threaded IRQ and GENIRQ

2011-02-03 Thread Felipe Balbi
Start moving retu to threaded IRQ and while at that also give retu an irq_chip so children can use generic request_threaded_irq() calls. Signed-off-by: Felipe Balbi ba...@ti.com --- drivers/cbus/Makefile | 10 +- drivers/cbus/retu.c | 270 +

[RFT/RFC/PATCH 08/13] cbus: retu: headset: convert to threaded_irq

2011-02-03 Thread Felipe Balbi
use the new irq_chip added to retu.c. Signed-off-by: Felipe Balbi ba...@ti.com --- drivers/cbus/Makefile |2 +- drivers/cbus/retu-headset.c | 22 -- 2 files changed, 13 insertions(+), 11 deletions(-) diff --git a/drivers/cbus/Makefile b/drivers/cbus/Makefile

[RFT/RFC/PATCH 09/13] cbus: retu-pwrbutton: convert to threaded irq

2011-02-03 Thread Felipe Balbi
Drop the timer function and move to threaded irq infrastructure. Signed-off-by: Felipe Balbi ba...@ti.com --- drivers/cbus/Makefile |2 +- drivers/cbus/retu-pwrbutton.c | 37 + 2 files changed, 10 insertions(+), 29 deletions(-) diff --git

[RFT/RFC/PATCH 11/13] cbus: retu-rtc: drop the reset_occurred flag

2011-02-03 Thread Felipe Balbi
that flag is never read anyway, only written, so we can drop it. Signed-off-by: Felipe Balbi ba...@ti.com --- drivers/cbus/retu-rtc.c | 10 ++ 1 files changed, 2 insertions(+), 8 deletions(-) diff --git a/drivers/cbus/retu-rtc.c b/drivers/cbus/retu-rtc.c index 6e201aa..b2b9472 100644

[RFT/RFC/PATCH 12/13] cbus: Makefile: re-enable retu-wdt

2011-02-03 Thread Felipe Balbi
Now that all conversions have been made, reenable retu-wdt driver. Signed-off-by: Felipe Balbi ba...@ti.com --- drivers/cbus/Makefile |3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/drivers/cbus/Makefile b/drivers/cbus/Makefile index 7bfd997..c5c3940 100644 ---

[RFT/RFC/PATCH 13/13] cbus: tahvo: drop tahvo-user

2011-02-03 Thread Felipe Balbi
get rid of the non-standard way of accessing the chip. Signed-off-by: Felipe Balbi ba...@ti.com --- drivers/cbus/Kconfig |7 - drivers/cbus/Makefile |1 - drivers/cbus/tahvo-user.c | 406 - drivers/cbus/tahvo.c | 11 --

[RFT/RFC/PATCH 00/13] CBUS meets GENIRQ

2011-02-03 Thread Felipe Balbi
Hi Tony, When you have some extra time, could you run these on N810 to check whether I'm on the right path ? After these patches all CBUS drivers are using standard request_threaded_irq() calls. It's one step closer into getting those in mainline. Felipe Balbi (13): cbus: retu: get rid of

[RFT/RFC/PATCH 10/13] cbus: retu-rtc: move to threaded irq

2011-02-03 Thread Felipe Balbi
Move to the generic threaded irq infrastructure and drop all the retu-specific magic. Unfortunately, due to the conversion and lack of docs, retu_rtc_ioctl() had to be dropped, someone else with access to docs is free to implement it later considering the new style of the driver. Signed-off-by:

Re: [PATCHv2 2/2] Input: ads7846 - configure pendown gpio as input

2011-02-03 Thread Felipe Balbi
On Thu, Feb 03, 2011 at 11:10:33AM +0100, Wolfram Sang wrote: On Thu, Feb 03, 2011 at 11:58:45AM +0200, Felipe Balbi wrote: On Thu, Feb 03, 2011 at 03:18:50PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio to detect pendown events, but does not configure its direction.

Re: [PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread Poddar, Sourav
On Thu, Feb 3, 2011 at 3:47 PM, Igor Grinberg grinb...@compulab.co.il wrote: Hi again, On 02/03/11 12:10, Igor Grinberg wrote: Hi, On 02/03/11 11:48, Sourav Poddar wrote: gpio_pendown in ads7846_probe is not getting initalized (defaulted to 0) resulting in gpio_free to be called without

Re: [PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread Felipe Balbi
Hi, On Thu, Feb 03, 2011 at 04:30:29PM +0530, Poddar, Sourav wrote: I used -1 because conditional check done in probe ads7846_probe function used this value. err_free_gpio: if (ts-gpio_pendown != -1) gpio_free(ts-gpio_pendown); you can actually change that

Re: [PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread Igor Grinberg
On 02/03/11 13:00, Poddar, Sourav wrote: On Thu, Feb 3, 2011 at 3:47 PM, Igor Grinberg grinb...@compulab.co.il wrote: if (pdata-get_pendown_state) { ts-get_pendown_state = pdata-get_pendown_state; ts-gpio_pendown = -1; return 0; } Yes we can do so .I initialise it at

Re: [PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread ABRAHAM, KISHON VIJAY
On Thu, Feb 3, 2011 at 4:42 PM, Igor Grinberg grinb...@compulab.co.il wrote: On 02/03/11 13:00, Poddar, Sourav wrote: On Thu, Feb 3, 2011 at 3:47 PM, Igor Grinberg grinb...@compulab.co.il wrote: if (pdata-get_pendown_state) {        ts-get_pendown_state = pdata-get_pendown_state;        

RE: [PATCHv5] omap3: Add basic support for 720MHz part

2011-02-03 Thread Premi, Sanjeev
-Original Message- From: Premi, Sanjeev Sent: Thursday, January 27, 2011 4:41 PM To: linux-omap@vger.kernel.org Cc: Premi, Sanjeev Subject: [PATCHv5] omap3: Add basic support for 720MHz part This patch adds support for speed enhanced variant of OMAP35x processors. These parts

[PATCH 0/2] Fix/Clean regulator consumer mapping for 3430sdp

2011-02-03 Thread Rajendra Nayak
This is a short series to fix some, and clean the existing regulator consumer supply mappings for the OMAP3430sdp board. The series is boot tested on the 3430sdp board and applies on 2.6.38-rc3. Rajendra Nayak (2): omap3sdp: Fix regulator mapping for ads7846 TS controller omap3sdp: clean

[PATCH 1/2] omap3sdp: Fix regulator mapping for ads7846 TS controller

2011-02-03 Thread Rajendra Nayak
On the OMAP3430SDP board, the ads7846 touchscreen controller is powered by VAUX3 regulator (supplying 2.8v). Fix this mapping in the board file, and hence prevent the ads7846 driver init to fail with the below error.. ads7846 spi1.0: unable to get regulator: -19 Signed-off-by: Rajendra Nayak

[PATCH 2/2] omap3sdp: clean regulator supply mapping in board file

2011-02-03 Thread Rajendra Nayak
clean the regulator supply mapping data in the 3430sdp board file (which is spread all over) by moving all of them together. Also use the REGULATOR_SUPPLY macro and remove instances of mapping dev pointers at run time. Signed-off-by: Rajendra Nayak rna...@ti.com ---

Re: [PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread Poddar, Sourav
On Thu, Feb 3, 2011 at 5:02 PM, Lothar Waßmann l...@karo-electronics.de wrote: Hi, Igor Grinberg writes: On 02/03/11 13:00, Poddar, Sourav wrote: On Thu, Feb 3, 2011 at 3:47 PM, Igor Grinberg grinb...@compulab.co.il wrote: if (pdata-get_pendown_state) {        ts-get_pendown_state

Re: [PATCHv2 2/2] Input: ads7846 - configure pendown gpio as input

2011-02-03 Thread Poddar, Sourav
On Thu, Feb 3, 2011 at 3:40 PM, Wolfram Sang w.s...@pengutronix.de wrote: On Thu, Feb 03, 2011 at 11:58:45AM +0200, Felipe Balbi wrote: On Thu, Feb 03, 2011 at 03:18:50PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio to detect pendown events, but does not configure its

Re: [PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread Lothar Waßmann
Hi, Igor Grinberg writes: On 02/03/11 13:00, Poddar, Sourav wrote: On Thu, Feb 3, 2011 at 3:47 PM, Igor Grinberg grinb...@compulab.co.il wrote: if (pdata-get_pendown_state) { ts-get_pendown_state = pdata-get_pendown_state; ts-gpio_pendown = -1; return 0;

Re: [PATCH 1/2] omap3sdp: Fix regulator mapping for ads7846 TS controller

2011-02-03 Thread Felipe Balbi
Hi, On Thu, Feb 03, 2011 at 05:01:44PM +0530, Rajendra Nayak wrote: diff --git a/arch/arm/mach-omap2/board-3430sdp.c b/arch/arm/mach-omap2/board-3430sdp.c index d4e41ef..dcdc718 100644 --- a/arch/arm/mach-omap2/board-3430sdp.c +++ b/arch/arm/mach-omap2/board-3430sdp.c @@ -427,6 +427,10 @@

Re: [PATCH 2/2] omap3sdp: clean regulator supply mapping in board file

2011-02-03 Thread Felipe Balbi
On Thu, Feb 03, 2011 at 05:01:45PM +0530, Rajendra Nayak wrote: clean the regulator supply mapping data in the 3430sdp board file (which is spread all over) by moving all of them together. Also use the REGULATOR_SUPPLY macro and remove instances of mapping dev pointers at run time.

RE: [PATCH 1/2] omap3sdp: Fix regulator mapping for ads7846 TS controller

2011-02-03 Thread Rajendra Nayak
-Original Message- From: Felipe Balbi [mailto:ba...@ti.com] Sent: Thursday, February 03, 2011 5:26 PM To: Rajendra Nayak Cc: linux-omap@vger.kernel.org; t...@atomide.com; linux-arm-ker...@lists.infradead.org Subject: Re: [PATCH 1/2] omap3sdp: Fix regulator mapping for ads7846 TS

[PATCH v2 1/2] omap3sdp: Fix regulator mapping for ads7846 TS controller

2011-02-03 Thread Rajendra Nayak
On the OMAP3430SDP board, the ads7846 touchscreen controller is powered by VAUX3 regulator (supplying 2.8v). Fix this mapping in the board file, and hence prevent the ads7846 driver init to fail with the below error.. ads7846 spi1.0: unable to get regulator: -19 Signed-off-by: Rajendra Nayak

[PATCH v2 0/2] Fix/Clean regulator consumer mapping for 3430sdp

2011-02-03 Thread Rajendra Nayak
This is a short series to fix some, and clean the existing regulator consumer supply mappings for the OMAP3430sdp board. The series is boot tested on the 3430sdp board and applies on 2.6.38-rc3. Changes in v2: Define regulator_consumer_supply as array's and use ARRAY_SIZE macro to define

[PATCH v2 2/2] omap3sdp: clean regulator supply mapping in board file

2011-02-03 Thread Rajendra Nayak
clean the regulator supply mapping data in the 3430sdp board file (which is spread all over) by moving all of them together. Also use the REGULATOR_SUPPLY macro and remove instances of mapping dev pointers at run time. Additonally define all regulator_consumer_supply as array's and use ARRAY_SIZE

Re: [PATCH 2/6] omap4: prcm: Fix the CPUx clockdomain offsets

2011-02-03 Thread Cousson, Benoit
Hi Kevin, On 2/2/2011 10:24 AM, Cousson, Benoit wrote: On 2/2/2011 2:20 AM, Hilman, Kevin wrote: Santosh Shilimkarsantosh.shilim...@ti.com writes: CPU0 and CPU1 clockdomain is at the offset of 0x18 from the LPRM base. The header file has set it wrongly to 0x0. Offset 0x0 is for CPUx power

Re: [PATCH v2 1/2] omap3sdp: Fix regulator mapping for ads7846 TS controller

2011-02-03 Thread Felipe Balbi
On Thu, Feb 03, 2011 at 06:15:21PM +0530, Rajendra Nayak wrote: On the OMAP3430SDP board, the ads7846 touchscreen controller is powered by VAUX3 regulator (supplying 2.8v). Fix this mapping in the board file, and hence prevent the ads7846 driver init to fail with the below error.. ads7846

Re: [PATCH v2 2/2] omap3sdp: clean regulator supply mapping in board file

2011-02-03 Thread Felipe Balbi
On Thu, Feb 03, 2011 at 06:15:22PM +0530, Rajendra Nayak wrote: clean the regulator supply mapping data in the 3430sdp board file (which is spread all over) by moving all of them together. Also use the REGULATOR_SUPPLY macro and remove instances of mapping dev pointers at run time.

Re: [PATCHv2 1/2] ads7846: OMAP3: Removal of warnings backtrace in bootup

2011-02-03 Thread Igor Grinberg
Hi, On 02/03/11 13:28, ABRAHAM, KISHON VIJAY wrote: On Thu, Feb 3, 2011 at 4:42 PM, Igor Grinberg grinb...@compulab.co.il wrote: On 02/03/11 13:00, Poddar, Sourav wrote: On Thu, Feb 3, 2011 at 3:47 PM, Igor Grinberg grinb...@compulab.co.il wrote: if (pdata-get_pendown_state) {

Re: [PATCHv2 2/2] Input: ads7846 - configure pendown gpio as input

2011-02-03 Thread Poddar, Sourav
On Thu, Feb 3, 2011 at 3:34 PM, Varadarajan, Charulatha ch...@ti.com wrote: Sourav, On Thu, Feb 3, 2011 at 15:28, Felipe Balbi ba...@ti.com wrote: On Thu, Feb 03, 2011 at 03:18:50PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio to detect pendown events, but does not

Re: [PATCH 4/7] usb: otg: OMAP4430: Add phy_suspend function pointer to twl4030_usb_data

2011-02-03 Thread Sergei Shtylyov
Hello. On 03-02-2011 12:49, Hema HK wrote: Introduce the .phy_suspend function pointer to twl4030_usb_data structure. assign the function to it for both sdp board and panda boards. This will be used by the twl6030-usb transceiver driver. Signed-off-by: Hema HKhem...@ti.com Cc: Felipe

Re: [PATCH 4/7] usb: otg: OMAP4430: Add phy_suspend function pointer to twl4030_usb_data

2011-02-03 Thread Sergei Shtylyov
Hello. On 03-02-2011 12:49, Hema HK wrote: Introduce the .phy_suspend function pointer to twl4030_usb_data structure. assign the function to it for both sdp board and panda boards. This will be used by the twl6030-usb transceiver driver. Signed-off-by: Hema HKhem...@ti.com Cc: Felipe

[PATCH 2/4] OMAP: DSS: Renaming the dpll clk pointer in struct dss

2011-02-03 Thread Raghuveer Murthy
The dss clk pointer dpll4_m4_ck is renamed to dpll_per_mx_ck, to be generic for OMAP3xxx and OMAP44xx platforms. Variable and function names containing dpll4/ dpll4_m4 are also renamed. Signed-off-by: Raghuveer Murthy raghuveer.mur...@ti.com --- drivers/video/omap2/dss/dss.c | 43

[PATCH 4/4] OMAP: DSS2: Get OMAP4 DPLL fclk for DPI interface

2011-02-03 Thread Raghuveer Murthy
DSS DPLL fclk pointer is set, to configure pixel clock for DPI interface. Signed-off-by: Raghuveer Murthy raghuveer.mur...@ti.com --- drivers/video/omap2/dss/dss.c |7 +++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/drivers/video/omap2/dss/dss.c

[PATCH 3/4] OMAP: DSS2: Using dss_features to clean cpu checks for clocks

2011-02-03 Thread Raghuveer Murthy
dss_features are used to substitute cpu_is_() checks for DPLL clock source Signed-off-by: Raghuveer Murthy raghuveer.mur...@ti.com --- drivers/video/omap2/dss/dss.c | 35 ++- 1 files changed, 18 insertions(+), 17 deletions(-) diff --git

[PATCH 1/4] OMAP: DSS2: Add dss_feature for variable DPLL fclk

2011-02-03 Thread Raghuveer Murthy
This patch adds dss_feature for OMAP chips to distinguish between those having a variable DPLL_PER functional clock (fclk). Additionally, a feature for distiguishing the number of available dividers, 16 or 32, for these fclk is added. Signed-off-by: Archit Taneja arc...@ti.com Signed-off-by:

[PATCH 0/4] OMAP4: DSS2: Adding fclk support for DPI interface

2011-02-03 Thread Raghuveer Murthy
- Adding dss_feature for DPLL fclk - Enabling pixel clock generation for DPI interface - Base url = git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git branch master commit 1bae4ce27c9c90344f23c65ea6966c50ffeae2f5 tag

[PATCH 0/4] OMAP: DSS2: Fix for DISPC core functional clock divider

2011-02-03 Thread Raghuveer Murthy
OMAP4 has 2 LCD channels and corresponding DISPC_DIVISOR1 and DISPC_DIVISOR2 registers to configure the pixel clock frequency, for the respective LCD displays. There is also DISPC_DIVISOR register, which by default has the ENABLE bit set to zero, for backward compatibility mode. Hence the logical

[PATCH 4/4] OMAP4: DSS2: Using dss_features to set independent core clock divider

2011-02-03 Thread Raghuveer Murthy
Using dss_features to select independent core clock divider and setting it. Added the register used, to DISPC context save and restore group --- In OMAP4, the minimum DISPC_CORE_CLK required can be expressed as:

[PATCH 3/4] OMAP: DSS2: Adding macro for DISPC_DIVISOR register

2011-02-03 Thread Raghuveer Murthy
Added macro for DISPC_DIVISOR. This is different from DISPC_DIVISOR1 and DISPC_DIVISOR2. OMAP4 supports all the above 3 registers. DISPC_DIVISOR1 and DISPC_DIVISOR2 registers are accessed through DISPC_DIVISORo(ch) macro Signed-off-by: Raghuveer Murthy raghuveer.mur...@ti.com ---

[PATCH 2/4] OMAP: DSS2: Renaming register macro DISPC_DIVISOR(ch)

2011-02-03 Thread Raghuveer Murthy
Renamed DISPC_DIVISOR(ch) to DISPC_DIVISORo(ch), to facilitate introduction of DISPC_DIVISOR register, which is specific for OMAP4. OMAP4 has 3 registers DISPC_DIVISOR, DISPC_DIVISOR1 and DISPC_DIVISOR2. Also updated, all the usages of DISPC_DIVISOR(ch) to DISPC_DIVISORo(ch). OMAP4 TRM uses

[PATCH 1/4] OMAP: DSS2: Adding dss_features for independent core clk divider

2011-02-03 Thread Raghuveer Murthy
In OMAP3xxx DISPC_DIVISOR register has a logical clock divisor (lcd_div) field. The lcd_div is common, for deciding the DISPC core functional clock frequency, and the final pixel clock frequency for LCD display. In OMAP4, there are 2 LCD channels, hence two divisor registers, DISPC_DIVISOR1 and

Re: serial8250: too much work for irq73

2011-02-03 Thread Mathias Nyman
ext Robert Wörle wrote: Hi List I am running into issues , when using ttyS1 on a heavy loaded application. It trys to send and recieve around 60bytes every 100ms with 57600baud. There is a PIC Microcontroller attached on the otherside which immidiatly returns the data when requested.

[PATCH v3 1/2] ads7846: fix gpio free without requesting

2011-02-03 Thread Sourav Poddar
gpio_pendown in ads7846_probe is not getting initalized (defaulted to 0) resulting in gpio_free being called without a gpio_request. This results in the following backtrace in bootup (at least on an OMAP3430 SDP). [ cut here ] WARNING: at drivers/gpio/gpiolib.c:1258

[PATCH v3 2/2] Input: ads7846: use gpio_request_one to configure pendown_gpio

2011-02-03 Thread Sourav Poddar
The ads7846 driver requests a gpio but does not currently configure it explicitly as an input. Use gpio_request_one to request and configure it at one shot. Signed-off-by: Sourav Poddar sourav.pod...@ti.com Cc: Dmitry Torokhov d...@mail.ru --- Links related to the previous discussions:

Re: [PATCH v3 1/2] ads7846: fix gpio free without requesting

2011-02-03 Thread Wolfram Sang
On Thu, Feb 03, 2011 at 08:51:26PM +0530, Sourav Poddar wrote: gpio_pendown in ads7846_probe is not getting initalized (defaulted to 0) resulting in gpio_free being called without a gpio_request. This results in the following backtrace in bootup (at least on an OMAP3430 SDP). I wonder if it

Re: [PATCH v3 1/2] ads7846: fix gpio free without requesting

2011-02-03 Thread Igor Grinberg
Hi, On 02/03/11 17:47, Wolfram Sang wrote: On Thu, Feb 03, 2011 at 08:51:26PM +0530, Sourav Poddar wrote: gpio_pendown in ads7846_probe is not getting initalized (defaulted to 0) resulting in gpio_free being called without a gpio_request. This results in the following backtrace in bootup (at

spin_lock_irqsave and ISP interrupts on OMAP 3530

2011-02-03 Thread Adam Wozniak
I'm hoping I'm just not understanding something and this isn't as broke as I fear it is. I'm using the ISP on an OMAP3530, linux 2.6.32. I've got some kernel code I want to lock in both the process context and the ISP interrupt context, so I'm using a spinlock. As I understand it, locking

Re: [PATCH v3 1/2] ads7846: fix gpio free without requesting

2011-02-03 Thread Wolfram Sang
I wonder if it makes sense to merge both patches under the name of fix gpio-handling or similar. Not sure, though... I'd rather not do that, because this patch fixes the request/free problem and the second is changing the functionality (e.g. configures the gpio as input) Ack. diff

Re: [PATCH v3 2/2] Input: ads7846: use gpio_request_one to configure pendown_gpio

2011-02-03 Thread Dmitry Torokhov
On Thu, Feb 03, 2011 at 08:51:46PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio but does not currently configure it explicitly as an input. Use gpio_request_one to request and configure it at one shot. Signed-off-by: Sourav Poddar sourav.pod...@ti.com Cc: Dmitry Torokhov

Re: [PATCH v3 2/2] Input: ads7846: use gpio_request_one to configure pendown_gpio

2011-02-03 Thread Wolfram Sang
On Thu, Feb 03, 2011 at 08:51:46PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio but does not currently configure it explicitly as an input. Use gpio_request_one to request and configure it at one shot. Signed-off-by: Sourav Poddar sourav.pod...@ti.com Cc: Dmitry Torokhov

Re: [PATCH v3 2/2] Input: ads7846: use gpio_request_one to configure pendown_gpio

2011-02-03 Thread Dmitry Torokhov
On Thu, Feb 03, 2011 at 08:54:05AM -0800, Dmitry Torokhov wrote: On Thu, Feb 03, 2011 at 08:51:46PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio but does not currently configure it explicitly as an input. Use gpio_request_one to request and configure it at one shot.

[PATCH v2 0/5] ARM: omap[34]: Thumb-2 compatibility fixes

2011-02-03 Thread Dave Martin
This set of patches, along with some other patches under discussion on alkml, should enable omap3 and omap4 kernels to be built with CONFIG_THUMB2_KERNEL. This patch set builds on recent cleanup done by the omap maintainers. It is also more aggressive than my last post: all affected low-level

[PATCH v2 1/5] ARM: omap4: Correct definition of do_wfi() for CONFIG_THUMB2_KERNEL

2011-02-03 Thread Dave Martin
For the Thumb-2 case, the wfi mnemonic is used, since in this case the tools will necessarily be new enough to support it. Signed-off-by: Dave Martin dave.mar...@linaro.org --- arch/arm/mach-omap2/include/mach/omap4-common.h |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff

[PATCH v2 2/5] ARM: omap4: Convert END() to ENDPROC() for correct linkage with CONFIG_THUMB2_KERNEL

2011-02-03 Thread Dave Martin
Code marked with ENTRY() also needs a matching ENDPROC() directive, in order to ensure that the type and instruction set of the symbol are correctly annotated. ENDPROC() tags the affected symbol as a function symbol, which will ensure that link-time fixups don't accidentally switch to the wrong

[PATCH v2 4/5] ARM: omap3: Thumb-2 compatibility for sram34xx.S

2011-02-03 Thread Dave Martin
* Remove deprecated/undefined PC-relative stores * Add the required ENDPROC() directive for each ENTRY(). * .align before data words Signed-off-by: Dave Martin dave.mar...@linaro.org --- arch/arm/mach-omap2/sram34xx.S | 28 1 files changed, 20 insertions(+), 8

Re: [PATCH V2] OMAP3: PM: Set/reset T2 bit for Smartreflex on TWL.

2011-02-03 Thread Kevin Hilman
Nishanth Menon n...@ti.com writes: Kevin Hilman wrote, on 02/03/2011 03:09 AM: Nishanth Menonn...@ti.com writes: Kevin Hilman wrote, on 02/02/2011 04:11 AM: Shweta Gulatishweta.gul...@ti.com writes: From: Thara Gopinathth...@ti.com The smartreflex bit on twl4030 needs to be enabled by

[PATCH v2 5/5] ARM: omap3: Thumb-2 compatibility for sleep34xx.S

2011-02-03 Thread Dave Martin
* Use BSYM() to get the correct Thumb branch address for adr Rd, label * Fix an out-of-range ADR when building for ARM * Correctly call es3_sdrc_fix as Thumb when copied to SRAM. * Remove deprecated/undefined PC-relative stores * Add the required ENDPROC() directive for each ENTRY().

[PATCH v2 3/5] ARM: omap3: Remove hand-encoded SMC instructions

2011-02-03 Thread Dave Martin
For various reasons, Linux now only officially supports being built with tools which are new enough to understand the SMC instruction. Replacing the hand-encoded instructions when the mnemonic also allows for correct assembly in Thumb-2 (otherwise, the result is random data in the middle of the

RE: [PATCH v2 3/5] ARM: omap3: Remove hand-encoded SMC instructions

2011-02-03 Thread Santosh Shilimkar
-Original Message- From: Dave Martin [mailto:dave.mar...@linaro.org] Sent: Thursday, February 03, 2011 11:33 PM To: linux-arm-ker...@lists.infradead.org Cc: Dave Martin; Tony Lindgren; Santosh Shilimkar; Jean Pihet; linux-omap@vger.kernel.org; Nicolas Pitre Subject: [PATCH v2 3/5]

RE: [PATCH v2 1/5] ARM: omap4: Correct definition of do_wfi() for CONFIG_THUMB2_KERNEL

2011-02-03 Thread Santosh Shilimkar
-Original Message- From: Dave Martin [mailto:dave.mar...@linaro.org] Sent: Thursday, February 03, 2011 11:33 PM To: linux-arm-ker...@lists.infradead.org Cc: Dave Martin; Tony Lindgren; Santosh Shilimkar; Jean Pihet; linux-omap@vger.kernel.org; Nicolas Pitre Subject: [PATCH v2 1/5]

RE: [PATCH v2 4/5] ARM: omap3: Thumb-2 compatibility for sram34xx.S

2011-02-03 Thread Santosh Shilimkar
-Original Message- From: Dave Martin [mailto:dave.mar...@linaro.org] Sent: Thursday, February 03, 2011 11:33 PM To: linux-arm-ker...@lists.infradead.org Cc: Dave Martin; Tony Lindgren; Santosh Shilimkar; Jean Pihet; linux-omap@vger.kernel.org; Nicolas Pitre Subject: [PATCH v2 4/5]

RE: [PATCH v2 5/5] ARM: omap3: Thumb-2 compatibility for sleep34xx.S

2011-02-03 Thread Santosh Shilimkar
-Original Message- From: Dave Martin [mailto:dave.mar...@linaro.org] Sent: Thursday, February 03, 2011 11:33 PM To: linux-arm-ker...@lists.infradead.org Cc: Dave Martin; Tony Lindgren; Santosh Shilimkar; Jean Pihet; linux-omap@vger.kernel.org; Nicolas Pitre Subject: [PATCH v2 5/5]

Re: [PATCH v2 1/5] ARM: omap4: Correct definition of do_wfi() for CONFIG_THUMB2_KERNEL

2011-02-03 Thread Russell King - ARM Linux
On Fri, Feb 04, 2011 at 12:09:34AM +0530, Santosh Shilimkar wrote: -Original Message- From: Dave Martin [mailto:dave.mar...@linaro.org] Sent: Thursday, February 03, 2011 11:33 PM To: linux-arm-ker...@lists.infradead.org Cc: Dave Martin; Tony Lindgren; Santosh Shilimkar; Jean

RE: [PATCH v2 1/5] ARM: omap4: Correct definition of do_wfi() forCONFIG_THUMB2_KERNEL

2011-02-03 Thread Santosh Shilimkar
-Original Message- From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk] Sent: Friday, February 04, 2011 12:38 AM To: Santosh Shilimkar Cc: Dave Martin; linux-arm-ker...@lists.infradead.org; Tony Lindgren; Nicolas Pitre; linux-omap@vger.kernel.org; Jean Pihet-XID Subject:

RE: [PATCH v9 0/7] nand prefetch-irq support and ecc layout chanage

2011-02-03 Thread Ghorai, Sukumar
-Original Message- From: Ghorai, Sukumar Sent: Friday, January 28, 2011 3:42 PM To: linux-omap@vger.kernel.org Cc: linux-...@lists.infradead.org; linux-arm-ker...@lists.infradead.org; Ghorai, Sukumar Subject: [PATCH v9 0/7] nand prefetch-irq support and ecc layout chanage The

[PATCH][trivial] ARM, OMAP, timer: Remove duplicate inclusion of linux/sched.h from arch/arm/mach-omap1/time.c

2011-02-03 Thread Jesper Juhl
arch/arm/mach-omap1/time.c includes linux/sched.h twice - it's enough to do it once. This removes the duplicate. Signed-off-by: Jesper Juhl j...@chaosbits.net --- time.c |1 - 1 file changed, 1 deletion(-) diff --git a/arch/arm/mach-omap1/time.c b/arch/arm/mach-omap1/time.c index

Re: [PATCH v3 2/2] Input: ads7846: use gpio_request_one to configure pendown_gpio

2011-02-03 Thread Wolfram Sang
On Thu, Feb 03, 2011 at 09:19:53AM -0800, Dmitry Torokhov wrote: On Thu, Feb 03, 2011 at 08:54:05AM -0800, Dmitry Torokhov wrote: On Thu, Feb 03, 2011 at 08:51:46PM +0530, Sourav Poddar wrote: The ads7846 driver requests a gpio but does not currently configure it explicitly as an input.

Re: [PATCH 02/13] OMAP: Introduce device specific set rate and get rate in omap_device structure

2011-02-03 Thread Kevin Hilman
Vishwanath BS vishwanath...@ti.com writes: From: Thara Gopinath th...@ti.com This patch extends the omap_device 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 omap device

Re: [PATCH 03/13] OMAP: Implement Basic DVFS

2011-02-03 Thread Kevin Hilman
Vishwanath BS vishwanath...@ti.com writes: This patch introduces an API to perform DVFS for a given voltage domain. It takes omap_vdd_dvfs_info pointer as input parameter, computes the highest requested voltage for that vdd and scales all the devices in that vdd to the requested frequency

[PATCH] omap: Fix DEBUG_LL code for p2v changes (Re: Fwd: [RFC 4/5] ARM: P2V: introduce phys_to_virt/virt_to_phys runtime patching)

2011-02-03 Thread Tony Lindgren
* Tony Lindgren t...@atomide.com [110118 12:36]: * Russell King - ARM Linux li...@arm.linux.org.uk [110118 10:32]: A warning for OMAP. Your use of the __virt_to_phys() in assembly code for the debug stuff will break with this patch... please ensure that it is resolved by the next merge

[PATCH 0/2] Allow using machine ID for DEBUG_LL macros

2011-02-03 Thread Tony Lindgren
Hi all, Here are two patches that allow using machine ID for DEBUG_LL macros by adding a new macro inituart. Will post the related omap changes separately. Regards, Tony --- Tony Lindgren (2): ARM: Add inituart macro to initialize DEBUG_LL serial port based on the machine ID

  1   2   >