devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: Create DT bindings for [PS]ATA controllers
Date: Tue, 31 Dec 2019 18:56:24 +0100	[thread overview]
Message-ID: <CACRpkdbR3TTiNqU8g54M4N4=N8yiV2UreFKoV0LffYUxZEChJw@mail.gmail.com> (raw)
In-Reply-To: <41b527ba-003d-425b-5e59-43cdd8c778e2@cogentembedded.com>

On Tue, Dec 31, 2019 at 6:46 PM Sergei Shtylyov
<sergei.shtylyov@cogentembedded.com> wrote:
> On 12/31/2019 08:24 PM, Linus Walleij wrote:

> > +properties:
> > +  $nodename:
> > +    pattern: "^[ps]ata-controller(@.*)?$"
>
>    I thought the DT spec has long ago standardized the node name as "ide" and "sata"?

I'm not 100% sure (Rob can answer) but I have *half-guessed* that the process
so far has been that when we define a schema for some generic node name
we also invent some new generic node name like this, or else all the old DTS
files people have will generate (lots of) errors.

The DTS files can then opt in to the schema by simply renaming its nodes
in accordance: "ide" -> "pata-controller", "sata" -> "sata-controller"
(I have such a patch for the Gemini that I made this for.)

If I'm wrong I'll switch to to ide@ and sata@.

Rob?

Yours,
Linus Walleij

  reply	other threads:[~2019-12-31 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31 17:24 [PATCH 1/2] dt-bindings: Create DT bindings for [PS]ATA controllers Linus Walleij
2019-12-31 17:24 ` [PATCH 2/2] dt-bindings: Convert Faraday FTIDE010 to DT schema Linus Walleij
2019-12-31 19:14   ` Rob Herring
2019-12-31 17:46 ` [PATCH 1/2] dt-bindings: Create DT bindings for [PS]ATA controllers Sergei Shtylyov
2019-12-31 17:56   ` Linus Walleij [this message]
2019-12-31 18:30     ` Rob Herring
2019-12-31 18:44 ` Rob Herring
2020-01-06  1:16   ` Linus Walleij

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='CACRpkdbR3TTiNqU8g54M4N4=N8yiV2UreFKoV0LffYUxZEChJw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=axboe@kernel.dk \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    /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).