Hardware supported by the i2c sh_mobile and rcar drivers is only found
on SUPERH or ARCH_SHMOBILE platforms. Restrict non-COMPILE_TEST
compilation to them.
Cc: Wolfram Sang
Cc: linux-i2c@vger.kernel.org
Signed-off-by: Laurent Pinchart
---
drivers/i2c/busses/Kconfig | 4 ++--
1 file changed, 2 i
On Tue, Nov 26, 2013 at 5:00 AM, Wolfram Sang wrote:
> Have you also tried repeated module loading/unloading?
I ran a loop of insmod + rmmod 1000 times and didn't see any issues.
Thanks,
Tim Kryger
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message
> I had looked a bit in that direction, but I think there's currently
> no way for a driver to say "I won't be needing the bus for a while".
> Something like that would be critical for such a pm system to work.
Yes. I wasn't sure if something already existed.
> In any case, it doesn't sound like
On 11/26/2013 01:28 PM, Wolfram Sang wrote:
CCing linux-pm, maybe they know more...
The extra I2C traffic consumes extra power. If the bus is terminated
using 2k resistors, approximately 1mA of current (assuming ~2V
signals) is flowing when the bus is pulled low. On low power
designs, this ext
On 26 November 2013 13:28, Wolfram Sang wrote:
>
> CCing linux-pm, maybe they know more...
>
>> The extra I2C traffic consumes extra power. If the bus is terminated
>> using 2k resistors, approximately 1mA of current (assuming ~2V
>> signals) is flowing when the bus is pulled low. On low power
>>
On Tue, Nov 19, 2013 at 06:14:18PM -0800, Benson Leung wrote:
> Hi Wolfram,
>
> On Thu, Nov 14, 2013 at 10:05 AM, Wolfram Sang wrote:
> >> In the chromeos_laptop driver, I do by-name matching of i2c busses to
> >> find busses and instantiate devices, so there is value to have each
> >> named some
On Fri, Nov 08, 2013 at 09:59:28AM -0700, Stephen Warren wrote:
> On 11/08/2013 02:49 AM, Florian Meier wrote:
> > In order to find I2C devices in the device tree, the platform nodes
> > have to be known by the I2C core. Analogous to the i2c-omap driver
> > this requires setting the dev.of_node par
On Mon, Nov 25, 2013 at 12:01:18PM -0800, Tim Kryger wrote:
> Correct a typo that prevented the driver from being built as a module.
>
> Signed-off-by: Tim Kryger
Applied to for-current, thanks!
Have you also tried repeated module loading/unloading?
signature.asc
Description: Digital signatu
On Mon, Nov 25, 2013 at 09:01:50AM +0100, Florian Meier wrote:
> In order to find I2C devices in the device tree, the platform nodes
> have to be known by the I2C core. This requires setting the
> dev.of_node parameter of the adapter.
>
> Signed-off-by: Florian Meier
Malformed patch, please rese
On Sun, Nov 24, 2013 at 03:57:23PM +0100, Martin Vogt wrote:
> The previous diolan adapter uses other out/in endpoints than
> the current DLN-2-U2C in compatibility mode.
> They changed from 0x2/0x84 to 0x3/0x83.
> This patch gets the endpoints from the usb interface, instead
> of hardcode them in
> > diff --git a/drivers/i2c/busses/i2c-bcm-kona.c
> > b/drivers/i2c/busses/i2c-bcm-kona.c
> > index 865e5dd..1d74da5 100644
> > --- a/drivers/i2c/busses/i2c-bcm-kona.c
> > +++ b/drivers/i2c/busses/i2c-bcm-kona.c
> > @@ -20,7 +20,6 @@
> > #include
> > #include
> > #include
> > -#include
>
On Thu, Nov 21, 2013 at 10:58:46AM +0800, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Remove duplicated include.
Removed duplicated message (same as subject ;))
> Signed-off-by: Wei Yongjun
Applied to for-current, thanks!
signature.asc
Description: Digital signature
> @@ -1142,7 +1142,7 @@ omap_i2c_probe(struct platform_device *pdev)
>* Also since the omap_i2c_read_reg uses reg_map_ip_* a
>* raw_readw is done.
>*/
> - rev = __raw_readw(dev->base + 0x04);
> + rev = readw_relaxed(dev->base + 0x04);
>
> dev->scheme = OMAP_
On Wed, Nov 20, 2013 at 08:23:44PM +0200, Taras Kondratiuk wrote:
> I2C IP block expect LE data, but CPU may operate in BE mode.
> Need to use endian neutral functions to read/write h/w registers.
> I.e instead of __raw_read[lw] and __raw_write[lw] functions code
> need to use read[lw]_relaxed and
CCing linux-pm, maybe they know more...
> The extra I2C traffic consumes extra power. If the bus is terminated
> using 2k resistors, approximately 1mA of current (assuming ~2V
> signals) is flowing when the bus is pulled low. On low power
> designs, this extra power consumption is noticable. Ther
Hello Sachin,
On 26 November 2013 16:59, Sachin Kamat wrote:
> On 26 November 2013 09:56, Naveen Krishna Chatradhi
> wrote:
>> This patch adds new compatible to support HSI2C module on Exynos5260
>> HSI2C module on Exynos5260 needs to be reset during during initialization.
>>
>> Signed-off-by: N
On 26 November 2013 09:56, Naveen Krishna Chatradhi
wrote:
> This patch adds new compatible to support HSI2C module on Exynos5260
> HSI2C module on Exynos5260 needs to be reset during during initialization.
>
> Signed-off-by: Naveen Krishna Chatradhi
[snip]
>
> Required properties:
>- compat
On 11/26/2013 10:06 AM, Wolfram Sang wrote:
On Tue, Nov 26, 2013 at 07:32:00AM +0100, Mike Looijmans wrote:
Leaving the mux enabled causes needless I2C traffic on the downstream
bus. De-selecting after every request causes excess I2C traffic and
switching.
This patch implements a hybrid solutio
On Tue, Nov 26, 2013 at 07:32:00AM +0100, Mike Looijmans wrote:
> Leaving the mux enabled causes needless I2C traffic on the downstream
> bus. De-selecting after every request causes excess I2C traffic and
> switching.
>
> This patch implements a hybrid solution: After 200ms of inactivity,
> the m
19 matches
Mail list logo
