From: Conor Dooley <conor@kernel.org>
To: Andrei Simion <andrei.simion@microchip.com>
Cc: krzk@kernel.org, alexandre.belloni@bootlin.com,
broonie@kernel.org, claudiu.beznea@tuxon.dev,
conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: misc: atmel,at91-ssc: Convert to YAML format
Date: Wed, 29 Jan 2025 17:44:56 +0000 [thread overview]
Message-ID: <20250129-confound-progeny-62b1f12cb03d@spud> (raw)
In-Reply-To: <20250129132822.9382-1-andrei.simion@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
On Wed, Jan 29, 2025 at 03:28:23PM +0200, Andrei Simion wrote:
> Hi,
>
> Thank you for the review.
>
> I will place this in: Documentation/devicetree/bindings/sound/
> because the SSC it is used only for Audio.
>
> >
> > Missing dai-cells. Old binding said 0, now you say anything...
> >
> > Missing required block
> >
> >> +allOf:
> >> + - $ref: ../sound/dai-common.yaml#
> >
> > Full path, so /schemas/
> >
> >> + - if:
> >> + properties:
> >> + compatible:
> >> + contains:
> >> + enum:
> >> + - atmel,at91sam9g45-ssc
> >> + then:
> >> + required:
> >> + - compatible
> >> + - reg
> >> + - interrupts
> >> + - dmas
> >> + - dma-names
> >
> > So only dmas?
> >
> >> + - clocks
> >> + - clock-names
> >> + else:
> >> + required:
> >> + - compatible
> >> + - reg
> >> + - interrupts
> >> + - clocks
> >> + - clock-names
> >
> > Drop entire required:
> >
>
> I have a question:
>
> 1) The old binding said if "atmel,at91sam9g45-ssc": add dmas and DMA-names to the list:
> - compatible, reg, interrupts, clock-names, clocks
> Why do you ask: "drop entire required"?
The bits that are required in both cases can be set outside the
conditional, so you can do something like
if:
foo
then:
required:
- dmas
- dma-names
required:
- compatible
- reg
- interrupts
- clocks
- clock-names
which I think captures all of what you're trying to do in the quote
above.
> I intended to set the required through a conditional.
> case 1) dma transfer
> case 2) pdc transfer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-01-29 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 16:18 [PATCH 0/2] Convert atmel-ssc.txt to YAML Andrei Simion
2025-01-28 16:18 ` [PATCH 1/2] dt-bindings: misc: atmel,at91-ssc: Convert to YAML format Andrei Simion
2025-01-29 8:13 ` Krzysztof Kozlowski
2025-01-29 13:28 ` Andrei Simion
2025-01-29 17:44 ` Conor Dooley [this message]
2025-01-30 7:18 ` Krzysztof Kozlowski
2025-01-28 16:18 ` [PATCH 2/2] MAINTAINERS: Update the documentation file supported for MICROCHIP SSC DRIVER Andrei Simion
2025-01-29 8:13 ` Krzysztof Kozlowski
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=20250129-confound-progeny-62b1f12cb03d@spud \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andrei.simion@microchip.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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).