From: Jerome Brunet <jbrunet@baylibre.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
stephan@gerhold.net, linux-kernel@vger.kernel.org,
Sameer Pujar <spujar@nvidia.com>,
lgirdwood@gmail.com, jonathanh@nvidia.com, broonie@kernel.org,
thierry.reding@gmail.com, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 1/3] ASoC: Add json-schema documentation for sound-name-prefix
Date: Fri, 03 Sep 2021 10:29:37 +0200 [thread overview]
Message-ID: <1jk0jyt617.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <YTElQBgwF6xBFH9l@robh.at.kernel.org>
On Thu 02 Sep 2021 at 14:25, Rob Herring <robh@kernel.org> wrote:
> On Thu, Sep 02, 2021 at 02:47:27PM +0200, Jerome Brunet wrote:
>>
>> On Thu 02 Sep 2021 at 11:23, Sameer Pujar <spujar@nvidia.com> wrote:
>>
>> > The 'sound-name-prefix' is used to prepend suitable strings to a
>> > component widgets or controls. This is helpful when there are
>> > multiple instances of the same component. Add relevant json-schema
>> > and is inspired from sound-name-prefix.txt documentation.
>> >
>> > Signed-off-by: Sameer Pujar <spujar@nvidia.com>
>> > Cc: Jerome Brunet <jbrunet@baylibre.com>
>> > Cc: Rob Herring <robh+dt@kernel.org>
>> > ---
>> > .../devicetree/bindings/sound/name-prefix.yaml | 35 ++++++++++++++++++++++
>> > 1 file changed, 35 insertions(+)
>> > create mode 100644 Documentation/devicetree/bindings/sound/name-prefix.yaml
>> >
>> > diff --git a/Documentation/devicetree/bindings/sound/name-prefix.yaml b/Documentation/devicetree/bindings/sound/name-prefix.yaml
>> > new file mode 100644
>> > index 00000000..b58cc9e
>> > --- /dev/null
>> > +++ b/Documentation/devicetree/bindings/sound/name-prefix.yaml
>> > @@ -0,0 +1,35 @@
>> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> > +%YAML 1.2
>> > +---
>> > +$id: http://devicetree.org/schemas/sound/name-prefix.yaml#
>> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> > +
>> > +title: Component sound name prefix
>> > +
>> > +maintainers:
>> > + - Jerome Brunet <jbrunet@baylibre.com>
>>
>> Since this file is referenced using "AllOf", am I going to be listed as
>> maintainer of all the drivers using the property below ? I'm not sure I
>> want that ... :P
>
> No. That's not how it works. You're maintainer of files that list you as
> maintainer.
Thanks for clarifying.
You can ignore my comment then Sameer.
>
>> Maybe it would be better to drop the above ?
>>
>> > +
>> > +properties:
>> > + sound-name-prefix:
>> > + $ref: /schemas/types.yaml#/definitions/string
>> > + description: |
>> > + Card implementing the routing property define the connection between
>> > + audio components as list of string pair. Component using the same
>> > + sink/source names may use this property to prepend the name of their
>> > + sinks/sources with the provided string.
>> > +
>> > +additionalProperties: true
>> > +
>> > +examples:
>> > + - |
>> > + analog-amplifier@0 {
>> > + compatible = "simple-audio-amplifier";
>> > + sound-name-prefix = "FRONT";
>> > + };
>> > +
>> > + analog-amplifier@1 {
>> > + compatible = "simple-audio-amplifier";
>> > + sound-name-prefix = "BACK";
>> > + };
>> > +
>> > +...
>>
>>
next prev parent reply other threads:[~2021-09-03 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 5:53 [PATCH v2 0/3] Convert name-prefix doc to json-schema Sameer Pujar
2021-09-02 5:53 ` [PATCH v2 1/3] ASoC: Add json-schema documentation for sound-name-prefix Sameer Pujar
2021-09-02 12:03 ` Rob Herring
2021-09-02 19:27 ` Rob Herring
2021-09-02 12:47 ` Jerome Brunet
2021-09-02 16:22 ` Sameer Pujar
2021-09-02 19:25 ` Rob Herring
2021-09-03 8:29 ` Jerome Brunet [this message]
2021-09-02 5:53 ` [PATCH v2 2/3] ASoC: Use schema reference " Sameer Pujar
2021-09-02 19:28 ` Rob Herring
2021-09-02 5:53 ` [PATCH v2 3/3] ASoC: Remove name-prefix.txt Sameer Pujar
2021-09-02 12:44 ` [PATCH v2 0/3] Convert name-prefix doc to json-schema Jerome Brunet
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=1jk0jyt617.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=spujar@nvidia.com \
--cc=stephan@gerhold.net \
--cc=thierry.reding@gmail.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