[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aYxJb1mDYIwPr7TY@Lord-Beerus.station>
Date: Wed, 11 Feb 2026 10:18:39 +0100
From: Stefano Radaelli <stefano.radaelli21@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
alexander.h@...iscite.com, pierluigi.p@...iscite.com,
Stefano Radaelli <stefano.r@...iscite.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: sound: simple-card: add
sysclk-cpu-first flag
Hi Krzysztof,
>
> You described the desired Linux feature or behavior, not the actual
> hardware. The bindings are about the latter, so instead you need to
> rephrase the property and its description to match actual hardware
> capabilities/features/configuration etc.
>
thanks for pointing this out.
After re-reading the binding and thinking about it again, I agree with you.
The proposed property describes a Linux driver policy (sysclk programming
order) rather than a hardware capability or configuration, so it does not
really fit the DT binding model.
I'll drop the DT binding part for now and reconsider how this should be
handled on the driver side instead.
If you have suggestions on a more appropriate direction for this kind of
configuration, I'd be happy to hear your opinion.
Best regards,
Stefano
Powered by blists - more mailing lists