From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: "Rafał Miłecki" <rafal@milecki.pl>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH 5/5] ARM: dts: BCM5301X: Disable unused gmac0 and gmac2 on Asus RT-AC88U
Date: Fri, 1 Apr 2022 14:36:26 +0300 [thread overview]
Message-ID: <21285586-7c9a-5fda-0f07-1d43312ea8c6@arinc9.com> (raw)
In-Reply-To: <06e49b67a2e2f75040c51f8a05c329ef@milecki.pl>
On 01/04/2022 13:40, Rafał Miłecki wrote:
> On 2022-04-01 12:20, Arınç ÜNAL wrote:
>> Disable gmac0 and gmac2 which are currently not used. This doesn't
>> seem to
>> be implemented yet on drivers/net/ethernet/broadcom/bgmac-bcma.c but this
>> change is harmless, nonetheless.
>
> It doesn't matter whether Linux respects that.
>
>
>> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
>> ---
>> arch/arm/boot/dts/bcm47094-asus-rt-ac88u.dts | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/bcm47094-asus-rt-ac88u.dts
>> b/arch/arm/boot/dts/bcm47094-asus-rt-ac88u.dts
>> index 2f944d1c0330..0f5c5d576814 100644
>> --- a/arch/arm/boot/dts/bcm47094-asus-rt-ac88u.dts
>> +++ b/arch/arm/boot/dts/bcm47094-asus-rt-ac88u.dts
>> @@ -242,11 +242,19 @@ fixed-link {
>> };
>> };
>>
>> +&gmac0 {
>> + status = "disabled";
>> +};
>> +
>> &gmac1 {
>> nvmem-cells = <&et1macaddr>;
>> nvmem-cell-names = "mac-address";
>> };
>>
>> +&gmac2 {
>> + status = "disabled";
>> +};
>
> I don't think that is correct. Those interfaces are still there and
> they are actually connected to switch ports. If you configure your
> switch properly you can use them.
>
> Someone may want to use e.g. gmac0 & gmac1 with two sets of ports to
> speed up network communication.
>
> I think gmac2 is required if you want to enable FA (flow acceleration /
> accelerator) - even though there isn't Linux driver for it yet.
>
> They are not disabled / unpopulated / non functional interfaces.
I understand your point. However, while we're not supposed to care
whether the kernel respects the bindings, don't we also need to make the
bindings work on the version of the Linux kernel we're submitting the
bindings to?
With the current way DSA works, only one switch port can be used as a
CPU port. If we were to remove the status = "disabled" property from
port@8 which connects to gmac2, it'd break the communication between the
switch and the CPU on the current Linux kernel.
If a new driver or a feature is introduced, we should update the
bindings accordingly afterwards.
For this reason, I don't see an issue with explaining the driver side of
it on the commit log for DT bindings.
DT bindings are not exactly static either. Someone could want to use
gmac2 instead of gmac1. In that case, I think they should change the
bindings themselves as it's for their own use.
By the way, gmac0 would be wired to port@5 but since port@5 is wired to
realtek switch's port@6 instead, it's actually non-functional.
Arınç
next prev parent reply other threads:[~2022-04-01 11:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 10:19 [PATCH 1/5] ARM: dts: BCM5301X: Fix DTC warning for NAND node Arınç ÜNAL
2022-04-01 10:19 ` [PATCH 2/5] ARM: dts: BCM5301X: Remove cell properties from srab ports on Asus RT-AC88U Arınç ÜNAL
2022-04-01 10:28 ` Rafał Miłecki
2022-04-04 18:35 ` Florian Fainelli
2022-04-01 10:20 ` [PATCH 3/5] ARM: dts: BCM5301X: Add rgmii to port@5 of Broadcom switch " Arınç ÜNAL
2022-04-04 18:36 ` Florian Fainelli
2022-04-01 10:20 ` [PATCH 4/5] ARM: dts: BCM5301X: Retrieve gmac1 MAC address from NVRAM " Arınç ÜNAL
2022-04-01 10:32 ` Rafał Miłecki
2022-04-04 18:36 ` Florian Fainelli
2022-04-01 10:20 ` [PATCH 5/5] ARM: dts: BCM5301X: Disable unused gmac0 and gmac2 " Arınç ÜNAL
2022-04-01 10:40 ` Rafał Miłecki
2022-04-01 11:36 ` Arınç ÜNAL [this message]
2022-04-06 18:16 ` Florian Fainelli
2022-04-10 9:20 ` Arınç ÜNAL
2022-04-01 10:27 ` [PATCH 1/5] ARM: dts: BCM5301X: Fix DTC warning for NAND node Rafał Miłecki
2022-04-04 18:35 ` Florian Fainelli
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=21285586-7c9a-5fda-0f07-1d43312ea8c6@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@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).