devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rohit Visavalia <rohit.visavalia@amd.com>,
	mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: clock: xilinx: Update VCU bindings for reset GPIO
Date: Thu, 2 Jan 2025 19:29:37 +0100	[thread overview]
Message-ID: <35351b4f-daee-46f9-8d0e-f3de12869794@kernel.org> (raw)
In-Reply-To: <20250102163700.759712-4-rohit.visavalia@amd.com>

On 02/01/2025 17:37, Rohit Visavalia wrote:
> Updated VCU binding for reset GPIO pin as optional property.

Subject and here: everything is an update. Be specific and drop all
redundant things making this unnecessary long: add reset GPIO

> It is marked as optional as some of the ZynqMP designs are having vcu_reset
> (reset pin of VCU IP) is driven by proc_sys_reset, proc_sys_reset is another

"are having is" looks like two verbs.

I don't get here mainly why SoC has something driven by its own GPIO.
That's unusual pattern.


> PL IP driven by the PS pl_reset. So, here the VCU reset is not driven by
> axi_gpio or PS GPIO so there will be no GPIO entry.

Anyway, this has to be constrained per SoC.

> 
> Signed-off-by: Rohit Visavalia <rohit.visavalia@amd.com>
> ---
>  Documentation/devicetree/bindings/clock/xlnx,vcu.yaml | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/clock/xlnx,vcu.yaml b/Documentation/devicetree/bindings/clock/xlnx,vcu.yaml
> index bdb14594c40b..b3061309f8dd 100644
> --- a/Documentation/devicetree/bindings/clock/xlnx,vcu.yaml
> +++ b/Documentation/devicetree/bindings/clock/xlnx,vcu.yaml
> @@ -36,6 +36,11 @@ properties:
>        - const: pll_ref
>        - const: aclk
>  
> +  reset-gpios:
> +    description: Optional GPIO used to reset the VCU, if available. Need use this

Drop redundant parts. Not being part of required defines "optional"
already. Don't repeat the schema but say something which we cannot
deduce from this.

> +      reset gpio when in design 'vcu_resetn' is driven by gpio.
> +    maxItems: 1
> +
>  required:
>    - reg
>    - clocks
> @@ -52,6 +57,7 @@ examples:
>          xlnx_vcu: vcu@a0040000 {
>              compatible = "xlnx,vcu-logicoreip-1.0";
>              reg = <0x0 0xa0040000 0x0 0x1000>;
> +            reset-gpios = <&gpio 0x4e GPIO_ACTIVE_HIGH>;

GPIO numbers are not hex... unless this is not GPIO :/

>              clocks = <&si570_1>, <&clkc 71>;
>              clock-names = "pll_ref", "aclk";
>          };


Best regards,
Krzysztof

  reply	other threads:[~2025-01-02 18:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 16:36 [PATCH 0/3] dt-bindings: clock: xilinx: Update VCU bindings Rohit Visavalia
2025-01-02 16:36 ` [PATCH 1/3] dt-bindings: clock: xilinx: move xlnx_vcu dt-binding to clock from soc Rohit Visavalia
2025-01-02 18:30   ` Krzysztof Kozlowski
2025-01-03 11:35     ` Visavalia, Rohit
2025-01-02 16:36 ` [PATCH 2/3] dt-bindings: clock: xilinx: Convert VCU bindings to dtschema Rohit Visavalia
2025-01-02 18:26   ` Krzysztof Kozlowski
2025-01-03 11:35     ` Visavalia, Rohit
2025-01-02 16:37 ` [PATCH 3/3] dt-bindings: clock: xilinx: Update VCU bindings for reset GPIO Rohit Visavalia
2025-01-02 18:29   ` Krzysztof Kozlowski [this message]
2025-01-03 11:35     ` Visavalia, Rohit

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=35351b4f-daee-46f9-8d0e-f3de12869794@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=rohit.visavalia@amd.com \
    --cc=sboyd@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).