From: Krzysztof Kozlowski <krzk@kernel.org>
To: Drew Fustini <dfustini@tenstorrent.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Jose Abreu <joabreu@synopsys.com>,
Jisheng Zhang <jszhang@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Drew Fustini <drew@pdp7.com>, Guo Ren <guoren@kernel.org>,
Fu Wei <wefu@redhat.com>, Conor Dooley <conor@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 1/3] dt-bindings: net: Add T-HEAD dwmac support
Date: Thu, 3 Oct 2024 12:42:09 +0200 [thread overview]
Message-ID: <8f0a6e27-df0c-41fb-8714-10fdfbe976ab@kernel.org> (raw)
In-Reply-To: <Zv2aE7jmE2awLwcl@x1>
On 02/10/2024 21:08, Drew Fustini wrote:
> On Tue, Oct 01, 2024 at 08:58:34AM +0200, Krzysztof Kozlowski wrote:
>> On Mon, Sep 30, 2024 at 11:23:24PM -0700, Drew Fustini wrote:
>>> From: Jisheng Zhang <jszhang@kernel.org>
>>>
>>> Add documentation to describe the DesginWare-based GMAC controllers in
>>> the T-HEAD TH1520 SoC.
>>>
>>> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
>>> Signed-off-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>
>>> [drew: rename compatible, add apb registers as second reg of gmac node]
>>> Signed-off-by: Drew Fustini <dfustini@tenstorrent.com>
>>> ---
>>> .../devicetree/bindings/net/snps,dwmac.yaml | 1 +
>>> .../devicetree/bindings/net/thead,th1520-gmac.yaml | 97 ++++++++++++++++++++++
>>> MAINTAINERS | 1 +
>>> 3 files changed, 99 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/net/snps,dwmac.yaml b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
>>> index 4e2ba1bf788c..474ade185033 100644
>>> --- a/Documentation/devicetree/bindings/net/snps,dwmac.yaml
>>> +++ b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
>>> @@ -99,6 +99,7 @@ properties:
>>> - snps,dwxgmac-2.10
>>> - starfive,jh7100-dwmac
>>> - starfive,jh7110-dwmac
>>> + - thead,th1520-gmac
>>>
>>> reg:
>>> minItems: 1
>>> diff --git a/Documentation/devicetree/bindings/net/thead,th1520-gmac.yaml b/Documentation/devicetree/bindings/net/thead,th1520-gmac.yaml
>>> new file mode 100644
>>> index 000000000000..fef1810b10c4
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/net/thead,th1520-gmac.yaml
>>> @@ -0,0 +1,97 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/net/thead,th1520-gmac.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: T-HEAD TH1520 GMAC Ethernet controller
>>> +
>>> +maintainers:
>>> + - Drew Fustini <dfustini@tenstorrent.com>
>>> +
>>> +description: |
>>> + The TH1520 GMAC is described in the TH1520 Peripheral Interface User Manual
>>> + https://git.beagleboard.org/beaglev-ahead/beaglev-ahead/-/tree/main/docs
>>> +
>>> + Features include
>>> + - Compliant with IEEE802.3 Specification
>>> + - IEEE 1588-2008 standard for precision networked clock synchronization
>>> + - Supports 10/100/1000Mbps data transfer rate
>>> + - Supports RGMII/MII interface
>>> + - Preamble and start of frame data (SFD) insertion in Transmit path
>>> + - Preamble and SFD deletion in the Receive path
>>> + - Automatic CRC and pad generation options for receive frames
>>> + - MDIO master interface for PHY device configuration and management
>>> +
>>> + The GMAC Registers consists of two parts
>>> + - APB registers are used to configure clock frequency/clock enable/clock
>>> + direction/PHY interface type.
>>> + - AHB registers are use to configure GMAC core (DesignWare Core part).
>>> + GMAC core register consists of DMA registers and GMAC registers.
>>> +
>>> +select:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - thead,th1520-gmac
>>> + required:
>>> + - compatible
>>> +
>>> +allOf:
>>> + - $ref: snps,dwmac.yaml#
>>> +
>>> +properties:
>>> + compatible:
>>> + items:
>>> + - enum:
>>> + - thead,th1520-gmac
>>> + - const: snps,dwmac-3.70a
>>> +
>>> + reg:
>>> + items:
>>> + - description: DesignWare GMAC IP core registers
>>> + - description: GMAC APB registers
>>> +
>>> + reg-names:
>>> + items:
>>> + - const: dwmac
>>> + - const: apb
>>
>> I don't get why none of snps,dwmac properties are restricted. How many
>> interrupts do you have here? How many clocks? resets?
>
> Thanks for pointing this out. Yes, I forgot to document the clocks,
> interrupts and resets.
>
> There needs to be 2 clocks (stmmaceth and pclk). There also needs to be
> 2 resets: each GMAC has a reset plus a seperate reset for the GMAC AXI
> interface. There is 1 interrupt (macirq) but it is optional. The BeagleV
> Ahead uses it but the LicheePi 4A does not use the interrupt.
>
> However, I'm uncertain about how to restrict the snps,dwmac properties.
>
> I see that starfive,jh7110-dwmac.yaml has the following logic. Should I
> be adding something like this to restrict the snps,dwmac properties?
>
> ---------------------------------------------------------------------
> allOf:
> - $ref: snps,dwmac.yaml#
>
> - if:
> properties:
> compatible:
> contains:
> const: starfive,jh7100-dwmac
> then:
> properties:
> interrupts:
> minItems: 2
> maxItems: 2
>
> interrupt-names:
> minItems: 2
> maxItems: 2
>
> resets:
> maxItems: 1
>
> reset-names:
> const: ahb
No, that's not necessary. You have one device in this binding, so in
top-level should define how each such property looks like.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-03 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 6:23 [PATCH v3 0/3] Add the dwmac driver support for T-HEAD TH1520 SoC Drew Fustini
2024-10-01 6:23 ` [PATCH v3 1/3] dt-bindings: net: Add T-HEAD dwmac support Drew Fustini
2024-10-01 6:58 ` Krzysztof Kozlowski
2024-10-02 19:08 ` Drew Fustini
2024-10-03 10:42 ` Krzysztof Kozlowski [this message]
2024-10-01 6:23 ` [PATCH v3 2/3] net: stmmac: Add glue layer for T-HEAD TH1520 SoC Drew Fustini
2024-10-01 9:48 ` Emil Renner Berthing
2024-10-03 5:52 ` Drew Fustini
2024-10-01 6:23 ` [PATCH v3 3/3] riscv: dts: thead: Add TH1520 ethernet nodes Drew Fustini
2024-10-02 15:34 ` [PATCH v3 0/3] Add the dwmac driver support for T-HEAD TH1520 SoC Andrew Lunn
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=8f0a6e27-df0c-41fb-8714-10fdfbe976ab@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dfustini@tenstorrent.com \
--cc=drew@pdp7.com \
--cc=edumazet@google.com \
--cc=emil.renner.berthing@canonical.com \
--cc=guoren@kernel.org \
--cc=joabreu@synopsys.com \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peppe.cavallaro@st.com \
--cc=robh@kernel.org \
--cc=wefu@redhat.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).