From: Krzysztof Kozlowski <krzk@kernel.org>
To: Swathi K S <swathi.ks@samsung.com>,
krzk+dt@kernel.org, linux-fsd@tesla.com, robh@kernel.org,
conor+dt@kernel.org, richardcochran@gmail.com,
alim.akhtar@samsung.com
Cc: jayati.sahu@samsung.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pankaj.dubey@samsung.com, ravi.patel@samsung.com,
gost.dev@samsung.com
Subject: Re: [PATCH v7 1/2] arm64: dts: fsd: Add Ethernet support for FSYS0 Block of FSD SoC
Date: Sat, 1 Mar 2025 14:59:26 +0100 [thread overview]
Message-ID: <7328e538-31cf-4674-83d2-943f1a2d1455@kernel.org> (raw)
In-Reply-To: <20250220073527.22233-2-swathi.ks@samsung.com>
On 20/02/2025 08:35, Swathi K S wrote:
> &pinctrl_peric {
> diff --git a/arch/arm64/boot/dts/tesla/fsd.dtsi b/arch/arm64/boot/dts/tesla/fsd.dtsi
> index 690b4ed9c29b..01850fbf761f 100644
> --- a/arch/arm64/boot/dts/tesla/fsd.dtsi
> +++ b/arch/arm64/boot/dts/tesla/fsd.dtsi
> @@ -1007,6 +1007,26 @@
> clocks = <&clock_fsys0 UFS0_MPHY_REFCLK_IXTAL26>;
> clock-names = "ref_clk";
> };
> +
> + ethernet0: ethernet@15300000 {
> + compatible = "tesla,fsd-ethqos";
I don't see bindings in the linux-next, so I am dropping this patch from
my queue. Please resend when the bindings hit the linux-next.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-01 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250220073939epcas5p24b926b2dd3bcfda426b03309d8c29590@epcas5p2.samsung.com>
2025-02-20 7:35 ` [PATCH v7 0/2] arm64: dts: fsd: Add Ethernet support for FSD SoC Swathi K S
2025-02-20 7:35 ` [PATCH v7 1/2] arm64: dts: fsd: Add Ethernet support for FSYS0 Block of " Swathi K S
2025-03-01 13:59 ` Krzysztof Kozlowski [this message]
2025-03-06 3:48 ` Swathi K S
2025-02-20 7:35 ` [PATCH v7 2/2] arm64: dts: fsd: Add Ethernet support for PERIC " Swathi K S
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=7328e538-31cf-4674-83d2-943f1a2d1455@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gost.dev@samsung.com \
--cc=jayati.sahu@samsung.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsd@tesla.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=richardcochran@gmail.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).