From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Daney Subject: Re: [PATCH 2/2] misc/at25: Add an .id_table to at25 to facilitate driver loading and binding. Date: Mon, 17 Sep 2012 10:06:41 -0700 Message-ID: <505758A1.1050205@gmail.com> References: <1345662238-15211-1-git-send-email-ddaney.cavm@gmail.com> <1345662238-15211-3-git-send-email-ddaney.cavm@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: "devicetree-discuss" To: Ivo Sieben Cc: David Daney , devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Rob Herring List-Id: devicetree@vger.kernel.org On 09/17/2012 12:49 AM, Ivo Sieben wrote: > Hi, > > 2012/8/22 David Daney : >> From: David Daney >> >> /*-------------------------------------------------------------------------*/ >> +static const struct spi_device_id at25_id[] = { >> + {"at25", 0}, >> + {"m95256", 0}, >> + { } >> +}; >> +MODULE_DEVICE_TABLE(spi, at25_id); > > I use this driver for the ST M95040, M95020 & M95010 eeprom devices. > So wouldn't it be better to use the "famliy" name for these chips > ("m95" instead of "m95256"). > These are matched against device tree compatible properties. You could propose adding a generic "st,95xxx" compatible property and adding that to the at25_id list. But I don't think we want to remove "m95256", as we have deployed devices using this binding. David Daney