[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130201192923.GA23176@pengutronix.de>
Date: Fri, 1 Feb 2013 20:29:23 +0100
From: Wolfram Sang <w.sang@...gutronix.de>
To: Naveen Krishna Chatradhi <ch.naveen@...sung.com>
Cc: linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org, khali@...ux-fr.org,
ben-linux@...ff.org, grant.likely@...retlab.ca,
devicetree-discuss@...ts.ozlabs.org, sjg@...omium.org,
grundler@...omium.org, naveenkrishna.ch@...il.com,
broonie@...nsource.wolfsonmicro.com
Subject: Re: [PATCH v4] i2c: exynos5: add High Speed I2C controller driver
On Fri, Feb 01, 2013 at 09:24:44PM +0530, Naveen Krishna Chatradhi wrote:
> Adds support for High Speed I2C driver found in Exynos5 and later
> SoCs from Samsung. This driver currently supports Auto mode.
>
> Driver only supports Device Tree method.
> Note: Added debugfs support for registers view, not tested.
>
> Signed-off-by: Taekgyun Ko <taeggyun.ko@...sung.com>
> Signed-off-by: Naveen Krishna Chatradhi <ch.naveen@...sung.com>
> ---
> Help please,
>
> Usual reads and writes are happening. But, when i try doing
> i2cdetect -y 0 0x10 0x59; It throws me continous interrupts at 0x1a
> i2cdetect -y 0 0x50 0x64; It throws me continous interrupts at 0x63
>
> There are eeproms from 0x50 till 0x58
> wm8994 codec at 0x1a
>
> Kindly, can anyone explain this behaviour.
You select I2C_FUNC_SMBUS_EMUL, but make sure your hardware really
supports I2C_FUNC_SMBUS_QUICK. That would be my first guess. Also, which
eeprom do you have? Check its datasheet, some in deed use 8 addresses.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists