From: Nate Case <ncase@xes-inc.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Passing I2C platform_data from device tree to i2c driver
Date: Mon, 03 Nov 2008 17:54:46 -0600 [thread overview]
Message-ID: <1225756486.27415.258.camel@localhost.localdomain> (raw)
Is there a plan for providing a way to set pdata for an I2C chip in a
way that could be shared across all OF platforms?
For example, the pca953x I2C GPIO driver requires that pdata != NULL so
it can get the gpio_base field. It can also take in a default 'invert'
value to initialize a chip register with. Currently, there's no obvious
way to get this to work on PowerPC without hardcoding things in the
arch/powerpc/platforms/*.c file.
On ARM platforms, they currently handle this by declaring
I2C_BOARD_INFO() in their board-specific files. For OF platforms, I
think the obvious choice would be to specify platform data in the device
tree. We already register I2C devices automatically as found in the
device tree (see drivers/of/of_i2c.c), but this registration method does
not provide any way to set platform_data.
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?
--
Nate Case <ncase@xes-inc.com>
next reply other threads:[~2008-11-03 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 23:54 Nate Case [this message]
2008-11-06 18:54 ` Passing I2C platform_data from device tree to i2c driver Scott Wood
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=1225756486.27415.258.camel@localhost.localdomain \
--to=ncase@xes-inc.com \
--cc=linuxppc-dev@ozlabs.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).