From: Ricardo Rivera-Matos <rriveram@opensource.cirrus.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] ASoC: dt-bindings: cs35l45: Adds SYNC properties
Date: Thu, 27 Aug 2026 15:07:07 -0500 [thread overview]
Message-ID: <6f621efb-c7ba-45e4-a700-45844b89b8ef@opensource.cirrus.com> (raw)
In-Reply-To: <12761d4c-3f06-43ac-9f22-5d13e95e935e@kernel.org>
On 8/27/26 7:31 AM, Krzysztof Kozlowski wrote:
> On 22/08/2026 00:41, Ricardo Rivera-Matos wrote:
>> Introduces support for the multidevice synchronization (SYNC)
>> bus. The properties introduced allow for the configuration
>> of the device's transmitter IDs.
>>
>> Signed-off-by: Ricardo Rivera-Matos <rriveram@opensource.cirrus.com>
>> ---
>> .../devicetree/bindings/sound/cirrus,cs35l45.yaml | 27 ++++++++++++++++++++++
>> 1 file changed, 27 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/sound/cirrus,cs35l45.yaml b/Documentation/devicetree/bindings/sound/cirrus,cs35l45.yaml
>> index 70f6c62aedca..20d758dc442f 100644
>> --- a/Documentation/devicetree/bindings/sound/cirrus,cs35l45.yaml
>> +++ b/Documentation/devicetree/bindings/sound/cirrus,cs35l45.yaml
>> @@ -53,6 +53,29 @@ properties:
>> maximum: 3
>> default: 2
>>
>> + sync:
>
> Same comment. You did not respond to Sashiko report because "it
> contradicts itself" is pointless. It did not... unless you meant
> irrelevant part about example. But that is just irrelevant to the binding.
I will explain the contradiction again. Pay close attention to the word bus.
Sashiko says "This commit introduces support for the multidevice
synchronization (SYNC) bus".
Sashiko and I agree, it is a bus.
Sashiko then complains "Is it necessary to use a child node here just to
group configuration properties? In Device Tree design, child nodes
usually represent distinct hardware components, sub-devices, buses, or
standardized structural elements rather than serving as logical folders
to group related configuration properties."
I am confused, do buses merit a child node or not? This is a
contradiction without additional context. Do certain kinds of buses get
child nodes and others do not?
Sashiko is an automated review tool that is being ambiguous. I need a
human maintainer decision made here. Does a bus merit a child node, yes
or no?
>
> Best regards,
> Krzysztof
Ricardo
next prev parent reply other threads:[~2026-08-27 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 22:41 [PATCH v4 0/2] Introduces MDSYNC support for CS35L45 Ricardo Rivera-Matos
2026-08-21 22:41 ` [PATCH v4 1/2] ASoC: dt-bindings: cs35l45: Adds SYNC properties Ricardo Rivera-Matos
2026-08-27 12:31 ` Krzysztof Kozlowski
2026-08-27 20:07 ` Ricardo Rivera-Matos [this message]
2026-08-27 21:26 ` Krzysztof Kozlowski
2026-08-27 21:57 ` Ricardo Rivera-Matos
2026-08-21 22:41 ` [PATCH v4 2/2] ASoC: cs35l45: Adds support for SYNC bus Ricardo Rivera-Matos
2026-08-21 22:49 ` sashiko-bot
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=6f621efb-c7ba-45e4-a700-45844b89b8ef@opensource.cirrus.com \
--to=rriveram@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david.rhodes@cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--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