All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Thierry Bultel <thierry.bultel.yh@bp.renesas.com>
Cc: thierry.bultel@linatsea.fr, linux-renesas-soc@vger.kernel.org,
	geert@linux-m68k.org, paul.barker.ct@bp.renesas.com,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v10 01/10] dt-bindings: serial: Added secondary clock for RZ/T2H RSCI
Date: Thu, 5 Jun 2025 09:39:20 -0500	[thread overview]
Message-ID: <20250605143920.GA2458810-robh@kernel.org> (raw)
In-Reply-To: <20250523142417.2840797-2-thierry.bultel.yh@bp.renesas.com>

On Fri, May 23, 2025 at 04:24:05PM +0200, Thierry Bultel wrote:
> At boot, the default clock is the PCLKM core clock (synchronous
> clock, which is enabled by the bootloader).
> For different baudrates, the asynchronous clock input must be used.
> Clock selection is made by an internal register of RCSI.
> 
> Add the optional "sck", external clock input.
> 
> Also remove the unneeded serial0 alias from the dts example.
> 
> Signed-off-by: Thierry Bultel <thierry.bultel.yh@bp.renesas.com>
> ---
> Changes v9->v10:
>  - mention sck in description
>  - no maxItems on clock-names
>  - fixed the #include dependency in dts example
> Changes v8->v9:
>  - typo in description
>  - named clocks 'operational' and 'bus', and added optional 'sck' clock
>  - uses value of 2nd core clock in example to break the dependency on cpg patch
> ---
>  .../bindings/serial/renesas,rsci.yaml           | 17 +++++++++--------
>  1 file changed, 9 insertions(+), 8 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/serial/renesas,rsci.yaml b/Documentation/devicetree/bindings/serial/renesas,rsci.yaml
> index ea879db5f485..1bf255407df0 100644
> --- a/Documentation/devicetree/bindings/serial/renesas,rsci.yaml
> +++ b/Documentation/devicetree/bindings/serial/renesas,rsci.yaml
> @@ -35,10 +35,15 @@ properties:
>        - const: tei
>  
>    clocks:
> -    maxItems: 1
> +    minItems: 2
> +    maxItems: 3
>  
>    clock-names:
> -    const: fck # UART functional clock
> +    minItems: 2
> +    items:
> +      - const: operation
> +      - const: bus
> +      - const: sck # optional external clock input

You can't just change the clock names. What happens to users of 'fck'?

And you can't make additional entries required. What happens to users 
with only 1 clock defined?

Rob

  parent reply	other threads:[~2025-06-05 14:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 14:24 [PATCH v10 00/10] Add initial support for Renesas RZ/T2H SoC Thierry Bultel
2025-05-23 14:24 ` [PATCH v10 01/10] dt-bindings: serial: Added secondary clock for RZ/T2H RSCI Thierry Bultel
2025-05-23 15:26   ` Geert Uytterhoeven
2025-06-05 14:39   ` Rob Herring [this message]
2025-06-05 18:47     ` Geert Uytterhoeven
2025-05-23 14:24 ` [PATCH v10 02/10] dt-bindings: clock: Add cpg for the Renesas RZ/T2H SoC Thierry Bultel
2025-05-23 14:24 ` [PATCH v10 03/10] soc: renesas: Add RZ/T2H (R9A09G077) config option Thierry Bultel
2025-05-23 14:24 ` [PATCH v10 04/10] clk: renesas: Pass sub struct of cpg_mssr_priv to cpg_clk_register Thierry Bultel
2025-05-23 14:24 ` [PATCH v10 05/10] clk: renesas: Add support for R9A09G077 SoC Thierry Bultel
2025-05-23 14:24 ` [PATCH v10 06/10] serial: sh-sci: Use private port ID Thierry Bultel
2025-05-23 14:24 ` [PATCH v10 07/10] serial: sh-sci: Add support for RZ/T2H SCI Thierry Bultel
2025-05-23 15:28   ` Geert Uytterhoeven
2025-05-23 14:24 ` [PATCH v10 08/10] arm64: dts: renesas: Add initial support for renesas RZ/T2H SoC Thierry Bultel
2025-05-23 14:24 ` [PATCH v10 09/10] arm64: dts: renesas: Add initial support for renesas RZ/T2H eval board Thierry Bultel
2025-05-23 14:24 ` [PATCH v10 10/10] arm64: defconfig: Enable Renesas RZ/T2H serial SCI Thierry Bultel

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=20250605143920.GA2458810-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=paul.barker.ct@bp.renesas.com \
    --cc=thierry.bultel.yh@bp.renesas.com \
    --cc=thierry.bultel@linatsea.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.