From: Krzysztof Kozlowski <krzk@kernel.org>
To: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
Cc: Abel Vesa <abelvesa@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-clk@vger.kernel.org, imx@lists.linux.dev,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH 3/7] dt-bindings: clock: document 8ULP's SIM LPAV
Date: Tue, 14 Oct 2025 01:46:42 +0200 [thread overview]
Message-ID: <0f75ad16-e1b0-430e-bf0c-4c386d401d13@kernel.org> (raw)
In-Reply-To: <1ad36baf-83af-4ab7-9f47-dd7f74d4749f@gmail.com>
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
next prev parent reply other threads:[~2025-10-13 23:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 15:54 [PATCH 0/7] Add support for i.MX8ULP's SIM LPAV Laurentiu Mihalcea
2025-08-04 15:54 ` [PATCH 1/7] dt-bindings: reset: imx8ulp: add SIM LPAV reset ID definitions Laurentiu Mihalcea
2025-08-05 7:01 ` Krzysztof Kozlowski
2025-08-04 15:54 ` [PATCH 2/7] dt-bindings: clock: imx8ulp: add SIM LPAV clock gate " Laurentiu Mihalcea
2025-08-05 7:02 ` Krzysztof Kozlowski
2025-10-13 12:52 ` Laurentiu Mihalcea
2025-10-13 23:45 ` Krzysztof Kozlowski
2025-08-04 15:54 ` [PATCH 3/7] dt-bindings: clock: document 8ULP's SIM LPAV Laurentiu Mihalcea
2025-08-05 7:03 ` Krzysztof Kozlowski
2025-10-13 12:48 ` Laurentiu Mihalcea
2025-10-13 23:46 ` Krzysztof Kozlowski [this message]
2025-08-04 15:54 ` [PATCH 4/7] clk: imx: add driver for imx8ulp's sim lpav Laurentiu Mihalcea
2025-08-04 15:54 ` [PATCH 5/7] reset: imx8mp-audiomix: Extend the driver usage Laurentiu Mihalcea
2025-08-05 7:51 ` Daniel Baluta
2025-08-04 15:54 ` [PATCH 6/7] reset: imx8mp-audiomix: Support i.MX8ULP SIM LPAV Laurentiu Mihalcea
2025-08-05 7:53 ` Daniel Baluta
2025-08-04 15:54 ` [PATCH 7/7] arm64: dts: imx8ulp: add sim lpav node Laurentiu Mihalcea
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=0f75ad16-e1b0-430e-bf0c-4c386d401d13@kernel.org \
--to=krzk@kernel.org \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=laurentiumihalcea111@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).