Hi Jon,
On Mon, 20 Oct 2008 23:02:05 -0400, Jon Smirl wrote:
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
drivers/i2c/chips/Kconfig |9
drivers/i2c/chips/Makefile |1
drivers/i2c/chips/max9485.c | 106
+++
On Mon, Oct 20, 2008 at 11:02:05PM -0400, Jon Smirl wrote:
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
drivers/i2c/chips/Kconfig |9
drivers/i2c/chips/Makefile |1
drivers/i2c/chips/max9485.c | 106
+++
Hi Arjen,
On Mon, 20 Oct 2008 21:57:51 -0700, Arjan van de Ven wrote:
From 2642176b21b402e7f1ea7697ad2659d0e7e59f6e Mon Sep 17 00:00:00 2001
From: Arjan van de Ven [EMAIL PROTECTED]
Date: Sun, 28 Sep 2008 16:13:48 -0700
Subject: [PATCH] pci: use pci_ioremap_bar() in drivers/i2c
Use the
Hy,
I wrote a simple user program to test an i2c bus driver. I found in
Documentation/i2c/dev-interface their is macro function to read data
(i2c_smbus_read_byte_data). I used it but I have link error when I compile :
$ arm-linux-gcc -O i2cread.c -o i2cread
/tmp/ccfa90st.o: In function
Hi All,
I wrote a MCP3021's driver using the new I2C device model under Linux
2.6.26.
The chip MCP3021 is connected to Freescale's I2C controller.
Now it works well, the following is the log info:
-sh-2.05b# ls /sys/bus/i2c/drivers/mcp3021/
0-004d 1-004d bind module uevent unbind
Hi Vincent,
On Tue, 21 Oct 2008 18:31:07 +0800, Hu Mingkai-B21284 wrote:
I wrote a MCP3021's driver using the new I2C device model under Linux
2.6.26.
The chip MCP3021 is connected to Freescale's I2C controller.
Now it works well, the following is the log info:
-sh-2.05b# ls
Hi all,
I use an etx-board with a Geode LX800 and a CS5536. I want to connect a
eeprom with i2c. My board has pins for i2c and smbus.
Because there are several smbus-devices on board, I want to use the
i2c-pins for connecting my eeprom (24c64).
How can I tell the linux kernel (2.6.21) which
Salut Fabien,
On Tue, 21 Oct 2008 11:44:28 +0200, Fabien Marteau wrote:
I wrote a simple user program to test an i2c bus driver. I found in
Documentation/i2c/dev-interface their is macro function to read data
(i2c_smbus_read_byte_data). I used it but I have link error when I compile :
$
This patch adds support for the (I2C based) DS28CM00 ID chip.
(v2 after running through checkpatch)
Signed-off-by: M.Jackson [EMAIL PROTECTED]
---
drivers/i2c/chips/Kconfig|7 ++
drivers/i2c/chips/Makefile |1 +
drivers/i2c/chips/ds28cm00.c | 166
On Tue, 21 Oct 2008 15:55:26 +0100, Mark Jackson wrote:
This patch adds support for the (I2C based) DS28CM00 ID chip.
(v2 after running through checkpatch)
Signed-off-by: M.Jackson [EMAIL PROTECTED]
---
drivers/i2c/chips/Kconfig|7 ++
drivers/i2c/chips/Makefile |1 +
The chips directory under drivers/i2c is deprecated. Spread the word!
Signed-off-by: Wolfram Sang [EMAIL PROTECTED]
---
Maybe this makes Jean's life a bit easier ;)
drivers/i2c/chips/Kconfig |3 +++
drivers/i2c/chips/Makefile |3 ++-
2 files changed, 5 insertions(+), 1 deletions(-)
Jean Delvare wrote:
On Tue, 21 Oct 2008 15:55:26 +0100, Mark Jackson wrote:
This patch adds support for the (I2C based) DS28CM00 ID chip.
(v2 after running through checkpatch)
Signed-off-by: M.Jackson [EMAIL PROTECTED]
---
drivers/i2c/chips/Kconfig|7 ++
Mark Jackson wrote:
Jean Delvare wrote:
Hi Mark,
On Tue, 21 Oct 2008 19:42:42 +0100, Mark Jackson wrote:
Jean Delvare wrote:
Nack. No new drivers under drivers/i2c/chips please, it's going away
soon.
Okay ... where should any new drivers be located ?
Depends of what the device does.
*
On Tue, Oct 21, 2008 at 4:36 AM, Jean Delvare [EMAIL PROTECTED] wrote:
Honestly I don't see any value in this driver. There's nothing you can
do with it that you couldn't already do without it.
I need a driver so that my device tree will bind and tell me the i2c
address of the device.
We may
On Fri, 2008-10-17 at 11:21 +0200, Jean Delvare wrote:
Hi Anton,
On Thu, 16 Oct 2008 21:12:53 +0400, Anton Vorontsov wrote:
If present the info-archdata is copied into the dev-archdata.
Some (OpenFirmware) platforms need it.
Signed-off-by: Anton Vorontsov [EMAIL PROTECTED]
---
So
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
drivers/misc/Kconfig|9
drivers/misc/Makefile |1
drivers/misc/max9485.c | 105 +++
include/linux/i2c/max9485.h | 39
4 files changed, 154 insertions(+), 0
On Wed, Oct 22, 2008 at 05:03:47AM +0400, Anton Vorontsov wrote:
On Wed, Oct 22, 2008 at 11:29:20AM +1100, Benjamin Herrenschmidt wrote:
But it doesn't work as a module (i.e. OF-specific bits should be
always in-kernel).
Why not ?
If say X driver loads prior to bus-notifier
On Wed, 2008-10-22 at 05:03 +0400, Anton Vorontsov wrote:
If say X driver loads prior to bus-notifier module (where we fill
the platform data), then X.0 device will try to probe w/o platform
data and will fail. The only way to re-probe things is to rmmod X
insmod of_pdata_filler_X insmod X.
On Wed, 2008-10-22 at 05:42 +0400, Anton Vorontsov wrote:
Thinking about it more, I started recalling other issues. The bus
notifier chain doesn't replay previous events, so we also have to
register the notifier before the _devices_ are registered. And this
ruins the whole approach. :-/
On Thu, Oct 16, 2008 at 09:12:56PM +0400, Anton Vorontsov wrote:
For I2C devices we just setting the the node pointer in the archdata.
This is needed so that the other code would know device's node.
Signed-off-by: Anton Vorontsov [EMAIL PROTECTED]
Looks okay to me.
Acked-by: Grant Likely
20 matches
Mail list logo
