From: Javier Martinez Canillas <javier@dowhile0.org>
To: Rob Herring <robh@kernel.org>
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
Simon Horman <horms@verge.net.au>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sekhar Nori <nsekhar@ti.com>,
David Lechner <david@lechnology.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 01/21] dt-bindings: i2c: eeprom: Document manufacturer used as generic fallback
Date: Mon, 15 May 2017 12:48:03 +0200 [thread overview]
Message-ID: <CABxcv=mq7xOKL5WXG+qkhwQCiOuN4J=WWRzKnq0DTx9vxinOpQ@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqL-DRPBCeeNYzf9YBDijFc9s8ZBVQ-5PNkHxuTSYbHnew@mail.gmail.com>
Hello Rob,
Thanks for the feedback and sorry for the delayed response (I've been
moving to a new country so didn't have too much time to answer
emails).
On Thu, Apr 20, 2017 at 1:35 AM, Rob Herring <robh@kernel.org> wrote:
> On Wed, Apr 19, 2017 at 6:27 PM, Rob Herring <robh@kernel.org> wrote:
>> On Thu, Apr 13, 2017 at 10:04:25PM -0300, Javier Martinez Canillas wrote:
[snip]
>>>
>>> If there is no specific driver for <manufacturer>, a generic
>>> - driver based on <type> is selected. Possible types are:
>>> + driver based on <type> and manufacturer "atmel" is selected.
>>> + Possible types are:
>>
>> This isn't quite right. What the driver does isn't really relevant to
>> the binding.
>>
>> These types with no vendor are used as the compatible string, so we have
>> to allow them. But it should be clear that no vendor is deprecated.
>> Ironically, it is a lot of Atmel boards that do this.
>>
>> We should also explicitly list what are valid manufacturers. We also
>> have "at" as a vendor prefix which perhaps we should explicitly say is
>> deprecated.
>
> I should perhaps look at the rest of the series before replying..
>
> Based on that, the only comment that applies is listing the
> manufacturers that are valid. From a DT perspective, I should not have
> to know what the OS driver supports. If the device is compatible with
> atmel, then that is required. If not, then the specific manufacturer's
> compatible alone is enough and the OS has to match to that.
>
Got it, I'll re-spin the series probably this week adding that
information to the DT binding doc.
> Rob
Best regards,
Javier
next prev parent reply other threads:[~2017-05-15 10:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170414010445.21727-1-javier@osg.samsung.com>
2017-04-14 1:04 ` [PATCH v3 01/21] dt-bindings: i2c: eeprom: Document manufacturer used as generic fallback Javier Martinez Canillas
2017-04-19 23:27 ` Rob Herring
2017-04-19 23:35 ` Rob Herring
2017-05-15 10:48 ` Javier Martinez Canillas [this message]
2017-04-14 1:04 ` [PATCH v3 02/21] eeprom: at24: Add OF device ID table Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 03/21] ARM: dts: omap: Add generic compatible string for I2C EEPROM Javier Martinez Canillas
2017-04-14 14:17 ` Tony Lindgren
2017-04-19 23:56 ` Rob Herring
2017-05-15 10:55 ` Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 04/21] ARM: dts: turris-omnia: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 05/21] ARM: dts: at91: " Javier Martinez Canillas
2017-05-15 9:32 ` Alexandre Belloni
2017-04-14 1:04 ` [PATCH v3 06/21] ARM: dts: efm32: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 07/21] ARM: dts: imx: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 08/21] ARM: dts: keystone: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 09/21] ARM: dts: lpc18xx: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 10/21] ARM: dts: r7s72100: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 11/21] ARM: dts: koelsch: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 12/21] ARM: dts: socfpga: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 13/21] ARM: dts: uniphier: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 14/21] ARM: dts: zynq: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 15/21] arm64: dts: ls1043a: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 16/21] arm64: zynqmp: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 17/21] powerpc/5200: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 18/21] powerpc/fsl: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 19/21] powerpc/512x: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 20/21] powerpc/83xx: " Javier Martinez Canillas
2017-04-14 1:04 ` [PATCH v3 21/21] powerpc/44x: " 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=mq7xOKL5WXG+qkhwQCiOuN4J=WWRzKnq0DTx9vxinOpQ@mail.gmail.com' \
--to=javier@dowhile0.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=javier@osg.samsung.com \
--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).