From: Kurt Kanzenbach <kurt@linutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Richard Cochran <richardcochran@gmail.com>,
Kamil Alkhouri <kamil.alkhouri@hs-offenburg.de>,
ilias.apalodimas@linaro.org
Subject: Re: [RFC PATCH 9/9] dt-bindings: net: dsa: Add documentation for Hellcreek switches
Date: Mon, 22 Jun 2020 14:02:19 +0200 [thread overview]
Message-ID: <87imfjtik4.fsf@kurt> (raw)
In-Reply-To: <20200619135657.GF304147@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
On Fri Jun 19 2020, Andrew Lunn wrote:
>> > The switch is 100/100Mbps right? The MAC is only Fast ethernet. Do you
>> > need some properties in the port@0 node to tell the switch to only use
>> > 100Mbps? I would expect it to default to 1G. Not looked at the code
>> > yet...
>>
>> No, that is not needed. That is a hardware configuration and AFAIK
>> cannot be changed at run time.
>
> I was wondering about that in general. I did not spot any code in the
> driver dealing with results from the PHY auto-neg. So you are saying
> the CPU is fixed speed, by strapping? But what about the other ports?
> Does the MAC need to know the PHY has negotiated 10Half, not 1G? Would
> that not make a difference to your TSN?
Indeed, that does make a difference. I've checked with the vendor. The
current version of the switch IP does not support configuring the speed
etc. at run time. It is hard wired to 100 Mbit/s or 1000 Mbit/s for
now. Later versions of the chip might support setting the speed etc. via
configuration registers. As a result the PHYs at the front ports should
be programmed to only advertise 100 Mbit/s or 1G depending on the
hardware setup.
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-06-22 12:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 6:40 [RFC PATCH 0/9] Hirschmann Hellcreek DSA driver Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 1/9] net: dsa: Add tag handling for Hirschmann Hellcreek switches Kurt Kanzenbach
2020-06-18 13:42 ` Andrew Lunn
2020-06-18 6:40 ` [RFC PATCH 2/9] net: dsa: Add DSA driver " Kurt Kanzenbach
2020-06-18 15:22 ` Andrew Lunn
2020-06-19 8:12 ` Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 3/9] net: dsa: hellcreek: Add PTP clock support Kurt Kanzenbach
2020-06-18 15:46 ` Jakub Kicinski
2020-06-19 8:13 ` Kurt Kanzenbach
2020-06-18 17:23 ` Andrew Lunn
2020-06-19 8:26 ` Kurt Kanzenbach
2020-06-19 13:40 ` Andrew Lunn
2020-06-22 11:52 ` Kurt Kanzenbach
2020-06-24 13:03 ` Richard Cochran
2020-06-25 7:08 ` Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 4/9] net: dsa: hellcreek: Add support for hardware timestamping Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 5/9] net: dsa: hellcreek: Add TAPRIO offloading support Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 6/9] net: dsa: hellcreek: Add debugging mechanisms Kurt Kanzenbach
2020-06-18 17:34 ` Andrew Lunn
2020-06-19 8:36 ` Kurt Kanzenbach
2020-06-19 13:42 ` Andrew Lunn
2020-06-22 12:32 ` Kurt Kanzenbach
2020-06-22 13:55 ` Andrew Lunn
2020-06-23 6:07 ` Kurt Kanzenbach
2020-06-22 14:14 ` Vladimir Oltean
2020-06-23 6:04 ` Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 7/9] net: dsa: hellcreek: Add PTP status LEDs Kurt Kanzenbach
2020-06-18 17:46 ` Andrew Lunn
2020-06-19 8:45 ` Kurt Kanzenbach
2020-06-19 13:52 ` Andrew Lunn
2020-06-18 6:40 ` [RFC PATCH 8/9] dt-bindings: Add vendor prefix for Hirschmann Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 9/9] dt-bindings: net: dsa: Add documentation for Hellcreek switches Kurt Kanzenbach
2020-06-18 13:47 ` Andrew Lunn
2020-06-19 8:47 ` Kurt Kanzenbach
2020-06-19 13:56 ` Andrew Lunn
2020-06-22 12:02 ` Kurt Kanzenbach [this message]
2020-06-22 13:49 ` Andrew Lunn
2020-06-23 6:09 ` Kurt Kanzenbach
2020-06-18 17:40 ` Florian Fainelli
2020-06-19 8:48 ` Kurt Kanzenbach
2020-06-22 12:05 ` Kurt Kanzenbach
2020-06-26 17:11 ` 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=87imfjtik4.fsf@kurt \
--to=kurt@linutronix.de \
--cc=andrew@lunn.ch \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kamil.alkhouri@hs-offenburg.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@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).