From: "Rafał Miłecki" <rafal@milecki.pl>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH 2/2] ARM: dts: BCM5301X: Set fixed-link for extra Netgear R8000 CPU ports
Date: Wed, 18 Oct 2023 22:08:48 +0200 [thread overview]
Message-ID: <6dcf098e93f9b49b440a500586939e5f@milecki.pl> (raw)
In-Reply-To: <5a70a1ca-8840-40e9-b598-2ce0d80cbc9e@broadcom.com>
On 2023-10-18 20:10, Florian Fainelli wrote:
> On 10/16/23 08:45, Andrew Lunn wrote:
>> On Mon, Oct 16, 2023 at 05:36:24PM +0200, Rafał Miłecki wrote:
>>> On 2023-10-14 18:50, Andrew Lunn wrote:
>>>> On Fri, Oct 13, 2023 at 12:33:14PM +0200, Rafał Miłecki wrote:
>>>>> From: Rafał Miłecki <rafal@milecki.pl>
>>>>>
>>>>> While switch ports 5 and 7 are disabled (vendor designed port 8 to
>>>>> be
>>>>> used for CPU traffic) they could be used strictly technically. For
>>>>> some
>>>>> reason however both those ports need forcing link to be usable.
>>>>
>>>> This explanation is not making much sense to me.
>>>>
>>>> I assume this board does not have an RJ45 for these two ports? But
>>>> does it have a header so you can access the MII interface?
>>>
>>> This PATCH as it is requires a basic familiarity with Northstar
>>> platform
>>> or checking bcm-ns.dtsi.
>>>
>>> All Northstar (BCM5301X) devices have 3 Ethernet interfaces. 99% of
>>> them
>>> have:
>>> 1. gmac0 connected to port 5
>>> 2. gmac1 connected to port 7
>>> 3. gmac2 connected to port 8
>>> (it's described in bcm-ns.dtsi).
>>>
>>>
>>> Some vendors decide to use gmac0 and switch port 5. They fill NVRAM
>>> with
>>> MAC for gmac0.
>>>
>>> Some vendors decide to use gmac2 & port 8. They set MAC for gmac2.
>>>
>>>
>>> Netgear decided to use gmac2 & port 8 for R8000. They fill NVRAM with
>>> MAC for gmac2.
>>>
>>> If you however insist on using gmac0 you could do that. That just
>>> requires setting up gmac0 with a custom/random MAC and forcing link
>>> for
>>> switch ports as described in this PATCH.
>>
>> If the ports are not used, you have them set to disabled, why do they
>> need a fixed-link? That is what i don't understand yet.
>
> It seems to me like the commit message could be reworded such that:
>
> Even though ports 5 and 7 are disabled and the system is intended to
> use port 8, make it possible for users to experiment with using ports
> 5 and/or 7 if they desire so by ensuring that they have the necessary
> 'fixed-link' properties to describe the internal connection within the
> SoC between the switch ports and the two Ethernet controllers.
>
> Rafal, does that capture the intent? If so I can amend the commit
> message while applying.
I believe so. You're correct that in practice it's for experimenting
mainly. Formally it also describes hardware which DT is for.
I'm sure we can find a lot of *disabled* hardware blocks in Linux's DTS
files that are still described for the sake of documenting it.
--
Rafał Miłecki
next prev parent reply other threads:[~2023-10-18 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 10:33 [PATCH 1/2] ARM: dts: BCM5301X: Explicitly disable unused switch CPU ports Rafał Miłecki
2023-10-13 10:33 ` [PATCH 2/2] ARM: dts: BCM5301X: Set fixed-link for extra Netgear R8000 " Rafał Miłecki
2023-10-14 16:50 ` Andrew Lunn
2023-10-16 15:36 ` Rafał Miłecki
2023-10-16 15:45 ` Andrew Lunn
2023-10-18 18:10 ` Florian Fainelli
2023-10-18 20:08 ` Rafał Miłecki [this message]
2023-10-18 20:04 ` Rafał Miłecki
2023-10-18 20:09 ` Andrew Lunn
2023-10-23 18:33 ` Florian Fainelli
2023-10-23 18:36 ` Florian Fainelli
2023-10-23 19:48 ` Rafał Miłecki
2023-10-18 18:26 ` [PATCH 1/2] ARM: dts: BCM5301X: Explicitly disable unused switch " 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=6dcf098e93f9b49b440a500586939e5f@milecki.pl \
--to=rafal@milecki.pl \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.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).