On 05/29/2013 08:22 PM, Kevin Hilman wrote:
Oleksandr Dmytryshyn writes:
Starting from the OMAP chips with version2 registers scheme there are
2 registers (I2C_IRQENABLE_SET and I2C_IRQENABLE_CLR) to manage
interrupts instead of the older OMAP chips with old scheme which have
only one
On 05/30/2013 05:18 PM, Kevin Hilman wrote:
Oleksandr Dmytryshyn writes:
On 05/29/2013 08:22 PM, Kevin Hilman wrote:
Oleksandr Dmytryshyn writes:
Starting from the OMAP chips with version2 registers scheme there are
2 registers (I2C_IRQENABLE_SET and I2C_IRQENABLE_CLR) to manage
E register. But with my patch interrupts
are disabled in the omap_i2c_runtime_suspend() function.
Next patch fixes it.
Patch is based on:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tag: v3.10-rc2
Verified on OMAP4430.
Oleksandr Dmytryshyn (1):
i2c: omap: correct usage of the
addresses, the interrupt enabling procedure is unchanged.
Signed-off-by: Oleksandr Dmytryshyn
---
drivers/i2c/busses/i2c-omap.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index e02f9e3..2419899
On 05/30/2013 07:46 PM, Kevin Hilman wrote:
Oleksandr Dmytryshyn writes:
If the i2c controller during suspend will generate an interrupt, it
can lead to unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
prohibited during suspend
addresses, the interrupt enabling procedure is unchanged.
Change-Id: Ie49165990a4e7c67a4ccf2e4a66cd3b78f2e2b70
Signed-off-by: Oleksandr Dmytryshyn
---
drivers/i2c/busses/i2c-omap.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b
led in the omap_i2c_runtime_suspend() function.
This has been working up until now because we've just been lucky.
Next patch fixes it.
Patch is based on:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tag: v3.10-rc2
Verified on OMAP4430.
Oleksandr Dmytryshyn (1):
i2c
) function.
This has been working up until now because we've just been lucky.
Next patch fixes it.
Patch is based on:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tag: v3.10-rc2
Verified on OMAP4430.
Oleksandr Dmytryshyn (1):
i2c: omap: correct usage of the i
addresses, the interrupt enabling procedure is unchanged.
Signed-off-by: Oleksandr Dmytryshyn
---
drivers/i2c/busses/i2c-omap.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index e02f9e3..64c26f9
s based on:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tag: v3.10-rc2
Verified on OMAP4430.
Signed-off-by: Oleksandr Dmytryshyn
---
drivers/i2c/busses/i2c-omap.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2
t
tag: v3.10-rc2
Verified on OMAP4430.
Oleksandr Dmytryshyn (1):
i2c: omap: correct usage of the interrupt enable register
drivers/i2c/busses/i2c-omap.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
--
1.8.2.rc2
--
To unsubscribe from this list: send the line "u
interrupts and I2C_IRQENABLE_CLR register
for disabling interrupts.
Because the registers I2C_IRQENABLE_SET and I2C_IE have the same
addresses, the interrupt enabling procedure is unchanged.
Change-Id: Ie49165990a4e7c67a4ccf2e4a66cd3b78f2e2b70
Signed-off-by: Oleksandr Dmytryshyn
---
drivers/i2c/busses
12 matches
Mail list logo