Thread (24 messages) flat view 24 messages, 4 authors, 2007-12-10

Re: [PATCH 0/4] Series to add device tree naming to i2c

From: Olof Johansson <hidden>
Date: 2007-12-04 00:00:58

On Mon, Dec 03, 2007 at 06:52:06PM -0500, Jon Smirl wrote:
On 12/3/07, Olof Johansson [off-list ref] wrote:
quoted
On Mon, Dec 03, 2007 at 04:20:32PM -0500, Jon Smirl wrote:
quoted
The following series implements standard linux module aliasing for i2c modules
It then converts the mpc i2c driver from being a platform driver to an open
firmware one. I2C device names are picked up from the device tree. Module
aliasing is used to translate from device tree names into to linux kernel
names. Several i2c drivers are updated to use the new aliasing.
May I ask why you want to modify the i2c layer instead of keeping the
OF->i2c driver mapping in PPC code? It seems simpler to keep it in the
PPC-specific code, since otherwise you might end up with confused i2c
driver writers that make up their own OF names without knowing for sure
that's what will be used. No?
Audio codecs have the same problem. That table is could end up with
hundreds of entries. The right place to store the mappings is in the
device driver for the device.

A side effect of moving the mappings into the device drivers is that
the correct i2c drivers can be automatically loaded by the kernel.
This lets you make distro CDs with all of the i2c drivers on disk and
the device tree will cause insmod of the correct ones.
Ok, good enough reasons. I'll back out my i2c commits and wait for yours
to settle, then add the pasemi stuff in the same way.

(Whitespace comments still apply).


-Olof
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help