From: "Bryan Wu" <cooloney.lkml@gmail.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: bryan.wu@analog.com, Andrey Panin <pazke@donpac.ru>,
Roel Kluin <12o3l@tiscali.nl>,
"Ahmed S. Darwish" <darwish.07@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@atrey.karlin.mff.cuni.cz,
linux-joystick@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH try #4] Input/Joystick Driver: add support AD7142 joystick driver
Date: Wed, 17 Oct 2007 23:35:49 +0800 [thread overview]
Message-ID: <386072610710170835j20d88feej2b107c8e8b686e89@mail.gmail.com> (raw)
In-Reply-To: <20071017160702.3316fc24@hyperion.delvare>
On 10/17/07, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Bryan,
>
> On Wed, 17 Oct 2007 15:12:00 +0800, Bryan Wu wrote:
> > Subject: [PATCH try #4] Input/Joystick Driver: add support AD7142 joystick driver
>
> This driver is a good candidate for the new-style i2c infrastructure.
> Instead of letting i2c-core probe for the device on all available I2C
> buses, you would explicitly instantiate it from platform data. In
> practice this would mean:
> * Declare the ad7142 in platform data.
> * Call i2c_register_board_info() on that data.
> * In your ad7142 driver, implement .probe and .remove instead
> of .attach_adapter and .detach_client.
>
I would like to rewrite it by using new-style i2c infrastructure.
But it will take some time. If I meet some problem, hope can get some advice
from you and the community.
> Of course this assumes that the underlying bus driver is also new-style
> ready (i.e. it uses i2c_add_numbered_adapter() instead of
> i2c_add_adapter()), and that you know in advance when the AD7142 is
> there or not. I hope this is the case?
>
Oh, currently i2c-bfin-twi driver is using the old-style code.
> Using a new-style i2c driver is especially important if the device
> can't be detected.
>
> Also see my i2c-related comments inline.
>
I will fix all the issues and try to pass our Blackfin AD7142 Joystick testcase.
and resubmit a patch.
Thanks
-Bryan
[!snip!]
next prev parent reply other threads:[~2007-10-17 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 7:12 [PATCH try #4] Input/Joystick Driver: add support AD7142 joystick driver Bryan Wu
2007-10-17 14:07 ` Jean Delvare
2007-10-17 15:35 ` Bryan Wu [this message]
2007-10-17 19:14 ` Robin Getz
2007-10-17 20:04 ` Jean Delvare
2007-10-17 16:12 ` Dmitry Torokhov
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=386072610710170835j20d88feej2b107c8e8b686e89@mail.gmail.com \
--to=cooloney.lkml@gmail.com \
--cc=12o3l@tiscali.nl \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=darwish.07@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=khali@linux-fr.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-joystick@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@donpac.ru \
/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).