From: Conor Dooley <conor@kernel.org>
To: Varshini Rajendran <varshini.rajendran@microchip.com>
Cc: claudiu.beznea@microchip.com, lgirdwood@gmail.com,
broonie@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
codrin.ciubotariu@microchip.com, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 31/50] ASoC: dt-bindings: microchip: add sam9x7
Date: Sat, 29 Jul 2023 11:13:09 +0100 [thread overview]
Message-ID: <20230729-contently-gopher-27c3ee182aaa@spud> (raw)
In-Reply-To: <20230728102828.266861-1-varshini.rajendran@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
On Fri, Jul 28, 2023 at 03:58:28PM +0530, Varshini Rajendran wrote:
> Add sam9x7 compatible in the DT documentation.
>
> Signed-off-by: Varshini Rajendran <varshini.rajendran@microchip.com>
> ---
> .../bindings/sound/microchip,sama7g5-i2smcc.yaml | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/sound/microchip,sama7g5-i2smcc.yaml b/Documentation/devicetree/bindings/sound/microchip,sama7g5-i2smcc.yaml
> index 651f61c7c25a..fb630a184350 100644
> --- a/Documentation/devicetree/bindings/sound/microchip,sama7g5-i2smcc.yaml
> +++ b/Documentation/devicetree/bindings/sound/microchip,sama7g5-i2smcc.yaml
> @@ -24,9 +24,14 @@ properties:
> const: 0
>
> compatible:
> - enum:
> - - microchip,sam9x60-i2smcc
> - - microchip,sama7g5-i2smcc
> + oneOf:
> + - enum:
> + - microchip,sam9x60-i2smcc
> + - microchip,sama7g5-i2smcc
> + - items:
> + - enum:
> + - microchip,sam9x7-i2smcc
> + - const: microchip,sam9x60-i2smcc
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-07-29 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 10:28 [PATCH v3 31/50] ASoC: dt-bindings: microchip: add sam9x7 Varshini Rajendran
2023-07-29 10:13 ` Conor Dooley [this message]
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=20230729-contently-gopher-27c3ee182aaa@spud \
--to=conor@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=codrin.ciubotariu@microchip.com \
--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=varshini.rajendran@microchip.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).