From: Mark Jackson <mpfj@mimc.co.uk>
To: Jean Delvare <khali@linux-fr.org>
Cc: ben-linux@fluff.org, akpm@linux-foundation.org,
i2c@lm-sensors.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [i2c] [PATCH v2] Add support for Dallas DS28CM00 Unique ID chip
Date: Tue, 21 Oct 2008 20:17:48 +0100 [thread overview]
Message-ID: <48FE2ADC.8020203@mimc.co.uk> (raw)
In-Reply-To: <20081021211219.18fb7d84@hyperion.delvare>
Jean Delvare wrote:
> Hi Mark,
>
> On Tue, 21 Oct 2008 19:42:42 +0100, Mark Jackson wrote:
>> Jean Delvare wrote:
>>> On Tue, 21 Oct 2008 15:55:26 +0100, Mark Jackson wrote:
>>>> This patch adds support for the (I2C based) DS28CM00 ID chip.
>>>> (v2 after running through checkpatch)
>>>>
>>>> Signed-off-by: M.Jackson <mpfj@mimc.co.uk>
>>>> ---
>>>> drivers/i2c/chips/Kconfig | 7 ++
>>>> drivers/i2c/chips/Makefile | 1 +
>>>> drivers/i2c/chips/ds28cm00.c | 166 ++++++++++++++++++++++++++++++++++++++++++
>>>> 3 files changed, 174 insertions(+), 0 deletions(-)
>>> Nack. No new drivers under drivers/i2c/chips please, it's going away
>>> soon.
>> Okay ... where should any new drivers be located ?
>
> Depends of what the device does.
> * Hardware monitoring chip drivers go to drivers/hwmon
> * RTC chip drivers go to drivers/rtc
> * I/O expander drivers go to drivers/gpio
> If you can't find a suitable directory under drivers, either create a
> new one if that makes sense, or put your driver under drivers/misc.
Ah, now I understand !! I think drivers/misc is probably a good a place as any,
>>>> +static int ds28cm00_attach_adapter(struct i2c_adapter *adapter);
>>>> +static int ds28cm00_detect(struct i2c_adapter *adapter, int address, int kind);
>>>> +static int ds28cm00_detach_client(struct i2c_client *client);
>>>> +
>>>> +/* This is the driver that will be inserted */
>>>> +static struct i2c_driver ds28cm00_driver = {
>>>> + .driver = {
>>>> + .name = "ds28cm00",
>>>> + },
>>>> + .attach_adapter = ds28cm00_attach_adapter,
>>>> + .detach_client = ds28cm00_detach_client,
>>>> +};
>>> attach_adapter and detach_client are deprecated. Please use probe and
>>> remove instead.
>> Are there any existing chip drivers that use this new method ?
>
> As of 2.6.27-git10: all drivers under drivers/i2c/chips, all i2c
> drivers under drivers/gpio, all i2c drivers under drivers/hwmon, all
> i2c drivers under drivers/rtc, and more.
>
> You may want to take a look at Documentation/i2c/upgrading-clients too.
Okay ... thanks for the pointer.
Mark
next prev parent reply other threads:[~2008-10-21 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 14:55 [PATCH v2] Add support for Dallas DS28CM00 Unique ID chip Mark Jackson
2008-10-21 15:35 ` [i2c] " Jean Delvare
2008-10-21 18:42 ` Mark Jackson
2008-10-21 19:12 ` Jean Delvare
2008-10-21 19:17 ` Mark Jackson [this message]
2008-10-21 19:40 ` Mark Jackson
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=48FE2ADC.8020203@mimc.co.uk \
--to=mpfj@mimc.co.uk \
--cc=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.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