Re: [PATCH v3 2/2] i2c: change id to let i2c-at91 work

Hi J, On 10/16/2012 19:10, Jean-Christophe PLAGNIOL-VILLARD wrote: On 18:25 Tue 16 Oct , Bo Shen wrote: Hi J, On 10/16/2012 16:39, Jean-Christophe PLAGNIOL-VILLARD wrote: On 11:13 Tue 16 Oct , Bo Shen wrote: Hi J, On 10/15/2012 23:02, Jean-Christophe PLAGNIOL-VILLARD wrote: On 17:3

Re: [PATCH 1/1] twl4030: Fix chained irq handling on resume from suspend

Kalle Jokiniemi writes: > The irqs are enabled one-by-one in pm core resume_noirq phase. > This leads to situation where the twl4030 primary interrupt > handler (PIH) is enabled before the chained secondary handlers > (SIH). As the PIH cannot clear the pending interrupt, and > SIHs have not been

Re: [PATCH v2] i2c-hid: introduce HID over i2c specification implementation

Hi Jiri, On Tue, Oct 16, 2012 at 10:17 AM, Jiri Slaby wrote: > On 10/15/2012 10:38 PM, Benjamin Tissoires wrote: >> Notes: >> {1}: I don't have all the informations in the beginning of the probe >> function to >> get the real size I need to allocate. So the behavior is to allocate first a >> buf

[PATCH] i2c: omap: adopt pinctrl support

Some GPIO expanders need some early pin control muxing. Due to legacy boards sometimes the driver uses subsys_initcall instead of module_init. This patch takes advantage of defer probe feature and pin control in order to wait until pin control probing before GPIO driver probing. It has been tested

Re: [PATCH 1/1] twl4030: Fix chained irq handling on resume from suspend

Hi, ti, 2012-10-16 kello 17:59 +0300, Kalle Jokiniemi kirjoitti: > The irqs are enabled one-by-one in pm core resume_noirq phase. > This leads to situation where the twl4030 primary interrupt > handler (PIH) is enabled before the chained secondary handlers > (SIH). As the PIH cannot clear the pend

[PATCH 1/1] twl4030: Fix chained irq handling on resume from suspend

The irqs are enabled one-by-one in pm core resume_noirq phase. This leads to situation where the twl4030 primary interrupt handler (PIH) is enabled before the chained secondary handlers (SIH). As the PIH cannot clear the pending interrupt, and SIHs have not been enabled yet, a flood of interrupts h

Re: [PATCH] i2c: omap: revert "i2c: omap: switch to threaded IRQ support"

Hi again, On Tue, Oct 16, 2012 at 04:33:56PM +0300, Felipe Balbi wrote: > Hi, > > + Thomas Gleixner > > On Tue, Oct 16, 2012 at 06:28:13PM +0530, Shubhrajyoti Datta wrote: > > On Mon, Oct 15, 2012 at 7:21 AM, Paul Walmsley wrote: > > > > > > Commit 3b2f8f82dad7d1f79cdc8fc05bd1c94baf109bde ("i2c

Re: [PATCH] i2c: omap: revert "i2c: omap: switch to threaded IRQ support"

Hi, + Thomas Gleixner On Tue, Oct 16, 2012 at 06:28:13PM +0530, Shubhrajyoti Datta wrote: > On Mon, Oct 15, 2012 at 7:21 AM, Paul Walmsley wrote: > > > > Commit 3b2f8f82dad7d1f79cdc8fc05bd1c94baf109bde ("i2c: omap: switch to > > threaded IRQ support") causes communication with I2C devices to fai

Re: [PATCH] i2c: omap: revert "i2c: omap: switch to threaded IRQ support"

On Mon, Oct 15, 2012 at 7:21 AM, Paul Walmsley wrote: > > Commit 3b2f8f82dad7d1f79cdc8fc05bd1c94baf109bde ("i2c: omap: switch to > threaded IRQ support") causes communication with I2C devices to fail > after system suspend/resume on all OMAP3 devices: > Could you tell me which omap3 platform On

Re: [PATCH v3 2/2] i2c: change id to let i2c-at91 work

On 18:25 Tue 16 Oct , Bo Shen wrote: > Hi J, > > On 10/16/2012 16:39, Jean-Christophe PLAGNIOL-VILLARD wrote: > >On 11:13 Tue 16 Oct , Bo Shen wrote: > >>Hi J, > >> > >>On 10/15/2012 23:02, Jean-Christophe PLAGNIOL-VILLARD wrote: > >>>On 17:30 Mon 15 Oct , Bo Shen wrote: > The i2c

Re: [PATCH v3 2/2] i2c: change id to let i2c-at91 work

Hi J, On 10/16/2012 16:39, Jean-Christophe PLAGNIOL-VILLARD wrote: On 11:13 Tue 16 Oct , Bo Shen wrote: Hi J, On 10/15/2012 23:02, Jean-Christophe PLAGNIOL-VILLARD wrote: On 17:30 Mon 15 Oct , Bo Shen wrote: The i2c core driver will turn the platform device ID to busnum When using pl

Re: [PATCH v3 2/2] i2c: change id to let i2c-at91 work

On 11:13 Tue 16 Oct , Bo Shen wrote: > Hi J, > > On 10/15/2012 23:02, Jean-Christophe PLAGNIOL-VILLARD wrote: > >On 17:30 Mon 15 Oct , Bo Shen wrote: > >>The i2c core driver will turn the platform device ID to busnum > >>When using platfrom device ID as -1, it means dynamically assigned >

Re: [PATCH] i2c: omap: fix spurious IRQs: disable/enable IRQ at INTC when idle

Hi, ma, 2012-10-15 kello 18:02 -0700, Tony Lindgren kirjoitti: > * Kevin Hilman [121015 10:32]: > > Kalle Jokiniemi writes: > > > > > > Does not work for me :( > > > > > > As I said, the issue occurs for me when I enter static suspend (echo mem > > >> /sys/power/autosleep or /sys/power/state). I

Re: [PATCH v2] i2c-hid: introduce HID over i2c specification implementation

On 10/15/2012 10:38 PM, Benjamin Tissoires wrote: > Notes: > {1}: I don't have all the informations in the beginning of the probe function > to > get the real size I need to allocate. So the behavior is to allocate first a > buffer by using HID_MIN_BUFFER_SIZE and once I got the information, I can

Re: [RESEND PATCH v3 2/2] i2c: change id to let i2c-at91 work

On Tue, Oct 16, 2012 at 01:17:48PM +0800, Bo Shen wrote: > From: voice > > The i2c core driver will turn the platform device ID to busnum > When using platfrom device ID as -1, it means dynamically assigned > the busnum. When writing code, we need to make sure the busnum, > and call i2c_register_

Re: [RESEND PATCH v3 1/2] i2c: change id to let i2c-gpio work

On Tue, Oct 16, 2012 at 01:17:47PM +0800, Bo Shen wrote: > From: voice > > The i2c core driver will turn the platform device ID to busnum > When using platfrom device ID as -1, it means dynamically assigned > the busnum. When writing code, we need to make sure the busnum, > and call i2c_register_