On Fri, Jul 28, 2023 at 02:51:26PM +0200, Krzysztof Kozlowski wrote: > On 28/07/2023 11:08, Maso Huang wrote: > > + - assigned-clocks > > + - assigned-clock-parents > You should constrain your clocks per variants. I doubt that they are > really so flexible/optional on each SoC... or maybe missing clocks are > result of unimplemented parts in the driver? But then this should not > really affect bindings. Bindings still should require such clocks. Your > DTS can always provide a <0>, if needed. Depending on what the clocks are some of them might genuinely be optional, it's fairly common for audio devices to have multiple clock inputs and be able to select between them depending on system requirements or to have bidirectional clock pins which may be either a provider or consumer depending on system configuration. No idea how that applies with this specific device.
Attachment:
signature.asc
Description: PGP signature
