From: Rob Herring <robh@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: "Mark Brown" <broonie@kernel.org>,
"Cezary Rojewski" <cezary.rojewski@intel.com>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"\"Amadeusz Sławiński\"" <amadeuszx.slawinski@linux.intel.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 14/15] ASoC: dt-bindings: renesas,rsnd.yaml: add common port-def
Date: Fri, 14 Jul 2023 08:42:45 -0600 [thread overview]
Message-ID: <20230714144245.GA3492124-robh@kernel.org> (raw)
In-Reply-To: <87lefn8gh9.wl-kuninori.morimoto.gx@renesas.com>
On Tue, Jul 11, 2023 at 09:00:18AM +0900, Kuninori Morimoto wrote:
>
> Hi Rob
>
> Thank you for reviewing
>
>
> > > diff --git a/Documentation/devicetree/bindings/sound/renesas,rsnd.yaml b/Documentation/devicetree/bindings/sound/renesas,rsnd.yaml
> > > index 8a821dec9526..d9808b130e8d 100644
> > > --- a/Documentation/devicetree/bindings/sound/renesas,rsnd.yaml
> > > +++ b/Documentation/devicetree/bindings/sound/renesas,rsnd.yaml
> > > @@ -9,6 +9,20 @@ title: Renesas R-Car Sound Driver
> > > maintainers:
> > > - Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > >
> > > +definitions:
> >
> > $defs
>
> Hmm... many drivers are using "definitions" ?
Patches welcome to change them. I don't think it's many (not counting
types.yaml). Use of "definitions" or "$defs" is an exception.
> This kind of indication is very confusable...
"definitions" was common convention in early json-schema. "$defs" was
added to the specification to standardize it.
> > > port:
> > > - $ref: audio-graph-port.yaml#/definitions/port-base
> > > - unevaluatedProperties: false
> > > - patternProperties:
> > > - "^endpoint(@[0-9a-f]+)?":
> > > - $ref: audio-graph-port.yaml#/definitions/endpoint-base
> > > - properties:
> > > - playback:
> > > - $ref: /schemas/types.yaml#/definitions/phandle-array
> > > - capture:
> > > - $ref: /schemas/types.yaml#/definitions/phandle-array
> > > - unevaluatedProperties: false
> > > + $ref: "#/definitions/port-def"
> >
> > It would be better if users just always used "ports { port {}; };" even
> > in the single port case.
>
> "ports" support is added, we can't modify past.
I don't understand. The graph APIs all work the same with or without
'ports'. Changing the DT shouldn't affect the ABI.
Rob
next prev parent reply other threads:[~2023-07-14 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mt04o96f.wl-kuninori.morimoto.gx@renesas.com>
2023-07-10 1:21 ` [PATCH v2 14/15] ASoC: dt-bindings: renesas,rsnd.yaml: add common port-def Kuninori Morimoto
2023-07-10 15:19 ` Rob Herring
2023-07-11 0:00 ` Kuninori Morimoto
2023-07-14 14:42 ` Rob Herring [this message]
2023-07-19 0:11 ` Kuninori Morimoto
2023-07-19 23:36 ` Kuninori Morimoto
2023-08-04 17:56 ` Rob Herring
2023-07-10 1:21 ` [PATCH v2 15/15] ASoC: dt-bindings: renesas,rsnd.yaml: enable multi ports for multi Component support Kuninori Morimoto
2023-07-10 15:23 ` Rob Herring
2023-07-11 0:05 ` Kuninori Morimoto
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=20230714144245.GA3492124-robh@kernel.org \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=pierre-louis.bossart@linux.intel.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).