From: Gary Thomas <gary@mlbassoc.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Linux PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: Using archaic I2C with OF
Date: Mon, 04 May 2009 06:19:14 -0600 [thread overview]
Message-ID: <49FEDD42.4030806@mlbassoc.com> (raw)
In-Reply-To: <20090501160403.GA7943@pengutronix.de>
Wolfram Sang wrote:
>> Post this on the i2c list. Jean has made an effort to convert all
>> drivers. He must have missed that one.
>>
>
> What Jean did was converting all drivers who used the legacy i2c-binding to use
> the new binding which is a lot better suited to the driver model. The above
> mentioned driver already uses the new binding.
>
> The problem coming up here is another issue and also long standing and not yet
> solved. There are drivers which require platform_data with function pointers.
> You cannot encode function pointers to the device tree.
>
> One solution is to create a custom driver for your board with the needed
> specific function and create a platform device from there. Sometimes it
> works to add a bit more info to the device tree (e.g. some gpios) and
> parse it via an of_wrapper around the platform driver.
>
So somehow, I need to create a platform driver, possibly inside an
of_wrapper, which
eventually instantiates an I2C device on a particular bus, with my
specific platform
data.
Sorry, but I'm lost here. How do I untangle this maze of twisty little
passages?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2009-05-04 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 13:04 Using archaic I2C with OF Gary Thomas
2009-05-01 14:39 ` Jon Smirl
2009-05-01 14:39 ` Jon Smirl
2009-05-01 14:50 ` Gary Thomas
2009-05-01 14:55 ` Jon Smirl
2009-05-01 16:04 ` Wolfram Sang
2009-05-01 16:08 ` Gary Thomas
2009-05-04 12:19 ` Gary Thomas [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=49FEDD42.4030806@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=w.sang@pengutronix.de \
/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).