Message-ID: <48FE3017.4080009@mimc.co.uk>
Date: Tue, 21 Oct 2008 20:40:07 +0100
From: Mark Jackson <mpfj@mimc.co.uk>
Organization: Mercury IMC Ltd
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Jean Delvare <khali@linux-fr.org>
CC: i2c@lm-sensors.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [i2c] [PATCH v2] Add support for Dallas DS28CM00 Unique ID chip
References: <48FDED5E.5080605@mimc.co.uk>	<20081021173505.2f7673e2@hyperion.delvare>	<48FE22A2.7030604@mimc.co.uk> <20081021211219.18fb7d84@hyperion.delvare> <48FE2ADC.8020203@mimc.co.uk>
In-Reply-To: <48FE2ADC.8020203@mimc.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1119
Lines: 31

Mark Jackson wrote:
> Jean Delvare wrote:
>> Hi Mark,
>>
>> On Tue, 21 Oct 2008 19:42:42 +0100, Mark Jackson wrote:
>>> Jean Delvare wrote:
>>>> 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,

In fact, I now realise that the device is *really* just a read-only eeprom.

So I'm guessing I don't need a custom driver, I can just use the existing
"at24" driver.

Ho hum ...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/