linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] i2c: nomadik: Add Device Tree support to the Nomadik I2C driver
Date: Wed, 5 Sep 2012 07:41:07 +0100	[thread overview]
Message-ID: <20120905064106.GA4233@gmail.com> (raw)
In-Reply-To: <CACRpkdZESujO=2BU3jeKiX3Cm+JY2UPEXwGkro75FWa5Gio5YQ@mail.gmail.com>

On Tue, Sep 04, 2012 at 07:27:10PM +0200, Linus Walleij wrote:
> On Tue, Sep 4, 2012 at 4:28 PM, Arnd Bergmann <arnd@arndb.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?

So why can't Alessandro continue to use Platform Data in the normal way?

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2012-09-05  6:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 15:01 [PATCH 1/3] ARM: ux500: Add i2c configurations to the Device Tree for DB8500 based devices Lee Jones
2012-08-23 15:01 ` [PATCH 2/3] Documentation: Device Tree binding information for i2c-nomadik driver Lee Jones
2012-08-23 15:01 ` [PATCH 3/3] i2c: nomadik: Add Device Tree support to the Nomadik I2C driver Lee Jones
2012-08-27 23:42   ` Linus Walleij
2012-08-31 10:36     ` Lee Jones
2012-08-31 11:22   ` Wolfram Sang
2012-08-31 12:04     ` Lee Jones
2012-08-31 12:23     ` Lee Jones
2012-09-03  9:22       ` Linus Walleij
2012-09-03  9:44         ` Wolfram Sang
2012-09-03  9:50           ` Lee Jones
2012-09-03 10:07           ` Lee Jones
2012-09-03 11:07             ` Linus Walleij
2012-09-03 11:11               ` Lee Jones
2012-09-03 11:32               ` Lee Jones
2012-09-03 11:58                 ` Linus Walleij
2012-09-03 12:34                   ` Lee Jones
2012-09-03 13:19                     ` Linus Walleij
2012-09-03 13:28                       ` Lee Jones
2012-09-03 14:33                   ` Stephen Warren
2012-09-03 14:35                     ` Linus Walleij
2012-09-03 15:09                       ` Rob Herring
2012-09-03 15:20                         ` Lee Jones
2012-09-04 14:28                           ` Arnd Bergmann
2012-09-04 17:27                             ` Linus Walleij
2012-09-05  6:41                               ` Lee Jones [this message]
2012-09-05  6:53                                 ` Linus Walleij
2012-09-04 17:35                             ` Alessandro Rubini
2012-09-05  7:33     ` Lee Jones
2012-09-05  8:22       ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120905064106.GA4233@gmail.com \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).