From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Stefan Agner <stefan@agner.ch>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v2 2/6] dt-bindings: gpio: vf610: correct i.MX8ULP and i.MX93
Date: Sun, 17 Sep 2023 09:52:31 +0200 [thread overview]
Message-ID: <7ec16938-53fa-24dc-8443-ed6428697558@linaro.org> (raw)
In-Reply-To: <20230916-vf610-gpio-v2-2-40823da788d7@nxp.com>
On 16/09/2023 04:03, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> i.MX8ULP and i.MX93 actually has two interrupts for each gpio
> controller, one for Trustzone non-secure world, one for secure world.
>
> And they has one register based, not two as i.MX7ULP or VF610.
>
> Although the Linux Kernel driver gpio-vf610.c could work with
> fsl,imx7ulp-gpio compatible, it is based on some tricks did in
> device tree with some offset added to base address.
>
> So actually i.MX8ULP/i.MX93 is not compatible with i.MX7ULP.
>
> Last, i.MX93 is directly derived from i.MX8ULP, so make i.MX93 GPIO
> compatible with i.MX8ULP
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> .../devicetree/bindings/gpio/gpio-vf610.yaml | 41 +++++++++++++++++++---
> 1 file changed, 37 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-vf610.yaml b/Documentation/devicetree/bindings/gpio/gpio-vf610.yaml
> index 59427d97adf5..8c1f87a1a393 100644
> --- a/Documentation/devicetree/bindings/gpio/gpio-vf610.yaml
> +++ b/Documentation/devicetree/bindings/gpio/gpio-vf610.yaml
> @@ -20,6 +20,7 @@ description: |
> properties:
> compatible:
> oneOf:
> + - const: fsl,imx8ulp-gpio
> - const: fsl,vf610-gpio
> - items:
> - const: fsl,imx7ulp-gpio
> @@ -27,16 +28,21 @@ properties:
> - items:
> - enum:
> - fsl,imx93-gpio
> - - fsl,imx8ulp-gpio
> - - const: fsl,imx7ulp-gpio
> + - const: fsl,imx8ulp-gpio
>
> reg:
> description: The first reg tuple represents the PORT module, the second tuple
> represents the GPIO module.
> - maxItems: 2
> + items:
> + - description: PORT register base address
> + - description: GPIO register base address
> + minItems: 1
>
> interrupts:
> - maxItems: 1
> + items:
> + - description: GPIO Trustzone non-secure interrupt number
> + - description: GPIO Trustzone secure interrupt number
> + minItems: 1
>
> interrupt-controller: true
>
> @@ -78,6 +84,33 @@ required:
> - "#gpio-cells"
> - gpio-controller
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - fsl,vf610-gpio
> + - fsl,imx7ulp-gpio
> + then:
> + properties:
> + interrupts:
> + items:
> + - description: GPIO interrupt number
So this is different than first interrupt mentioned in top-level?
> + reg:
> + items:
> + - description: PORT register base address
> + - description: GPIO register base address
You have the description in top-level, no need to repeat it. Just
minItems: 2... although it depends whether top-level property will stay.
> + else:
> + properties:
> + interrupts:
> + items:
> + - description: GPIO Trustzone non-secure interrupt number
> + - description: GPIO Trustzone secure interrupt number
> + reg:
> + items:
> + - description: GPIO register base address
So the first entry is different between variants? Then top-level should
be just min/maxItems.
> +
> additionalProperties: false
>
> examples:
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-17 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 2:03 [PATCH v2 0/6] gpio: update i.MX93/8ULP and support i.MX95 Peng Fan (OSS)
2023-09-16 2:03 ` [PATCH v2 1/6] dt-bindings: gpio: vf610: update gpio-ranges Peng Fan (OSS)
2023-09-17 7:46 ` Krzysztof Kozlowski
2023-09-16 2:03 ` [PATCH v2 2/6] dt-bindings: gpio: vf610: correct i.MX8ULP and i.MX93 Peng Fan (OSS)
2023-09-17 7:52 ` Krzysztof Kozlowski [this message]
2023-09-17 12:46 ` Peng Fan
2023-09-16 2:03 ` [PATCH v2 3/6] dt-bindings: gpio: vf610: add i.MX95 compatible Peng Fan (OSS)
2023-09-17 7:52 ` Krzysztof Kozlowski
2023-09-16 2:04 ` [PATCH v2 4/6] gpio: vf610: add i.MX8ULP of_device_id entry Peng Fan (OSS)
2023-09-16 2:04 ` [PATCH v2 5/6] arm64: dts: imx8ulp: update gpio node Peng Fan (OSS)
2023-09-17 7:48 ` Krzysztof Kozlowski
2023-09-17 12:51 ` Peng Fan
2023-09-16 2:04 ` [PATCH v2 6/6] arm64: dts: imx93: " Peng Fan (OSS)
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=7ec16938-53fa-24dc-8443-ed6428697558@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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
all inboxes | Powered by JetHome®