[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABxcv==J_QwoivZ0PRWMoG-weAp7F-LpEXkBxw_9jwH3ENKjsw@mail.gmail.com>
Date: Mon, 10 Jul 2017 09:47:05 +0200
From: Javier Martinez Canillas <javier@...hile0.org>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Linux Kernel <linux-kernel@...r.kernel.org>,
Rob Herring <robh@...nel.org>,
Javier Martinez Canillas <javier@...hile0.org>,
Florian Larysch <fl@...1.de>,
David Lechner <david@...hnology.com>,
Rob Herring <robh+dt@...nel.org>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Catalin Marinas <catalin.marinas@....com>,
Sören Brinkmann <soren.brinkmann@...inx.com>,
Simon Horman <horms@...ge.net.au>,
Michal Simek <michal.simek@...inx.com>,
Dinh Nguyen <dinguyen@...nel.org>,
Russell King <linux@...linux.org.uk>,
Will Deacon <will.deacon@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Sekhar Nori <nsekhar@...com>, Scott Wood <oss@...error.net>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Joachim Eastwood <manabian@...il.com>,
Mark Rutland <mark.rutland@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michael Ellerman <mpe@...erman.id.au>,
Santosh Shilimkar <ssantosh@...nel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Paul Mackerras <paulus@...ba.org>,
Magnus Damm <magnus.damm@...il.com>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Uwe Kleine-König <kernel@...gutronix.de>,
Linux I2C <linux-i2c@...r.kernel.org>
Subject: Re: [RESEND PATCH v5 00/16] eeprom: at24: Add OF device ID table
Hello Wolfram,
On Thu, Jun 15, 2017 at 8:54 PM, Javier Martinez Canillas
<javier@...hile0.org> wrote:
>
> 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 <vendor,device> tuple, only adds a single
> entry for each chip type using the "atmel" vendor as a generic fallback.
>
> The first patch documents in the DT binding what's the correct vendor to
> use and what are the ones that are being deprecated. The second one adds
> the OF device ID table for the at24 driver and the next patches use this
> vendor in the compatible string to each DTS that defines a compatible I2C
> EEPROM device node.
>
> Patches can be applied independently since the DTS changes without driver
> changes are no-op and the OF table won't be used without the DTS changes.
>
> [0]: https://lkml.org/lkml/2017/3/14/589
> [1]: https://lkml.org/lkml/2017/3/15/99
>
Are you planning to pick this series? It has been in the list for
months and were resent many times...
Best regards,
Javier
Powered by blists - more mailing lists