From: "Sriranjani P" <sriranjani.p@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
<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>,
"'Jayati Sahu'" <jayati.sahu@samsung.com>,
<swathi.ks@samsung.com>
Subject: RE: [PATCH v2 4/4] arm64: dts: fsd: Add Ethernet support for PERIC Block of FSD SoC
Date: Mon, 14 Aug 2023 15:57:29 +0530 [thread overview]
Message-ID: <000101d9ce99$f454da20$dcfe8e60$@samsung.com> (raw)
In-Reply-To: <7d74a96e-e3a5-118c-04a9-e8ed95fffa54@linaro.org>
> -----Original Message-----
> From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@linaro.org]
> Sent: 12 January 2023 15:07
> 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; Jayati Sahu
> <jayati.sahu@samsung.com>
> Subject: Re: [PATCH v2 4/4] arm64: dts: fsd: Add Ethernet support for PERIC
> Block of FSD SoC
>
> On 11/01/2023 08:54, Sriranjani P wrote:
> > The FSD SoC contains two instances of Synopsys DWC QoS Ethernet IP,
> > one in
> > FSYS0 block and other in PERIC block.
> >
> > Adds device tree node for Ethernet in PERIC Block and enables the same
> > for FSD platform.
> >
> > Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> > Signed-off-by: Jayati Sahu <jayati.sahu@samsung.com>
> > Signed-off-by: Sriranjani P <sriranjani.p@samsung.com>
> > ---
> > arch/arm64/boot/dts/tesla/fsd-evb.dts | 9 ++++
> > arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi | 56
> ++++++++++++++++++++++
> > arch/arm64/boot/dts/tesla/fsd.dtsi | 29 +++++++++++
> > 3 files changed, 94 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/tesla/fsd-evb.dts
> > b/arch/arm64/boot/dts/tesla/fsd-evb.dts
> > index ca0c1a28d562..2c0cbe775e04 100644
> > --- a/arch/arm64/boot/dts/tesla/fsd-evb.dts
> > +++ b/arch/arm64/boot/dts/tesla/fsd-evb.dts
> > @@ -39,6 +39,15 @@
> > };
> > };
> >
> > +ðernet_1 {
> > + status = "okay";
> > +
> > + fixed-link {
> > + speed = <1000>;
> > + full-duplex;
> > + };
> > +};
> > +
> > &fin_pll {
> > clock-frequency = <24000000>;
> > };
> > diff --git a/arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi
> > b/arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi
> > index 7ccc0738a149..c955bf159786 100644
> > --- a/arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi
> > +++ b/arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi
> > @@ -395,6 +395,62 @@
> > samsung,pin-pud = <FSD_PIN_PULL_UP>;
> > samsung,pin-drv = <FSD_PIN_DRV_LV1>;
> > };
> > +
> > + eth1_tx_clk: eth1-tx-clk-pins {
> > + samsung,pins = "gpf2-0";
> > + samsung,pin-function = <FSD_PIN_FUNC_2>;
> > + samsung,pin-pud = <FSD_PIN_PULL_DOWN>;
> > + samsung,pin-drv = <FSD_PIN_DRV_LV6>;
> > + };
> > +
> > + eth1_tx_data: eth1-tx-data-pins {
> > + samsung,pins = "gpf2-1", "gpf2-2", "gpf2-3", "gpf2-4";
> > + samsung,pin-function = <FSD_PIN_FUNC_2>;
> > + samsung,pin-pud = <FSD_PIN_PULL_UP>;
> > + samsung,pin-drv = <FSD_PIN_DRV_LV6>;
> > + };
> > +
> > + eth1_tx_ctrl: eth1-tx-ctrl-pins {
> > + samsung,pins = "gpf2-5";
> > + samsung,pin-function = <FSD_PIN_FUNC_2>;
> > + samsung,pin-pud = <FSD_PIN_PULL_UP>;
> > + samsung,pin-drv = <FSD_PIN_DRV_LV6>;
> > + };
> > +
> > + eth1_phy_intr: eth1-phy-intr-pins {
> > + samsung,pins = "gpf2-6";
> > + samsung,pin-function = <FSD_PIN_FUNC_2>;
> > + samsung,pin-pud = <FSD_PIN_PULL_UP>;
> > + samsung,pin-drv = <FSD_PIN_DRV_LV4>;
> > + };
> > +
> > + eth1_rx_clk: eth1-rx-clk-pins {
> > + samsung,pins = "gpf3-0";
> > + samsung,pin-function = <FSD_PIN_FUNC_2>;
> > + samsung,pin-pud = <FSD_PIN_PULL_UP>;
> > + samsung,pin-drv = <FSD_PIN_DRV_LV6>;
> > + };
> > +
> > + eth1_rx_data: eth1-rx-data-pins {
> > + samsung,pins = "gpf3-1", "gpf3-2", "gpf3-3", "gpf3-4";
> > + samsung,pin-function = <FSD_PIN_FUNC_2>;
> > + samsung,pin-pud = <FSD_PIN_PULL_UP>;
> > + samsung,pin-drv = <FSD_PIN_DRV_LV6>;
> > + };
> > +
> > + eth1_rx_ctrl: eth1-rx-ctrl-pins {
> > + samsung,pins = "gpf3-5";
> > + samsung,pin-function = <FSD_PIN_FUNC_2>;
> > + samsung,pin-pud = <FSD_PIN_PULL_UP>;
> > + samsung,pin-drv = <FSD_PIN_DRV_LV6>;
> > + };
> > +
> > + eth1_mdio: eth1-mdio-pins {
> > + samsung,pins = "gpf3-6", "gpf3-7";
> > + samsung,pin-function = <FSD_PIN_FUNC_2>;
> > + samsung,pin-pud = <FSD_PIN_PULL_UP>;
> > + samsung,pin-drv = <FSD_PIN_DRV_LV4>;
> > + };
> > };
> >
> > &pinctrl_pmu {
> > diff --git a/arch/arm64/boot/dts/tesla/fsd.dtsi
> > b/arch/arm64/boot/dts/tesla/fsd.dtsi
> > index ade707cc646b..8807055807dd 100644
> > --- a/arch/arm64/boot/dts/tesla/fsd.dtsi
> > +++ b/arch/arm64/boot/dts/tesla/fsd.dtsi
> > @@ -33,6 +33,7 @@
> > spi1 = &spi_1;
> > spi2 = &spi_2;
> > eth0 = ðernet_0;
> > + eth1 = ðernet_1;
>
> Nope for the reasons I explained last time.
Sorry somehow I'm not able to find my previous mail chain.
I had replied to your comment in the previous version of the mail.
In this case alias id is used to differentiate between Ethernet instance 0 and 1 in the driver code.
>
> > };
> >
> > cpus {
> > @@ -882,6 +883,34 @@
> > phy-mode = "rgmii";
> > status = "disabled";
> > };
> > +
> > + ethernet_1: ethernet@14300000 {
>
> Do not add nodes to the end.
If you mean to say that the nodes are supposed to be in the increasing order of physical address,
I can see that the existing file is not arranged in that format. If that is required I can first fix the
existing file and post the revised patch for the same.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2023-08-14 12:15 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
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
2023-01-11 7:54 ` [PATCH v2 2/4] net: stmmac: dwc-qos: Add FSD EQoS support Sriranjani P
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
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 [this message]
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='000101d9ce99$f454da20$dcfe8e60$@samsung.com' \
--to=sriranjani.p@samsung.com \
--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=jayati.sahu@samsung.com \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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=swathi.ks@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