From: Rob Herring <robh@kernel.org>
To: Maxim Kochetkov <fido_max@inbox.ru>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Sameer Pujar <spujar@nvidia.com>,
Astrid Rost <astrid.rost@axis.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Herve Codina <herve.codina@bootlin.com>,
Aidan MacDonald <aidanmacdonald.0x0@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: dt-bindings: simple-card: add triggers properties
Date: Tue, 18 Jul 2023 16:08:43 -0600 [thread overview]
Message-ID: <20230718220843.GA1944897-robh@kernel.org> (raw)
In-Reply-To: <20230715083046.108674-3-fido_max@inbox.ru>
On Sat, Jul 15, 2023 at 11:30:43AM +0300, Maxim Kochetkov wrote:
> The trigger-start/stop properties allows to specify DAI link
> trigger ordering method.
Obviously. Why do you need these? What problem does it solve?
I don't think these belong in simple-card. What's next? What if you need
delays between each step? This is the problem with 'simple' or 'generic'
bindings. It's a never ending addition of properties which are not well
thought out.
>
> Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru>
> ---
> .../bindings/sound/simple-card.yaml | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/sound/simple-card.yaml b/Documentation/devicetree/bindings/sound/simple-card.yaml
> index 59ac2d1d1ccf..f1878d470d83 100644
> --- a/Documentation/devicetree/bindings/sound/simple-card.yaml
> +++ b/Documentation/devicetree/bindings/sound/simple-card.yaml
> @@ -99,6 +99,28 @@ definitions:
> description: the widget names for which pin switches must be created.
> $ref: /schemas/types.yaml#/definitions/string-array
>
> + trigger-start:
> + description: |-
> + Start trigger ordering method:
> + default: Link->Component->DAI
> + ldc: Link->DAI->Component
> + $ref: /schemas/types.yaml#/definitions/string
> + items:
> + enum:
> + - default
Why do you need a value of 'default'? What's the default when the
property is not present?
> + - ldc
> +
> + trigger-stop:
> + description: |-
> + Stop trigger ordering method:
> + default: DAI->Component->Link
> + ldc: Component->DAI->Link
> + $ref: /schemas/types.yaml#/definitions/string
> + items:
> + enum:
> + - default
> + - ldc
> +
> format:
> description: audio format.
> items:
> @@ -210,6 +232,10 @@ properties:
> maxItems: 1
> simple-audio-card,mic-det-gpio:
> maxItems: 1
> + simple-audio-card,trigger-start:
> + $ref: "#/definitions/trigger-start"
> + simple-audio-card,trigger-stop:
> + $ref: "#/definitions/trigger-stop"
Don't continue this 'simple-audio-card,' prefix pattern. With it, no
other binding can use these properties.
>
> patternProperties:
> "^simple-audio-card,cpu(@[0-9a-f]+)?$":
> @@ -259,6 +285,11 @@ patternProperties:
> maxItems: 1
> mic-det-gpio:
> maxItems: 1
> + trigger-start:
> + $ref: "#/definitions/trigger-start"
> + trigger-stop:
> + $ref: "#/definitions/trigger-stop"
> +
>
> patternProperties:
> "^cpu(-[0-9]+)?$":
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-07-18 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 8:30 [PATCH v2] Add support for trigger-start/stop for simple audio card Maxim Kochetkov
2023-07-15 8:30 ` [PATCH v2] ASoC: simple-card-utils: introduce asoc_simple_parse_triggers() Maxim Kochetkov
2023-07-15 8:30 ` [PATCH v2] ASoC: dt-bindings: simple-card: add triggers properties Maxim Kochetkov
2023-07-18 22:08 ` Rob Herring [this message]
2023-07-19 7:13 ` Maxim Kochetkov
2023-07-15 8:30 ` [PATCH v2] ASoC: simple-card: add triggers parsing from DT node support Maxim Kochetkov
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=20230718220843.GA1944897-robh@kernel.org \
--to=robh@kernel.org \
--cc=aidanmacdonald.0x0@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=astrid.rost@axis.com \
--cc=broonie@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fido_max@inbox.ru \
--cc=herve.codina@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=spujar@nvidia.com \
--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).