From: Conor Dooley <conor@kernel.org>
To: Detlev Casanova <detlev.casanova@collabora.com>
Cc: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v3 1/2] dt-bindings: pinctrl: Add rk3576 pinctrl bindings
Date: Thu, 15 Aug 2024 16:05:29 +0100 [thread overview]
Message-ID: <20240815-illusive-pusher-43d3cced8bc9@spud> (raw)
In-Reply-To: <20240814223217.3498-2-detlev.casanova@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]
On Wed, Aug 14, 2024 at 06:30:38PM -0400, Detlev Casanova wrote:
> Add the compatible string as well as the rockchip,sys-grf field which is
> only used on this SoC.
>
> Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> .../bindings/pinctrl/rockchip,pinctrl.yaml | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml
> index 20e806dce1ecb..28f8dc412cf92 100644
> --- a/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml
> @@ -45,6 +45,7 @@ properties:
> - rockchip,rk3368-pinctrl
> - rockchip,rk3399-pinctrl
> - rockchip,rk3568-pinctrl
> + - rockchip,rk3576-pinctrl
> - rockchip,rk3588-pinctrl
> - rockchip,rv1108-pinctrl
> - rockchip,rv1126-pinctrl
> @@ -62,6 +63,12 @@ properties:
> Required for at least rk3188 and rk3288. On the rk3368 this should
> point to the PMUGRF syscon.
>
> + rockchip,sys-grf:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + The phandle of the syscon node for the SYS GRF registers.
> + It is used on rk3576 for i3c software controlled weak pull-up.
> +
> "#address-cells":
> enum: [1, 2]
>
> @@ -72,6 +79,17 @@ properties:
>
> allOf:
> - $ref: pinctrl.yaml#
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: rockchip,rk3576-pinctrl
> + then:
> + required:
> + - rockchip,sys-grf
> + else:
> + properties:
> + rockchip,sys-grf: false
>
> required:
> - compatible
> --
> 2.46.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-08-15 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 22:30 [PATCH v3 0/2] Add pinctrl support for rk3576 Detlev Casanova
2024-08-14 22:30 ` [PATCH v3 1/2] dt-bindings: pinctrl: Add rk3576 pinctrl bindings Detlev Casanova
2024-08-15 15:05 ` Conor Dooley [this message]
2024-08-14 22:30 ` [PATCH v3 2/2] pinctrl: rockchip: Add rk3576 pinctrl support Detlev Casanova
2024-08-15 14:05 ` Heiko Stübner
2024-08-19 15:01 ` Detlev Casanova
2024-08-19 15:32 ` Heiko Stübner
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=20240815-illusive-pusher-43d3cced8bc9@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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).