From: Wolfram Sang <w.sang@pengutronix•de>
To: Jon Smirl <jonsmirl@gmail•com>
Cc: Linux PPC Development <linuxppc-dev@ozlabs•org>,
Gary Thomas <gary@mlbassoc•com>
Subject: Re: Using archaic I2C with OF
Date: Fri, 1 May 2009 18:04:03 +0200 [thread overview]
Message-ID: <20090501160403.GA7943@pengutronix.de> (raw)
In-Reply-To: <9e4733910905010755g595d686fmf075a40d6012e3fc@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
> 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.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-01 16:04 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 [this message]
2009-05-01 16:08 ` Gary Thomas
2009-05-04 12:19 ` Gary Thomas
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=20090501160403.GA7943@pengutronix.de \
--to=w.sang@pengutronix$(echo .)de \
--cc=gary@mlbassoc$(echo .)com \
--cc=jonsmirl@gmail$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/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