Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: shawnguo@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] dt-bindings: soc: imx-iomuxc-gpr: Document the CSI mux
Date: Wed, 10 Sep 2025 21:14:34 -0400	[thread overview]
Message-ID: <aMIies4V8iTNEcWI@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250910233402.567245-1-festevam@gmail.com>

On Wed, Sep 10, 2025 at 08:34:02PM -0300, Fabio Estevam wrote:
> On i.MX6Q/6DL the following subnodes exist to describe the CSI port muxing:
>
> - ipu1_csi0_mux
> - ipu1_csi1_mux
> - ipu2_csi0_mux
> - ipu2_csi1_mux
>
> As they were not documented, dt-schema emits warnings like:
>
>   'ipu1_csi0_mux', 'ipu1_csi1_mux' do not match any of the regexes:
>   '^pinctrl-[0-9]+$'
>
> Add a top-level patternProperties entry for these CSI mux subnodes
> and restrict it to i.MX6Q.
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>

Reviewed-by: Frank Li <Frank.Li@nxp.com>

> ---
> Changes since v1:
> - Restrict it to i.MX6Q (Frank).
>
>  .../bindings/soc/imx/fsl,imx-iomuxc-gpr.yaml     | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/imx/fsl,imx-iomuxc-gpr.yaml b/Documentation/devicetree/bindings/soc/imx/fsl,imx-iomuxc-gpr.yaml
> index 8451cb4dd87c..719de0489002 100644
> --- a/Documentation/devicetree/bindings/soc/imx/fsl,imx-iomuxc-gpr.yaml
> +++ b/Documentation/devicetree/bindings/soc/imx/fsl,imx-iomuxc-gpr.yaml
> @@ -50,6 +50,22 @@ properties:
>      type: object
>      $ref: /schemas/mux/reg-mux.yaml
>
> +patternProperties:
> +  "^ipu[12]_csi[01]_mux$":
> +    type: object
> +    $ref: /schemas/media/video-mux.yaml
> +
> +allOf:
> +  - if:
> +      properties:
> +        compatible:
> +          not:
> +            contains:
> +              const: fsl,imx6q-iomuxc-gpr
> +    then:
> +      patternProperties:
> +        '^ipu[12]_csi[01]_mux$': false
> +
>  additionalProperties: false
>
>  required:
> --
> 2.34.1
>

  reply	other threads:[~2025-09-11  1:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10 23:34 [PATCH v2] dt-bindings: soc: imx-iomuxc-gpr: Document the CSI mux Fabio Estevam
2025-09-11  1:14 ` Frank Li [this message]
2025-09-15  0:31 ` Rob Herring (Arm)
2025-10-20 11:58 ` Shawn Guo

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=aMIies4V8iTNEcWI@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh@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