public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Frank Li <Frank.li@nxp.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rui Miguel Silva <rmfrfs@gmail.com>,
	Martin Kepplinger <martink@posteo.de>,
	Purism Kernel Team <kernel@puri.sm>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	"Guoniu.zhou" <guoniu.zhou@nxp.com>,
	Robby Cai <robby.cai@nxp.com>,
	Robert Chiras <robert.chiras@nxp.com>
Subject: Re: [PATCH v2 01/14] dt-bindings: phy: Add MIPI CSI PHY for i.MX8Q
Date: Mon, 10 Feb 2025 23:10:13 +0200	[thread overview]
Message-ID: <20250210211013.GC8531@pendragon.ideasonboard.com> (raw)
In-Reply-To: <Z6UuR9mHhQUdnBEc@lizhi-Precision-Tower-5810>

On Thu, Feb 06, 2025 at 04:48:55PM -0500, Frank Li wrote:
> On Thu, Feb 06, 2025 at 11:18:08PM +0200, Laurent Pinchart wrote:
> > On Wed, Feb 05, 2025 at 12:18:10PM -0500, Frank Li wrote:
> > > Add MIPI CSI phy binding doc for i.MX8QXP, i.MX8QM and i.MX8ULP.
> >
> > s/CSI/CSI-2/ in the subject line, here and below.
> > s/phy/PHY/
> >
> > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > > ---
> > > change from v1 to v2
> > > - Add missed fsl,imx8qm-mipi-cphy, which failback to fsl,imx8qxp-mipi-cphy
> > > - Move reg to required. Previous 8ulp use fsl,offset in downstream version.
> > > which should be reg. So move it to required
> > > ---
> > >  .../bindings/phy/fsl,imx8qxp-mipi-cphy.yaml        | 57 ++++++++++++++++++++++
> > >  1 file changed, 57 insertions(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8qxp-mipi-cphy.yaml b/Documentation/devicetree/bindings/phy/fsl,imx8qxp-mipi-cphy.yaml
> > > new file mode 100644
> > > index 0000000000000..7335b9262d0e7
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/phy/fsl,imx8qxp-mipi-cphy.yaml
> > > @@ -0,0 +1,57 @@
> > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/phy/fsl,imx8qxp-mipi-cphy.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: Freescale i.MX8 SoC MIPI CSI PHY
> > > +
> > > +maintainers:
> > > +  - Frank Li <Frank.Li@nxp.com>
> > > +
> > > +properties:
> > > +  "#phy-cells":
> > > +    const: 0
> > > +
> > > +  compatible:
> > > +    oneOf:
> > > +      - enum:
> > > +          - fsl,imx8qxp-mipi-cphy
> > > +          - fsl,imx8ulp-mipi-cphy
> > > +      - items:
> > > +          - const: fsl,imx8qm-mipi-cphy
> > > +          - const: fsl,imx8qxp-mipi-cphy
> >
> > Why are those called cphy when, as far as I can tell from the
> > documentation, they are D-PHYs ? Does that stand for *C*SI PHY ?
> 
> There are already have D-PHYS for MIPI display phy binding. cphy just means
> for camera PHY.

Ah OK. I would probably have gone for *-mipi-dphy-rx then, but I'm OK
with the proposed "cphy". Explaining this in the description would be
useful.

> > I find
> > it slightly confusing, but not so much that I'd ask for a change. It's
> > just a name at the end of the day.
> >
> > Apart from that the binding looks fairly OK. Except maybe from the fact
> > that this device is not a PHY :-( It has two PHY control registers, but
> > the rest seems related to the glue logic at the output of the CSI-2
> > receiver. I wonder if we should go the syscon route.
> 
> Do you means use phandle to syscon node in csi-2 driver? Actually this
> ways is not perferred by device tree team because it should be exported
> as what actual function, such as PHY or RESET by use standard interface.
> 
> We met similar case at other substream.

I don't like syscon much either, but in this specific case I'm not sure
what else we could do. This device really aggregates some control over
the PHY and over the glue logic at the output of the CSI-2 controller.
Modelling it as "just a PHY" will cause problem as soon as you'll want
to configure the other parameters.

> > > +
> > > +  reg:
> > > +    maxItems: 1
> > > +
> > > +  power-domains:
> > > +    maxItems: 1
> > > +
> > > +required:
> > > +  - "#phy-cells"
> > > +  - compatible
> > > +  - reg
> > > +
> > > +allOf:
> > > +  - if:
> > > +      properties:
> > > +        compatible:
> > > +          contains:
> > > +            enum:
> > > +              - fsl,imx8qxp-mipi-cphy
> > > +    then:
> > > +      required:
> > > +        - power-domains
> > > +
> > > +additionalProperties: false
> > > +
> > > +examples:
> > > +  - |
> > > +    phy@58221000 {
> > > +            compatible = "fsl,imx8qxp-mipi-cphy";
> > > +            reg = <0x58221000 0x10000>;
> > > +            #phy-cells = <0>;
> > > +            power-domains = <&pd 0>;
> > > +    };
> > > +

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2025-02-10 21:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 17:18 [PATCH v2 00/14] media: imx8: add camera support Frank Li
2025-02-05 17:18 ` [PATCH v2 01/14] dt-bindings: phy: Add MIPI CSI PHY for i.MX8Q Frank Li
2025-02-06 21:18   ` Laurent Pinchart
2025-02-06 21:48     ` Frank Li
2025-02-10 21:10       ` Laurent Pinchart [this message]
2025-02-11 15:25         ` Frank Li
2025-02-05 17:18 ` [PATCH v2 02/14] phy: freescale: Add MIPI CSI PHY driver " Frank Li
2025-02-06 21:43   ` Laurent Pinchart
2025-02-05 17:18 ` [PATCH v2 03/14] dt-bindings: firmware: imx: add property reset-controller Frank Li
2025-02-05 17:18 ` [PATCH v2 04/14] reset: imx: Add SCU reset driver for i.MX8QXP and i.MX8QM Frank Li
2025-02-05 17:18 ` [PATCH v2 05/14] media: dt-bindings: Add binding doc for i.MX8QXP and i.MX8QM ISI Frank Li
2025-02-05 17:18 ` [PATCH v2 06/14] media: nxp: imx8-isi: Allow num_sources to be greater than num_sink Frank Li
2025-02-05 17:18 ` [PATCH v2 07/14] media: imx8-isi: Add support for i.MX8QM and i.MX8QXP Frank Li
2025-02-05 17:18 ` [PATCH v2 08/14] media: dt-bindings: nxp,imx8mq-mipi-csi2: Add i.MX8QM(QXP) compatible strings Frank Li
2025-02-05 17:18 ` [PATCH v2 09/14] media: imx8mq-mipi-csi2: Add imx8mq_plat_data for different " Frank Li
2025-02-05 17:18 ` [PATCH v2 10/14] media: imx8mq-mipi-csi2: Add support for i.MX8QXP Frank Li
2025-02-05 17:18 ` [PATCH v2 11/14] arm64: dts: imx8: add capture controller for i.MX8's img subsystem Frank Li
2025-02-05 17:18 ` [PATCH v2 12/14] arm64: dts: imx8qm: add 24MHz clock-xtal24m Frank Li
2025-02-05 17:18 ` [PATCH v2 13/14] arm64: dts: imx8q: add linux,cma node for imx8qm-mek and imx8qxp-mek Frank Li
2025-02-05 17:18 ` [PATCH v2 14/14] arm64: dts: imx8q: add camera ov5640 support " 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=20250210211013.GC8531@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=Frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=guoniu.zhou@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=kernel@puri.sm \
    --cc=kishon@kernel.org \
    --cc=krzk+dt@kernel.org \
    --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=rmfrfs@gmail.com \
    --cc=robby.cai@nxp.com \
    --cc=robert.chiras@nxp.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