[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZESujO=2BU3jeKiX3Cm+JY2UPEXwGkro75FWa5Gio5YQ@mail.gmail.com>
Date: Tue, 4 Sep 2012 19:27:10 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Arnd Bergmann <arnd@...db.de>,
Alessandro Rubini <rubini@...dd.com>,
Russell King - ARM Linux <linux@....linux.org.uk>
Cc: linux-arm-kernel@...ts.infradead.org,
Lee Jones <lee.jones@...aro.org>,
Rob Herring <robherring2@...il.com>,
Stephen Warren <swarren@...dia.com>,
linus.walleij@...ricsson.com, linux-kernel@...r.kernel.org,
Wolfram Sang <w.sang@...gutronix.de>,
linux-i2c@...r.kernel.org, STEricsson_nomadik_linux@...t.st.com,
devicetree-discuss@...ts.ozlabs.org
Subject: Re: [PATCH 3/3] i2c: nomadik: Add Device Tree support to the Nomadik
I2C driver
On Tue, Sep 4, 2012 at 4:28 PM, Arnd Bergmann <arnd@...db.de> wrote:
> In this particular case, we don't have a single board file providing a
> struct nmk_i2c_controller definition for platform data, so the best way
> to handle this IMHO is to remove the header file with the platform
> data definition, and just encode the defaults in the driver.
Alessandro Rubini is actively working on bridging this (and
other amba_device primecells) to PCI, that is the reason why it
was recently converted to an amba_device. How is he then supposed to
get the proper parameters into the driver? Note that the PCI ID
is no help at all since the parameters depend on what is connected
to the I2C bus, not on what it itself is connected to. Isn't platform data
used in such cases?
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists