From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Jose Abreu <joabreu@synopsys.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [QUERY] : STMMAC Clocks
Date: Sat, 1 Mar 2025 15:51:08 +0000 [thread overview]
Message-ID: <Z8Ms7C4-1IgjqBlq@shell.armlinux.org.uk> (raw)
In-Reply-To: <e54bf5af-b2ab-496d-9146-41f88bc4b5f2@lunn.ch>
On Sat, Mar 01, 2025 at 04:15:17PM +0100, Andrew Lunn wrote:
> > However, I think that we should push to standardise on the Synopsys
> > named clock names where they exist (essentially optional) and then
> > allow platform specific clocks where they're buried out of view in
> > the way I describe above.
>
> Interestingly snps,dwc-qos-ethernet.txt has a pretty good description:
>
> - clock-names: May contain any/all of the following depending on the IP
> configuration, in any order:
> - "tx"
> The EQOS transmit path clock. The HW signal name is clk_tx_i.
> In some configurations (e.g. GMII/RGMII), this clock also drives the PHY TX
> path. In other configurations, other clocks (such as tx_125, rmii) may
> drive the PHY TX path.
> - "rx"
> The EQOS receive path clock. The HW signal name is clk_rx_i.
> In some configurations (e.g. GMII/RGMII), this clock is derived from the
> PHY's RX clock output. In other configurations, other clocks (such as
> rx_125, rmii) may drive the EQOS RX path.
> In cases where the PHY clock is directly fed into the EQOS receive path
> without intervening logic, the DT need not represent this clock, since it
> is assumed to be fully under the control of the PHY device/driver. In
> cases where SoC integration adds additional logic to this path, such as a
> SW-controlled clock gate, this clock should be represented in DT.
> - "slave_bus"
> The CPU/slave-bus (CSR) interface clock. This applies to any bus type;
> APB, AHB, AXI, etc. The HW signal name is hclk_i (AHB) or clk_csr_i (other
> buses).
> - "master_bus"
> The master bus interface clock. Only required in configurations that use a
> separate clock for the master and slave bus interfaces. The HW signal name
> is hclk_i (AHB) or aclk_i (AXI).
> - "ptp_ref"
> The PTP reference clock. The HW signal name is clk_ptp_ref_i.
> - "phy_ref_clk"
> This clock is deprecated and should not be used by new compatible values.
> It is equivalent to "tx".
> - "apb_pclk"
> This clock is deprecated and should not be used by new compatible values.
> It is equivalent to "slave_bus".
>
> But snps,dwmac.yaml only has:
>
> clock-names:
> minItems: 1
> maxItems: 8
> additionalItems: true
> contains:
> enum:
> - stmmaceth
> - pclk
> - ptp_ref
>
> Could you improve the description in snps,dwmac.yaml, based on what
> you seen in the data book?
I'm afraid I can't, because the description there is basically rubbish.
As I stated in my previous email, the only one listed there which
means anything as far as the databook is concerned is "ptp_ref". The
other two are just made up names that have no basis for anything in
the databook.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-03-01 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 21:51 [QUERY] : STMMAC Clocks Lad, Prabhakar
2025-02-28 23:38 ` Andrew Lunn
2025-03-01 10:41 ` Russell King (Oracle)
2025-03-01 15:15 ` Andrew Lunn
2025-03-01 15:51 ` Russell King (Oracle) [this message]
2025-03-02 16:51 ` Lad, Prabhakar
2025-03-01 10:35 ` Russell King (Oracle)
2025-03-02 17:37 ` Lad, Prabhakar
2025-03-02 19:06 ` Russell King (Oracle)
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=Z8Ms7C4-1IgjqBlq@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=joabreu@synopsys.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=prabhakar.csengg@gmail.com \
/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).