From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andrei Simion <andrei.simion@microchip.com>,
claudiu.beznea@tuxon.dev, lgirdwood@gmail.com,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
Subject: Re: [PATCH 2/2] ASoC: dt-bindings: microchip,sama7g5-i2smcc: Add 'sound-name-prefix' property
Date: Mon, 9 Sep 2024 10:38:05 +0200 [thread overview]
Message-ID: <2bb15a72-82ef-4bc4-b01e-e4768687bab6@kernel.org> (raw)
In-Reply-To: <20240909083530.14695-3-andrei.simion@microchip.com>
On 09/09/2024 10:35, Andrei Simion wrote:
> From: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
>
> Add 'sound-name-prefix' property to differentiate between interfaces in
> DPCM use-cases. Property is optional.
>
> [andrei.simion@microchip.com: Adjust the commit title and message.
> Reword the description for 'sound-name-prefix'.]
>
> Signed-off-by: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
> Signed-off-by: Andrei Simion <andrei.simion@microchip.com>
> ---
> .../bindings/sound/microchip,sama7g5-i2smcc.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/sound/microchip,sama7g5-i2smcc.yaml b/Documentation/devicetree/bindings/sound/microchip,sama7g5-i2smcc.yaml
> index fb630a184350..ad34df67c7c0 100644
> --- a/Documentation/devicetree/bindings/sound/microchip,sama7g5-i2smcc.yaml
> +++ b/Documentation/devicetree/bindings/sound/microchip,sama7g5-i2smcc.yaml
> @@ -52,6 +52,13 @@ properties:
> - const: gclk
> minItems: 1
>
> + sound-name-prefix:
> + pattern: "^I2SMCC[0-9]$"
This does not look correct. Name/prefix can be anything matching real
hardware, why are you restricting it? How can you predict all names?
> + $ref: /schemas/types.yaml#/definitions/string
> + description:
> + Unique prefixes for the sink/source names of the component, ensuring
> + distinct identification among multiple instances.
You are duplicating property definitions. This is not needed at all.
Maybe your schema misses $ref to common schema.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-09 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 8:35 [PATCH 0/2] Adjust Stream Name and DT Bindings Updates Andrei Simion
2024-09-09 8:35 ` [PATCH 1/2] ASoC: atmel: mchp-i2s-mcc: Remove interface name from stream_name Andrei Simion
2024-09-09 8:35 ` [PATCH 2/2] ASoC: dt-bindings: microchip,sama7g5-i2smcc: Add 'sound-name-prefix' property Andrei Simion
2024-09-09 8:38 ` Krzysztof Kozlowski [this message]
[not found] ` <d4b445ec-dc9c-4313-8ef2-e5c086f21449@microchip.com>
2024-09-09 17:51 ` Krzysztof Kozlowski
2024-09-10 7:17 ` Krzysztof Kozlowski
2024-09-09 21:01 ` (subset) [PATCH 0/2] Adjust Stream Name and DT Bindings Updates Mark Brown
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=2bb15a72-82ef-4bc4-b01e-e4768687bab6@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=andrei.simion@microchip.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=codrin.ciubotariu@microchip.com \
--cc=conor+dt@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=tiwai@suse.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).