[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0f75ad16-e1b0-430e-bf0c-4c386d401d13@kernel.org>
Date: Tue, 14 Oct 2025 01:46:42 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Laurentiu Mihalcea <laurentiumihalcea111@...il.com>
Cc: Abel Vesa <abelvesa@...nel.org>, Peng Fan <peng.fan@....com>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd
<sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Fabio Estevam <festevam@...il.com>, Philipp Zabel <p.zabel@...gutronix.de>,
linux-clk@...r.kernel.org, imx@...ts.linux.dev, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Pengutronix Kernel Team <kernel@...gutronix.de>
Subject: Re: [PATCH 3/7] dt-bindings: clock: document 8ULP's SIM LPAV
On 13/10/2025 14:48, Laurentiu Mihalcea wrote:
>>> +
>>> + mux-controller:
>>> + $ref: /schemas/mux/reg-mux.yaml#
>>> +
>>> +required:
>>> + - compatible
>>> + - reg
>>> + - clocks
>>> + - clock-names
>>> + - '#clock-cells'
>> reset cells and mux controller.
>
>
> I'd say the mux-controller child can stay optional since the driver allows it?
>
>
> As for "#reset-cells": unless CONFIG_RESET_CONTROLLER is enabled, the driver allows
>
> this property to not be specified. The whole idea was to try and make the driver more
I don't talk here about driver, but hardware. How is it possible to
create a board with imx8ulp which sometimes have this mux and sometimes
does not have?
Best regards,
Krzysztof
Powered by blists - more mailing lists