From: Scott Wood <scottwood@freescale•com>
To: Nate Case <ncase@xes-inc•com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs•org>
Subject: Re: Passing I2C platform_data from device tree to i2c driver
Date: Thu, 6 Nov 2008 12:54:33 -0600 [thread overview]
Message-ID: <20081106185433.GA26616@loki.buserror.net> (raw)
In-Reply-To: <1225756486.27415.258.camel@localhost.localdomain>
On Mon, Nov 03, 2008 at 05:54:46PM -0600, Nate Case wrote:
> Of course, I could put some code in my board specific file to parse the
> device tree properties and set pdata accordingly, but this hardly seems
> ideal. After all, the device tree bindings -> pdata translation itself
> does not have to be board-specific.
>
> Basically, I think we need to have some common code somewhere that does
> the task of populating platform_data for a specific I2C chip based on a
> device tree node -- similarly to how we register the I2C devices
> already. Is anyone working on this? Did anyone have anything else in
> mind?
It should be fairly straightforward to add an optional function pointer to
the i2c device table that turns the device tree properties into platform
data.
-Scott
prev parent reply other threads:[~2008-11-06 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 23:54 Passing I2C platform_data from device tree to i2c driver Nate Case
2008-11-06 18:54 ` Scott Wood [this message]
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=20081106185433.GA26616@loki.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=ncase@xes-inc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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