devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@dowhile0.org>
To: Rob Herring <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Wolfram Sang <wsa@the-dreams.de>,
	Simon Horman <horms@verge.net.au>, Sekhar Nori <nsekhar@ti.com>,
	David Lechner <david@lechnology.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v4 01/20] dt-bindings: i2c: eeprom: Document vendor to be used and deprecated ones
Date: Tue, 23 May 2017 15:52:36 +0200	[thread overview]
Message-ID: <CABxcv=kL6E61FcTGDDHYD0mmk_yawroxFt+khQ7a7K++DHqioQ@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqLrdyUW=h9+SMc+5Eu558KSVXuS-ABD3-kv=Q02X5TY=A@mail.gmail.com>

Hello Rob,

On Tue, May 23, 2017 at 3:48 PM, Rob Herring <robh@kernel.org> wrote:
> On Mon, May 22, 2017 at 9:01 AM, Javier Martinez Canillas
> <javier@dowhile0.org> wrote:
>> The at24 driver allows to register I2C EEPROM chips using different vendor
>> and devices, but the I2C subsystem does not take the vendor into account
>> when matching using the I2C table since it only has device entries.
>>
>> But when matching using an OF table, both the vendor and device has to be
>> taken into account, so the exact list of supported <vendor,device> tuples
>> should be documented in the Device Tree binding document.
>>
>> But there is no need to have different manufacturers if the EEPROM chips
>> from different manufacturers are really compatible, so matching using a
>> single "atmel" vendor is enough for all chip types.
>>
>> Document in the Device Tree binding that the "atmel" manufacturer should
>> be used, and also document the manufacturers that have been deprecated.
>>
>> Suggested-by: Wolfram Sang <wsa@the-dreams.de>
>> Suggested-by: Rob Herring <robh@kernel.org>
>> Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
>>
>> ---
>>
>> Changes in v4:
>> - Document the manufacturers that have been deprecated (Rob Herring).
>
> I don't think that's what I said.
>
>>
>> Changes in v3: None
>> Changes in v2: None
>>
>>  Documentation/devicetree/bindings/eeprom/eeprom.txt | 14 ++++----------
>>  1 file changed, 4 insertions(+), 10 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/eeprom/eeprom.txt b/Documentation/devicetree/bindings/eeprom/eeprom.txt
>> index 5696eb508e95..121499252179 100644
>> --- a/Documentation/devicetree/bindings/eeprom/eeprom.txt
>> +++ b/Documentation/devicetree/bindings/eeprom/eeprom.txt
>> @@ -2,22 +2,16 @@ EEPROMs (I2C)
>>
>>  Required properties:
>>
>> -  - compatible : should be "<manufacturer>,<type>", like these:
>> +  - compatible : should be "atmel,<type>", like these:
>>
>>         "atmel,24c00", "atmel,24c01", "atmel,24c02", "atmel,24c04",
>>         "atmel,24c08", "atmel,24c16", "atmel,24c32", "atmel,24c64",
>>         "atmel,24c128", "atmel,24c256", "atmel,24c512", "atmel,24c1024"
>>
>> -       "catalyst,24c32"
>> +       The following manufacturers values have been deprecated:
>> +       "at", "at24", "catalyst", "microchip", "nxp", "ramtron", "renesas", "st"
>
> Only at and at24 should be deprecated.
>

Yes, I also fixed that on v5. Could you please take a look to that
version instead?

Best regards,
Javier

  reply	other threads:[~2017-05-23 13:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 14:01 [PATCH v4 00/20] eeprom: at24: Add OF device ID table Javier Martinez Canillas
2017-05-22 14:01 ` [PATCH v4 03/20] ARM: dts: omap: Add generic compatible string for I2C EEPROM Javier Martinez Canillas
2017-05-22 14:01 ` [PATCH v4 04/20] ARM: dts: turris-omnia: " Javier Martinez Canillas
2017-05-22 14:01 ` [PATCH v4 05/20] ARM: dts: efm32: " Javier Martinez Canillas
2017-05-22 14:01 ` [PATCH v4 08/20] ARM: dts: lpc18xx: " Javier Martinez Canillas
2017-05-22 14:01 ` [PATCH v4 09/20] ARM: dts: r7s72100: " Javier Martinez Canillas
2017-05-22 14:01 ` [PATCH v4 10/20] ARM: dts: koelsch: " Javier Martinez Canillas
2017-05-22 14:02 ` [PATCH v4 13/20] ARM: dts: zynq: " Javier Martinez Canillas
     [not found] ` <20170522140208.24652-1-javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org>
2017-05-22 14:01   ` [PATCH v4 01/20] dt-bindings: i2c: eeprom: Document vendor to be used and deprecated ones Javier Martinez Canillas
     [not found]     ` <20170522140208.24652-2-javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org>
2017-05-23 13:48       ` Rob Herring
2017-05-23 13:52         ` Javier Martinez Canillas [this message]
2017-05-22 14:01   ` [PATCH v4 06/20] ARM: dts: imx: Add generic compatible string for I2C EEPROM Javier Martinez Canillas
2017-05-22 14:01   ` [PATCH v4 07/20] ARM: dts: keystone: " Javier Martinez Canillas
2017-05-22 14:01   ` [PATCH v4 11/20] ARM: dts: socfpga: " Javier Martinez Canillas
2017-05-22 14:02   ` [PATCH v4 12/20] ARM: dts: uniphier: " Javier Martinez Canillas
2017-05-22 14:02   ` [PATCH v4 14/20] arm64: dts: ls1043a: " Javier Martinez Canillas
2017-05-22 14:02   ` [PATCH v4 15/20] arm64: zynqmp: " Javier Martinez Canillas
2017-05-22 14:02   ` [PATCH v4 16/20] powerpc/5200: " Javier Martinez Canillas
2017-05-22 14:02   ` [PATCH v4 17/20] powerpc/fsl: " Javier Martinez Canillas
2017-05-22 14:02   ` [PATCH v4 19/20] powerpc/83xx: " Javier Martinez Canillas
     [not found]     ` <20170522140208.24652-20-javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org>
2017-05-23 13:42       ` Rob Herring
     [not found]         ` <CAL_JsqLGC9sh9jhwtCHu1NE2z85cZh0CVXuMc9aohzCoxE_4fg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-23 13:49           ` Javier Martinez Canillas
2017-05-22 14:02 ` [PATCH v4 18/20] powerpc/512x: " Javier Martinez Canillas
2017-05-22 14:02 ` [PATCH v4 20/20] powerpc/44x: " Javier Martinez Canillas
2017-05-22 14:23 ` [PATCH v4 00/20] eeprom: at24: Add OF device ID table Geert Uytterhoeven
2017-05-22 14:26   ` Rob Herring
2017-05-22 14:46     ` Javier Martinez Canillas
2017-05-22 16:52       ` Rob Herring
2017-05-22 17:15         ` Javier Martinez Canillas
2017-05-22 19:30           ` Geert Uytterhoeven
2017-05-22 19:39             ` Javier Martinez Canillas

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='CABxcv=kL6E61FcTGDDHYD0mmk_yawroxFt+khQ7a7K++DHqioQ@mail.gmail.com' \
    --to=javier@dowhile0.org \
    --cc=david@lechnology.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nsekhar@ti.com \
    --cc=robh@kernel.org \
    --cc=wsa@the-dreams.de \
    /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;
as well as URLs for NNTP newsgroup(s).