From: Conor Dooley <conor@kernel.org>
To: David Rau <David.Rau.opensource@dm.renesas.com>
Cc: conor+dt@kernel.org, support.opensource@diasemi.com,
lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: dialog,da7219: convert to dtschema
Date: Fri, 19 May 2023 17:29:33 +0100 [thread overview]
Message-ID: <20230519-tables-stoppage-51c998e0421c@spud> (raw)
In-Reply-To: <20230519092321.26915-1-David.Rau.opensource@dm.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]
Hey David,
I think some wires got crossed here - what I meant was send 2 patches in
a series, where one did the conversion and the other added the new
property.
On Fri, May 19, 2023 at 09:23:21AM +0000, David Rau wrote:
> Convert Dialog DA7219 bindings to DT schema format.
>
> Signed-off-by: David Rau <David.Rau.opensource@dm.renesas.com>
> + interrupt-names:
> + oneOf:
> + - items:
> + - const: wakeup
> + - items:
> + - const: irq
> + description:
> + Name associated with interrupt line.
> + Should be "wakeup" if interrupt is to be used to wake system,
> + otherwise "irq" should be used.
Hmm, that is not quite what I meant. I was thinking that you could
add itemised descriptions for what the individual behaviours are.
But on reflection, how about:
interrupt-names:
description:
Should be "wakeup" if interrupt is to be used to wake the system,
otherwise "irq" should be used.
enum:
- wakeup
- irq
> +
> + wakeup-source:
> + type: boolean
> + description:
> + Flag to indicate this device can wake system (suspend/resume).
> +
> + "#clock-cells":
> + const: 1
> +
> + clock-output-names:
> + minItems: 2
> + maxItems: 2
I was thinking
clock-output-names:
- items:
- const: WCLK
- const: BCLK
(assuming I didn't misunderstand the text binding!)
> + description:
> + Name given for DAI word clock and bit clock outputs.
> +
> + clocks:
maxItems: 1
> + description:
> + phandle and clock specifier for codec MCLK.
> +
> + clock-names:
> + const: mclk
> + dlg,jack-det-rate:
> + enum: ["32ms_64ms", "64ms_128ms", "128ms_256ms", "256ms_512ms"]
The "s here are not needed btw, the other enums in the tree described
like this (that use strings) avoid the "s.
Thanks & apologies for the confusion,
Conor.
> + description:
> + Jack type detection latency (3/4 pole).
> + $ref: /schemas/types.yaml#/definitions/string
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-19 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 9:23 [PATCH] ASoC: dt-bindings: dialog,da7219: convert to dtschema David Rau
2023-05-19 16:29 ` Conor Dooley [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-18 9:14 David Rau
2023-05-18 20:03 ` Conor Dooley
2023-05-18 20:56 ` Conor Dooley
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=20230519-tables-stoppage-51c998e0421c@spud \
--to=conor@kernel.org \
--cc=David.Rau.opensource@dm.renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=support.opensource@diasemi.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).