From: Krzysztof Kozlowski <krzk@kernel.org>
To: Frank Li <Frank.Li@nxp.com>, Rui Miguel Silva <rmfrfs@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Martin Kepplinger <martink@posteo.de>,
Purism Kernel Team <kernel@puri.sm>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Eugen Hristev <eugen.hristev@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
Alice Yuan <alice.yuan@nxp.com>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org
Subject: Re: [PATCH 2/7] dt-bindings: soc: imx-blk-ctrl: add MIPI CSI2 dphy support
Date: Wed, 2 Jul 2025 08:40:59 +0200 [thread overview]
Message-ID: <5d22829c-f807-4416-ab5a-87d210ade897@kernel.org> (raw)
In-Reply-To: <20250701-95_cam-v1-2-c5172bab387b@nxp.com>
On 02/07/2025 00:06, Frank Li wrote:
> Add child node dphy-rx, which export phys interface to MIPI CSI2
> controller.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> imx media blk ctrl combined many small glue logic registers for display
> , camera, power, clk and reset.
>
> There are some discussion at
> https://lore.kernel.org/all/4414669.ejJDZkT8p0@steina-w/
> to define whole schema for this.
>
> But there are some difficults to cover whole once.
>
> Plan use two steps to complete it
> - add all camera related property and subnode
> - add all display related property and subnode
> ---
> .../bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml | 28 ++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml b/Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml
> index b3554e7f9e76d..708cd00f2b896 100644
> --- a/Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml
> +++ b/Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml
> @@ -46,6 +46,34 @@ properties:
> - const: csi
> - const: dsi
>
> + dphy-rx:
> + type: object
> + properties:
> + compatible:
> + enum:
> + - fsl,imx93-dphy-rx
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + items:
> + - const: cfg
> +
> + '#phy-cells':
> + const: 0
> +
> + power-domains:
> + maxItems: 1
This looks wrong. How a parent device can take one power domain and
child take a different one? If that's the same, then it is redundant,
because it is part of parent's power domain.
I have also some doubts about clock. Rarely syscon children have their
own resources which would make this entire node redundant.
Provide complete picture on this in commit msg.
> +
> + required:
> + - compatible
> + - clocks
> + - clock-names
> + - '#phy-cells'
> +
> + additionalProperties: false
Please place it after type:.
You also need to update the example.
> +
> required:
> - compatible
> - reg
>
Best regards,
Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-07-02 6:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 22:06 [PATCH 0/7] media: add imx93 mipi/controller csi support Frank Li
2025-07-01 22:06 ` [PATCH 1/7] dt-bindings: media: add DW MIPI CSI-2 Host support Frank Li
2025-07-02 6:38 ` Krzysztof Kozlowski
2025-07-01 22:06 ` [PATCH 2/7] dt-bindings: soc: imx-blk-ctrl: add MIPI CSI2 dphy support Frank Li
2025-07-02 6:40 ` Krzysztof Kozlowski [this message]
2025-07-02 6:42 ` Krzysztof Kozlowski
2025-07-02 18:02 ` Frank Li
2025-07-02 20:12 ` Krzysztof Kozlowski
2025-07-01 22:06 ` [PATCH 3/7] pmdomain: imx93-blk-ctrl: populate child devices Frank Li
2025-07-02 5:15 ` Alexander Stein
2025-07-01 22:06 ` [PATCH 4/7] phy: freescale: add imx93 MIPI CSI2 DPHY support Frank Li
2025-07-02 5:50 ` Alexander Stein
2025-07-01 22:06 ` [PATCH 5/7] media: nxp: add DesignWare MIPI CSI2 controller driver Frank Li
2025-07-02 6:04 ` Alexander Stein
2025-07-02 6:35 ` Krzysztof Kozlowski
2025-07-02 9:38 ` Laurent Pinchart
2025-07-02 15:55 ` Frank Li
2025-07-04 2:04 ` Frank Li
2025-07-01 22:06 ` [PATCH NOT MERGE 6/7] arm64: dts: imx93-11x11-evk: add camera related nodes Frank Li
2025-07-01 22:06 ` [PATCH NOT MERGE 7/7] media: i2c: add AP1302 driver from community Frank Li
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=5d22829c-f807-4416-ab5a-87d210ade897@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alice.yuan@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@linaro.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=martink@posteo.de \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=peng.fan@nxp.com \
--cc=rmfrfs@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vkoul@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).