From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH v3 00/21] eeprom: at24: Add OF device ID table Date: Wed, 19 Apr 2017 19:12:42 -0500 Message-ID: <20170420001242.vl3sga2bd65jlaoi@rob-hp-laptop> References: <20170414010445.21727-1-javier@osg.samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20170414010445.21727-1-javier@osg.samsung.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Javier Martinez Canillas Cc: Mark Rutland , Andrew Lunn , Wolfram Sang , Tony Lindgren , Catalin Marinas , Will Deacon , linux-kernel@vger.kernel.org, Masahiro Yamada , Alexandre Belloni , linux-i2c@vger.kernel.org, Hongtao Jia , Russell King , Mark Jackson , Herbert Xu , Horia =?utf-8?Q?Geant=C4=83?= , Michael Ellerman , Magnus Damm , Michal Simek , Andy Shevchenko , linux-arm-kernel@lists.infradead.org, Benjamin Herrenschmidt , Jason Cooper , Sebastian List-Id: devicetree@vger.kernel.org On Thu, Apr 13, 2017 at 10:04:24PM -0300, Javier Martinez Canillas wrote: > Hello Wolfram, > > This series is a follow-up to patch [0] that added an OF device ID table > to the at24 EEPROM driver. As you suggested [1], this version instead of > adding entries for every used tuple, only adds a single > entry for each chip type using the "atmel" vendor as a generic fallback. > > The first patch adds the OF device ID table for the at24 driver and the > next patches adds a generic fallback compatible string to each DTS that > defines a compatible I2C EEPROM device node. > > Patches can be applied independently since the DTS change without the > driver change is a no-op and the OF device table won't be used without > the DTS changes. > > [0]: https://lkml.org/lkml/2017/3/14/589 I don't have this patch in my inbox, but the i2c core will still match on compatibles with no vendor prefix? If not, those need to be added to the match table too. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f195.google.com (mail-io0-f195.google.com [209.85.223.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3w7fT93wGpzDqFJ for ; Thu, 20 Apr 2017 10:12:45 +1000 (AEST) Received: by mail-io0-f195.google.com with SMTP id h41so9231892ioi.1 for ; Wed, 19 Apr 2017 17:12:45 -0700 (PDT) Date: Wed, 19 Apr 2017 19:12:42 -0500 From: Rob Herring To: Javier Martinez Canillas Cc: linux-kernel@vger.kernel.org, Wolfram Sang , =?iso-8859-1?Q?Beno=EEt?= Cousson , Stuart Yoder , Sascha Hauer , Gregory Clement , =?iso-8859-1?Q?S=F6ren?= Brinkmann , David Lechner , linux-i2c@vger.kernel.org, Nicolas Ferre , Peter Rosin , Catalin Marinas , Mark Jackson , Fabio Estevam , Simon Horman , Michal Simek , Andy Shevchenko , Alexandre Belloni , Shawn Guo , Will Deacon , Florian Larysch , Magnus Damm , devicetree@vger.kernel.org, Benjamin Herrenschmidt , Sekhar Nori , Scott Wood , Sebastian Hesselbarth , Andrew Lunn , Joachim Eastwood , Herbert Xu , linux-omap@vger.kernel.org, Russell King , linux-arm-kernel@lists.infradead.org, Masahiro Yamada , Michael Ellerman , Jason Cooper , Santosh Shilimkar , linux-renesas-soc@vger.kernel.org, Hongtao Jia , Tony Lindgren , Paul Mackerras , Mark Rutland , Dinh Nguyen , linuxppc-dev@lists.ozlabs.org, Horia =?utf-8?Q?Geant=C4=83?= Subject: Re: [PATCH v3 00/21] eeprom: at24: Add OF device ID table Message-ID: <20170420001242.vl3sga2bd65jlaoi@rob-hp-laptop> References: <20170414010445.21727-1-javier@osg.samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20170414010445.21727-1-javier@osg.samsung.com> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Apr 13, 2017 at 10:04:24PM -0300, Javier Martinez Canillas wrote: > Hello Wolfram, > > This series is a follow-up to patch [0] that added an OF device ID table > to the at24 EEPROM driver. As you suggested [1], this version instead of > adding entries for every used tuple, only adds a single > entry for each chip type using the "atmel" vendor as a generic fallback. > > The first patch adds the OF device ID table for the at24 driver and the > next patches adds a generic fallback compatible string to each DTS that > defines a compatible I2C EEPROM device node. > > Patches can be applied independently since the DTS change without the > driver change is a no-op and the OF device table won't be used without > the DTS changes. > > [0]: https://lkml.org/lkml/2017/3/14/589 I don't have this patch in my inbox, but the i2c core will still match on compatibles with no vendor prefix? If not, those need to be added to the match table too. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: robh@kernel.org (Rob Herring) Date: Wed, 19 Apr 2017 19:12:42 -0500 Subject: [PATCH v3 00/21] eeprom: at24: Add OF device ID table In-Reply-To: <20170414010445.21727-1-javier@osg.samsung.com> References: <20170414010445.21727-1-javier@osg.samsung.com> Message-ID: <20170420001242.vl3sga2bd65jlaoi@rob-hp-laptop> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Apr 13, 2017 at 10:04:24PM -0300, Javier Martinez Canillas wrote: > Hello Wolfram, > > This series is a follow-up to patch [0] that added an OF device ID table > to the at24 EEPROM driver. As you suggested [1], this version instead of > adding entries for every used tuple, only adds a single > entry for each chip type using the "atmel" vendor as a generic fallback. > > The first patch adds the OF device ID table for the at24 driver and the > next patches adds a generic fallback compatible string to each DTS that > defines a compatible I2C EEPROM device node. > > Patches can be applied independently since the DTS change without the > driver change is a no-op and the OF device table won't be used without > the DTS changes. > > [0]: https://lkml.org/lkml/2017/3/14/589 I don't have this patch in my inbox, but the i2c core will still match on compatibles with no vendor prefix? If not, those need to be added to the match table too. Rob