From: Jon Smirl <jonsmirl@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Linux PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: Using archaic I2C with OF
Date: Fri, 1 May 2009 10:55:53 -0400 [thread overview]
Message-ID: <9e4733910905010755g595d686fmf075a40d6012e3fc@mail.gmail.com> (raw)
In-Reply-To: <49FB0C3B.3000209@mlbassoc.com>
On Fri, May 1, 2009 at 10:50 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> Jon Smirl wrote:
>> On Fri, May 1, 2009 at 10:39 AM, Jon Smirl <jonsmirl@gmail.com> wrote:
>>> On Fri, May 1, 2009 at 9:04 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> I'd like to use an existing I2C driver (a touchscreen device)
>>>> with my 834x based platform. =A0How do I arrange to provide
>>>> platform data (i2c_client->dev.platform_data) from my OF world?
>>> It is easier to convert the i2c driver to work in the current model.
>>
>> All in-tree drivers have already been converted.
>
> I'm looking at drivers/input/touchscreen/tsc2007.c (the one I need)
> from Kumar's 'next' tree. =A0It most definitely still uses the old
> model.
>
> Can you suggest another place to look?
Post this on the i2c list. Jean has made an effort to convert all
drivers. He must have missed that one.
>
> --
> ------------------------------------------------------------
> Gary Thomas =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0Consulting for the
> MLB Associates =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0Embedded world
> ------------------------------------------------------------
>
--=20
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2009-05-01 15:03 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 [this message]
2009-05-01 16:04 ` Wolfram Sang
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=9e4733910905010755g595d686fmf075a40d6012e3fc@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=gary@mlbassoc.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).