From: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
James Cowgill <james.cowgill@blaize.com>,
Matt Redfearn <matthew.redfearn@blaize.com>,
Neil Jones <neil.jones@blaize.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64/dts/blaize: Enable Ethernet on CB2 board
Date: Fri, 11 Jul 2025 15:02:18 +0100 [thread overview]
Message-ID: <1c0b5db2-ebfa-4ab0-94df-4a2d70da0552@blaize.com> (raw)
In-Reply-To: <7dffc2a4-c657-441b-86e5-b3869a72a800@kernel.org>
On 11/07/2025 14:51, Krzysztof Kozlowski wrote:
> On 11/07/2025 15:36, Nikolaos Pasaloukos wrote:
>> Use the Synopsys gigabit Ethernet controller on the Blaize BLZP1600
>> SoC to provide Ethernet connectivity using the TI DP83867 PHY which is
>> available on the CB2 board via an RJ45 connector.
>>
>> Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
>> ---
>> arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts | 22 ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts b/arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts
>> index fb5415eb347a028fc65090027a4c4fc89c8280f5..cbe8f0930ad3741b0e770dd7d494931e3b939815 100644
>> --- a/arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts
>> +++ b/arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts
>> @@ -6,6 +6,7 @@
>> /dts-v1/;
>>
>> #include "blaize-blzp1600-som.dtsi"
>> +#include <dt-bindings/net/ti-dp83867.h>
>>
>> / {
>> model = "Blaize BLZP1600 SoM1600P CB2 Development Board";
>> @@ -14,6 +15,7 @@ / {
>>
>> aliases {
>> serial0 = &uart0;
>> + ethernet = &gmac;
>> };
>>
>> chosen {
>> @@ -117,3 +119,23 @@ &gpio0 {
>> "BOARD_ID_1", /* GPIO_30 */
>> "BOARD_ID_2"; /* GPIO_31 */
>> };
>> +
>> +&gmac {
> Are you sure you follow DTS coding style? Which sorting rule is used by
> Blaize?
Hi Krzysztof,
First of all, thank you for your fast review. Apologies that I missed
that I missed that one, it was meant to be alphabetical, so above the
gpio0 section. Thanks for catching that.
>
>> + status = "okay";
>> + snps,reset-delays-us = <0 10000 50000>;
>> + snps,reset-gpio = <&gpio0 12 GPIO_ACTIVE_LOW>;
> Do not use deprecated properties. This is new code, not legacy.
>
>
> Best regards,
> Krzysztof
Thanks, I'll remove those.
Best regards,
Niko
prev parent reply other threads:[~2025-07-11 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 13:36 [PATCH 0/2] arm64/blaize: Enable Ethernet to SoC & CB2 Nikolaos Pasaloukos
2025-07-11 13:36 ` [PATCH 1/2] arm64/dts/blaize: Enable Ethernet support for BLZP1600 Nikolaos Pasaloukos
2025-07-11 13:50 ` Krzysztof Kozlowski
2025-07-11 13:36 ` [PATCH 2/2] arm64/dts/blaize: Enable Ethernet on CB2 board Nikolaos Pasaloukos
2025-07-11 13:51 ` Krzysztof Kozlowski
2025-07-11 14:02 ` Nikolaos Pasaloukos [this message]
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=1c0b5db2-ebfa-4ab0-94df-4a2d70da0552@blaize.com \
--to=nikolaos.pasaloukos@blaize.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.cowgill@blaize.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.redfearn@blaize.com \
--cc=neil.jones@blaize.com \
--cc=robh@kernel.org \
/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).