From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sriranjani P <sriranjani.p@samsung.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, alexandre.torgue@foss.st.com,
peppe.cavallaro@st.com, joabreu@synopsys.com,
mcoquelin.stm32@gmail.com
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, pankaj.dubey@samsung.com,
alim.akhtar@samsung.com, ravi.patel@samsung.com
Subject: Re: [PATCH v2 1/4] dt-bindings: net: Add FSD EQoS device tree bindings
Date: Thu, 12 Jan 2023 10:25:13 +0100 [thread overview]
Message-ID: <f566a556-4f9e-f5df-1ea4-2c8f633bdb4c@linaro.org> (raw)
In-Reply-To: <20230111075422.107173-2-sriranjani.p@samsung.com>
On 11/01/2023 08:54, Sriranjani P wrote:
> Add FSD Ethernet compatible in Synopsys dt-bindings document. Add FSD
> Ethernet YAML schema to enable the DT validation.
>
> Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> Signed-off-by: Ravi Patel <ravi.patel@samsung.com>
> Signed-off-by: Sriranjani P <sriranjani.p@samsung.com>
> ---
> .../devicetree/bindings/net/snps,dwmac.yaml | 1 +
> .../net/tesla,dwc-qos-ethernet-4.21.yaml | 103 ++++++++++++++++++
> 2 files changed, 104 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/tesla,dwc-qos-ethernet-4.21.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/snps,dwmac.yaml b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
> index 2f909ffe2fe8..e8d53061fd35 100644
> --- a/Documentation/devicetree/bindings/net/snps,dwmac.yaml
> +++ b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
> @@ -89,6 +89,7 @@ properties:
> - snps,dwmac-5.10a
> - snps,dwxgmac
> - snps,dwxgmac-2.10
> + - tesla,dwc-qos-ethernet-4.21
I don't get, why did you add the IP version number? Can Tesla FSD come
with different ones? The compatible should be specific to SoC and that's
all. Also keep consistent naming, so this is a "mac", right?
>
> reg:
> minItems: 1
> diff --git a/Documentation/devicetree/bindings/net/tesla,dwc-qos-ethernet-4.21.yaml b/Documentation/devicetree/bindings/net/tesla,dwc-qos-ethernet-4.21.yaml
> new file mode 100644
> index 000000000000..d0dfc4a38d17
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/tesla,dwc-qos-ethernet-4.21.yaml
> @@ -0,0 +1,103 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/tesla,dwc-qos-ethernet-4.21.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: FSD Ethernet Quality of Service Device Tree Bindings
Drop "Device Tree Bindings"
> +
> +allOf:
> + - $ref: "snps,dwmac.yaml#"
Drop quoets.
> +
> +maintainers:
> + - Sriranjani P <sriranjani.p@samsung.com>
> +
> +properties:
> + compatible:
> + const: tesla,dwc-qos-ethernet-4.21.yaml
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + minItems: 4
> +
> + clock-names:
> + minItems: 4
Why rx clock might be not connected?
> + items:
> + - const: ptp_ref
> + - const: master_bus
> + - const: slave_bus
> + - const: tx
> + - const: rx
> + - const: master2_bus
> + - const: slave2_bus
> + - const: eqos_rxclk_mux
> + - const: eqos_phyrxclk
> + - const: dout_peric_rgmii_clk
You have here 10 clocks, but snps,dwmac allows maximum 8. You need to
update it and fix any other dependent schemas.
> +
> + rx-clock-skew:
Does not look like generic property. Missing vendor prefix, description,
constraints.
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> +
> + iommus:
> + maxItems: 1
> +
> + phy-mode:
> + $ref: ethernet-controller.yaml#/properties/phy-connection-type
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> + - rx-clock-skew
> + - iommus
> + - phy-mode
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/fsd-clk.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + ethernet_1: ethernet@14300000 {
> + compatible = "tesla,dwc-qos-ethernet-4.21";
> + reg = <0x0 0x14300000 0x0 0x10000>;
Are you sure you tested the bindings? 100% sure?
> + interrupts = <GIC_SPI 176 IRQ_TYPE_LEVEL_HIGH>;
> + clocks =
Don't introduce fake blank lines.
> + <&clock_peric PERIC_EQOS_TOP_IPCLKPORT_CLK_PTP_REF_I>,
> + <&clock_peric PERIC_EQOS_TOP_IPCLKPORT_ACLK_I>,
> + <&clock_peric PERIC_EQOS_TOP_IPCLKPORT_HCLK_I>,
> + <&clock_peric PERIC_EQOS_TOP_IPCLKPORT_RGMII_CLK_I>,
> + <&clock_peric PERIC_EQOS_TOP_IPCLKPORT_CLK_RX_I>,
> + <&clock_peric PERIC_BUS_D_PERIC_IPCLKPORT_EQOSCLK>,
> + <&clock_peric PERIC_BUS_P_PERIC_IPCLKPORT_EQOSCLK>,
> + <&clock_peric PERIC_EQOS_PHYRXCLK_MUX>,
> + <&clock_peric PERIC_EQOS_PHYRXCLK>,
> + <&clock_peric PERIC_DOUT_RGMII_CLK>;
> + clock-names =
Ditto
> + "ptp_ref",
> + "master_bus",
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-12 9:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230111075438epcas5p44ac566fdedff7c59bd416b7de28f3922@epcas5p4.samsung.com>
2023-01-11 7:54 ` [PATCH v2 0/4] net: stmmac: dwc-qos: Add FSD EQoS support Sriranjani P
[not found] ` <CGME20230111075441epcas5p4f0b503484de61228e3ed71a4041cdd41@epcas5p4.samsung.com>
2023-01-11 7:54 ` [PATCH v2 1/4] dt-bindings: net: Add FSD EQoS device tree bindings Sriranjani P
2023-01-12 9:25 ` Krzysztof Kozlowski [this message]
[not found] ` <CGME20230111075445epcas5p2b94c8ddc5608c0b20d3d28b049592b4a@epcas5p2.samsung.com>
2023-01-11 7:54 ` [PATCH v2 2/4] net: stmmac: dwc-qos: Add FSD EQoS support Sriranjani P
[not found] ` <CGME20230111075450epcas5p3f13b94bfeaa66d386aa51f87ca4ec5bf@epcas5p3.samsung.com>
2023-01-11 7:54 ` [PATCH v2 3/4] arm64: dts: fsd: Add Ethernet support for FSYS0 Block of FSD SoC Sriranjani P
2023-01-12 9:35 ` Krzysztof Kozlowski
2023-08-14 10:18 ` Sriranjani P
2023-08-14 19:52 ` Krzysztof Kozlowski
[not found] ` <CGME20230111075455epcas5p1951d1981f15d252e09281621ef5fbf15@epcas5p1.samsung.com>
2023-01-11 7:54 ` [PATCH v2 4/4] arm64: dts: fsd: Add Ethernet support for PERIC " Sriranjani P
2023-01-12 9:37 ` Krzysztof Kozlowski
2023-08-14 10:27 ` Sriranjani P
2023-08-14 19:55 ` Krzysztof Kozlowski
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=f566a556-4f9e-f5df-1ea4-2c8f633bdb4c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=alim.akhtar@samsung.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pankaj.dubey@samsung.com \
--cc=peppe.cavallaro@st.com \
--cc=ravi.patel@samsung.com \
--cc=robh+dt@kernel.org \
--cc=sriranjani.p@samsung.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).