mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Biju Das <biju.das.jz@bp.renesas.com>
To: geert <geert@linux-m68k.org>
Cc: biju.das.au <biju.das.au@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	magnus.damm <magnus.damm@gmail.com>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: RE: [PATCH v3 05/10] dt-bindings: clock: Document RZ/G3L SoC
Date: Fri, 13 Mar 2026 14:35:36 +0000	[thread overview]
Message-ID: <TYCPR01MB113329C33FF3CF8832B9FB1498645A@TYCPR01MB11332.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdWtBRHKSd6wb7Q-YmCPSnBGk_pETp7q-eCUJi3t8ERS5Q@mail.gmail.com>

Hi Geert,

Thanks for the feedback.

> -----Original Message-----
> From: Geert Uytterhoeven <geert@linux-m68k.org>
> Sent: 13 March 2026 14:06
> Subject: Re: [PATCH v3 05/10] dt-bindings: clock: Document RZ/G3L SoC
> 
> Hi Biju,
> 
> On Thu, 5 Mar 2026 at 16:18, Biju Das <biju.das.jz@bp.renesas.com> wrote:
> > > From: Geert Uytterhoeven <geert@linux-m68k.org> On Tue, 3 Feb 2026
> > > at 11:30, Biju <biju.das.au@gmail.com> wrote:
> > > > From: Biju Das <biju.das.jz@bp.renesas.com>
> > > >
> > > > Document the device tree bindings for the Renesas RZ/G3L SoC Clock
> > > > Pulse Generator (CPG). RZ/G3L CPG is similar to RZ/G2L CPG but has
> > > > 5 clocks compared to 1 clock on other SoCs.
> > > >
> > > > Also define RZ/G3L (R9A08G046) Clock Pulse Generator Core Clock,
> > > > module clock outputs, as listed in section 4.4.2 ("Clock List
> > > > r1.00") and add Reset definitions referring to registers CPG_RST_*
> > > > in Section 4.4.3
> > > > ("Register") of the RZ/G3L Hardware User's Manual (Rev.1.00 Oct, 2025).
> > > >
> > > > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> > > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> > >
> > > > ---
> > > > a/Documentation/devicetree/bindings/clock/renesas,rzg2l-cpg.yaml
> > > > +++ b/Documentation/devicetree/bindings/clock/renesas,rzg2l-cpg.ya
> > > > +++ ml
> > > > @@ -28,19 +28,30 @@ properties:
> > > >        - renesas,r9a07g044-cpg # RZ/G2{L,LC}
> > > >        - renesas,r9a07g054-cpg # RZ/V2L
> > > >        - renesas,r9a08g045-cpg # RZ/G3S
> > > > +      - renesas,r9a08g046-cpg # RZ/G3L
> > > >        - renesas,r9a09g011-cpg # RZ/V2M
> > > >
> > > >    reg:
> > > >      maxItems: 1
> > > >
> > > >    clocks:
> > > > -    maxItems: 1
> > > > +    minItems: 1
> > > > +    items:
> > > > +      - description: Clock source to CPG can be either from external clock
> > > > +                     input (EXCLK) or crystal oscillator (XIN/XOUT).
> > > > +      - description: ETH0 TXC clock input
> > > > +      - description: ETH0 RXC clock input
> > > > +      - description: ETH1 TXC clock input
> > > > +      - description: ETH1 RXC clock input
> > > >
> > > >    clock-names:
> > > > -    description:
> > > > -      Clock source to CPG can be either from external clock input (EXCLK) or
> > > > -      crystal oscillator (XIN/XOUT).
> > > > -    const: extal
> > > > +    minItems: 1
> > > > +    items:
> > > > +      - const: extal
> > > > +      - const: eth0_txc_tx_clk
> > > > +      - const: eth0_rxc_rx_clk
> > > > +      - const: eth1_txc_tx_clk
> > > > +      - const: eth1_rxc_rx_clk
> > >
> > > Are you sure about these four clocks? On which pins are they input?
> >
> > From Figure 4.4-5 Block Diagram of the Deformed Clock System (4), page
> > 789
> >
> > These clks are external source clks connected to CPG_ETH_SSEL mux for
> > selecting rx/tx clks.
> >
> > In RGMII case, currently on RZ/G3L SMARC EVK:
> >
> > For Tx: we select DIV_ETH0_TR (SEL_ETH0A_SET) For Rx: we select
> > ETH0_RXC_RX_CLK_IN (SEL_ETH0B_SET)
> 
> Sure, these clocks are indeed shown in that Figure, and referenced in the CPG_ETH_SSEL register
> documentation, but where do they originate from? On which pins are they supplied?

Figure 6.3-1 Block Diagram of the Ethernet Interface 

and

1.3.3 Clock Pin Specifications
Table 1.3-3 List of Pin Functions (1/2)

For Rx this clock is supplied by PHY on the RZ/G3L SMARC SoM Module.
RZ_ETH0_RXC is the pin.
 
For Tx this clock is supplied by the SoC(RZ_ETH0_TXC)

Cheers,
Biju

  reply	other threads:[~2026-03-13 14:35 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 10:30 [PATCH v3 00/10] Add support for Renesas RZ/G3L SoC and SMARC-EVK platform Biju
2026-02-03 10:30 ` [PATCH v3 01/10] dt-bindings: dma: rz-dmac: Document RZ/G3L SoC Biju
2026-03-04  8:21   ` Geert Uytterhoeven
2026-03-04 14:02     ` Biju Das
2026-02-03 10:30 ` [PATCH v3 02/10] dt-bindings: soc: renesas: Document RZ/G3L SoC variants, SMARC SoM and Carrier-II EVK Biju
2026-02-04 18:03   ` Conor Dooley
2026-03-04  8:26   ` Geert Uytterhoeven
2026-02-03 10:30 ` [PATCH v3 03/10] dt-bindings: soc: renesas: renesas,rzg2l-sysc: Document RZ/G3L SoC Biju
2026-03-04  8:36   ` Geert Uytterhoeven
2026-02-03 10:30 ` [PATCH v3 04/10] soc: renesas: rz-sysc: Add SoC identification for " Biju
2026-03-04  8:37   ` Geert Uytterhoeven
2026-02-03 10:30 ` [PATCH v3 05/10] dt-bindings: clock: Document " Biju
2026-02-17 12:03   ` Biju Das
2026-03-05 14:21   ` Geert Uytterhoeven
2026-03-05 15:18     ` Biju Das
2026-03-13 14:05       ` Geert Uytterhoeven
2026-03-13 14:35         ` Biju Das [this message]
2026-03-17 16:40           ` Geert Uytterhoeven
2026-02-03 10:30 ` [PATCH v3 06/10] clk: renesas: Add support for " Biju
2026-02-17 11:13   ` Biju Das
2026-03-05 14:22     ` Geert Uytterhoeven
2026-02-03 10:30 ` [PATCH v3 07/10] arm64: dts: renesas: Add initial DTSI " Biju
2026-03-05 14:54   ` Geert Uytterhoeven
2026-03-05 14:57     ` Geert Uytterhoeven
2026-03-05 16:09       ` Biju Das
2026-03-05 16:57     ` Biju Das
2026-03-06  8:50       ` Geert Uytterhoeven
2026-03-06  9:10         ` Biju Das
2026-03-06  9:25           ` Geert Uytterhoeven
2026-03-06 11:57             ` Biju Das
2026-02-03 10:30 ` [PATCH v3 08/10] arm64: dts: renesas: Add initial support for RZ/G3L SMARC SoM Biju
2026-03-05 14:58   ` Geert Uytterhoeven
2026-02-03 10:30 ` [PATCH v3 09/10] arm64: dts: renesas: renesas-smarc2: Move usb3 nodes to board DTS Biju
2026-03-05 15:00   ` Geert Uytterhoeven
2026-03-05 16:10     ` Biju Das
2026-02-03 10:30 ` [PATCH v3 10/10] arm64: dts: renesas: Add initial device tree for RZ/G3L SMARC EVK board Biju
2026-03-05 15:02   ` Geert Uytterhoeven
2026-02-25 11:24 ` (subset) [PATCH v3 00/10] Add support for Renesas RZ/G3L SoC and SMARC-EVK platform Vinod Koul

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=TYCPR01MB113329C33FF3CF8832B9FB1498645A@TYCPR01MB11332.jpnprd01.prod.outlook.com \
    --to=biju.das.jz@bp.renesas.com \
    --cc=biju.das.au@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh@kernel.org \
    --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

all inboxes | Powered by JetHome®