Add CONFIG_PM_SLEEP to suspend/resume functions to fix the following
build warning when CONFIG_PM_SLEEP is not selected. This is because
sleep PM callbacks defined by SIMPLE_DEV_PM_OPS are only used when
the CONFIG_PM_SLEEP is enabled.
drivers/i2c/busses/i2c-ocores.c:460:12: warning: 'ocores_i2c_s
Add CONFIG_PM_SLEEP to suspend/resume functions to fix the following
build warning when CONFIG_PM_SLEEP is not selected. This is because
sleep PM callbacks defined by SIMPLE_DEV_PM_OPS are only used when
the CONFIG_PM_SLEEP is enabled.
drivers/i2c/busses/i2c-designware-platdrv.c:253:12: warning: '
Add CONFIG_PM_SLEEP to suspend/resume functions to fix the following
build warning when CONFIG_PM_SLEEP is not selected. This is because
sleep PM callbacks defined by SIMPLE_DEV_PM_OPS are only used when
the CONFIG_PM_SLEEP is enabled.
drivers/i2c/busses/i2c-designware-platdrv.c:253:12: warning: '
Jason Baron wrote:
> Hi,
>
> I've also hit the i2c_i801 driver conflicts with ACPI region:
>
> kernel: [73904.044722] i801_smbus :00:1f.3: PCI INT C -> GSI 18
> (level, low) -> IRQ 18
> kernel: [73904.045573] ACPI: resource :00:1f.3 [io 0xf000-0xf01f]
> conflicts with ACPI region SMBI [i
Hi,
I've also hit the i2c_i801 driver conflicts with ACPI region:
kernel: [73904.044722] i801_smbus :00:1f.3: PCI INT C -> GSI 18
(level, low) -> IRQ 18
kernel: [73904.045573] ACPI: resource :00:1f.3 [io 0xf000-0xf01f]
conflicts with ACPI region SMBI [io 0xf000-0xf00f]
kernel: [73904.046
From: Stephen Warren
Tegra only supports, and always enables, device tree. Remove all ifdefs
and runtime checks for DT support from the driver. Platform data is
therefore no longer required. Delete the header that defines it.
Signed-off-by: Stephen Warren
---
V2: Rebased onto v3.9-rc1; hopefull
Make them conform more to established standards.
Signed-off-by: Heiko Stuebner
---
changes since v1: none
drivers/i2c/busses/i2c-s3c2410.c | 50 ++---
1 files changed, 24 insertions(+), 26 deletions(-)
diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2
The register definitions are only used in the driver itself.
This also removes the last dependency on plat/ includes from the
i2c driver.
Signed-off-by: Heiko Stuebner
Acked-by: Kukjin Kim
---
changes since v1: rebased against 3.9-rc3
arch/arm/mach-s3c24xx/mach-rx1950.c |1 -
arc
From: Andy Shevchenko
This makes the error handling much more simpler than open-coding everything
and in addition makes the probe function smaller and tidier.
Signed-off-by: Andy Shevchenko
Signed-off-by: Mika Westerberg
---
drivers/i2c/busses/i2c-designware-platdrv.c | 73 -
This is not an atomic context so there is no need to use mdelay() but
instead use usleep_range().
Signed-off-by: Mika Westerberg
---
drivers/i2c/busses/i2c-designware-core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-designware-core.c
b/drivers
Using autosuspend helps to reduce the resume latency in situations where
another I2C message is going to be started soon. For example with HID over
I2C touch panels we get several messages in a short period of time while
the touch panel is in use.
Signed-off-by: Mika Westerberg
---
drivers/i2c/b
From: Andy Shevchenko
This makes the error handling much more simpler than open-coding everything
and in addition makes the probe function smaller an tidier.
Signed-off-by: Andy Shevchenko
Signed-off-by: Mika Westerberg
---
drivers/i2c/busses/i2c-designware-pcidrv.c | 68 +++
The correct way to disable or enable the controller is to wait until
DW_IC_ENABLE_STATUS register bit matches the bit we program to the
DW_IC_ENABLE register. This procedure is described in the DesignWare I2C
handbook.
By doing this we can be sure that the controller is in correct state once
the f
It is not good idea to mix static and dynamic I2C adapter numbering. In
this particular case on Lynxpoint we had graphics I2C adapter which took
the first numbers preventing the designware I2C driver from using the
adapter numbers it preferred.
Fix this by switching to use dynamic adapter numberin
From: Andy Shevchenko
With dev_err() we can get the device instance printed as well and is pretty
much standard to use dev_* macros in drivers anyway. In addition correct
indentation of probe() arguments.
Signed-off-by: Andy Shevchenko
Signed-off-by: Mika Westerberg
---
drivers/i2c/busses/i2c
On Fri, Mar 01, 2013 at 08:57:32AM -0800, Doug Anderson wrote:
> The commit: "i2c-core: dt: Pick i2c bus number from i2c alias if
> present" adds support for automatically picking the bus number based
> on the alias ID. Remove the now unnecessary code from i2c-pxa that
> did the same thing.
>
> S
On Tue, Mar 05, 2013 at 08:23:58PM +0800, Shawn Guo wrote:
> With the generic DMA device tree helper supported by mxs-dma driver,
> client devices only need to call dma_request_slave_channel() for
> requesting a DMA channel from dmaengine.
>
> Signed-off-by: Shawn Guo
> Cc: Wolfram Sang
> Cc: li
> I'm not sure anymore ... probably some linux-next. I'll redo them on top of
> your (i2c) for-next branch.
Thanks, but please use 3.9-rc3.
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://
On Thu, Feb 14, 2013 at 12:28:18PM +0100, Cong Ding wrote:
> If it goes to eclk through line 1107, the variable res would be NULL. It will
> cause a null pointer dereference error if we call release_mem_region. The
> correct way should be using devm_kzalloc rather than kzalloc to allocate
> memory.
Hi Wolfram,
Am Donnerstag, 21. März 2013, 10:57:58 schrieb Wolfram Sang:
> On Fri, Feb 08, 2013 at 12:57:00AM +0100, Heiko Stübner wrote:
> > The register definitions are only used in the driver itself.
> > This also removes the last dependency on plat/ includes from the
> > i2c driver.
> >
> > S
Am Donnerstag, 21. März 2013, 11:00:32 schrieb Wolfram Sang:
> On Mon, Mar 04, 2013 at 07:12:53PM +0530, Thomas Abraham wrote:
> > With device core now able to setup the default pin configuration,
> > the call to devm_pinctrl_get_select_default can be removed. And
> > the pin configuration code bas
On Thu, Mar 21, 2013 at 03:45:29PM +0530, Viresh Kumar wrote:
> On 21 March 2013 15:06, Wolfram Sang wrote:
> > I applied V11 of the core changes with minor modifications.
>
> Wow!! Thanks.
>
> > I do wonder
> > about the hook in the designware driver. You apply the recovery on
> > transfer time
On 21 March 2013 15:06, Wolfram Sang wrote:
> I applied V11 of the core changes with minor modifications.
Wow!! Thanks.
> I do wonder
> about the hook in the designware driver. You apply the recovery on
> transfer timeout. I think this should go into the timeout of
> i2c_dw_wait_bus_not_busy()?
On Mon, Mar 04, 2013 at 07:12:53PM +0530, Thomas Abraham wrote:
> With device core now able to setup the default pin configuration,
> the call to devm_pinctrl_get_select_default can be removed. And
> the pin configuration code based on the deprecated Samsung specific
> gpio bindings is also removed
On Fri, Feb 08, 2013 at 12:57:00AM +0100, Heiko Stübner wrote:
> The register definitions are only used in the driver itself.
> This also removes the last dependency on plat/ includes from the
> i2c driver.
>
> Signed-off-by: Heiko Stuebner
What tree is this against? I can't apply it on top of v
Viresh,
I applied V11 of the core changes with minor modifications. I do wonder
about the hook in the designware driver. You apply the recovery on
transfer timeout. I think this should go into the timeout of
i2c_dw_wait_bus_not_busy()?
Thanks,
Wolfram
--
To unsubscribe from this list: send th
26 matches
Mail list logo