From: "Russell King (Oracle)" <firstname.lastname@example.org> To: Vladimir Oltean <email@example.com> Cc: Prasanna Vengateshan <firstname.lastname@example.org>, Andrew Lunn <email@example.com>, firstname.lastname@example.org, email@example.com, UNGLinuxDriver@microchip.com, Woojung.Huh@microchip.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Re: [PATCH v3 net-next 05/10] net: dsa: microchip: add DSA support for microchip lan937x Date: Wed, 4 Aug 2021 10:59:54 +0100 [thread overview] Message-ID: <20210804095954.GN22278@shell.armlinux.org.uk> (raw) In-Reply-To: <20210803235401.rctfylazg47cjah5@skbuf> On Wed, Aug 04, 2021 at 02:54:01AM +0300, Vladimir Oltean wrote: > On Tue, Aug 03, 2021 at 10:24:27PM +0530, Prasanna Vengateshan wrote: > > Thanks Vladimir & Andrew for the right pointers and info. The thread talks about > > "rgmii-*" are going to be applied by the PHY only as per the doc. For fixed- > > link, MAC needs to add the delay. This fixed-link can be No-PHY or MAC-MAC or > > MAC to in-accessible PHY. In such case, i am not convinced in using rgmii-tx- > > delay-ps & rgmii-rx-delay-ps on the MAC side and apply delay. I still think > > proposed code in earlier mail thread should still be okay. > > Why? I genuinely do not understand your reasoning > > - I read a thread that brings some arguments for which MACs should not > add delays based on the delay type in the "rgmii-*" phy-mode string > [ but based on explicit rgmii-tx-delay-ps and rgmii-rx-delay-ps > properties under the MAC OF node; this is written in the same > message as the quote that you chose ] > > - I acknowledge that in certain configurations I need the MAC to apply > internal delays. > > => I disagree that I should parse the rgmii-tx-delay-ps and > rgmii-rx-delay-ps OF properties of the MAC, just apply RGMII delays > based on the "rgmii-*" phy-mode string value, when I am a DSA CPU > port and in no other circumstance > > ?! > > I mean, feel free to feel convinced or not, but you have not actually > brought any argument to the table here, or I'm not seeing it. > > Anyway, I don't believe that whatever you decide to do with the RGMII > delays is likely to be a decisive factor in whether the patches are > accepted or not, considering the fact that traditionally, everyone did > what suited their board best and that's about it; I will stop pushing back. > > I have a theory that all the RGMII setups driven by the Linux PHY > library cannot all work at the same time, with the same code base. > Someone will sooner or later come and change a driver to make it do what > they need, which will break what the original author intended, which > will then be again patched, which will again break ..., which .... This is why we need to have a clear definition of what the various RGMII interface types are, how and where they are applied, and make sure everyone sticks to that. We have this documented in Documentation/networking/phy.rst. The RGMII interface modes _only_ determine how the PHY should be configured - they do not determine how the MAC should be configured (with /maybe/ the exception of PHY_INTERFACE_MODE_RGMII allowing the MAC to insert "default delays".) In the case of a fixed link, there is no "PHY" as such, but the PHY interface mode describes the properties of the link from the MAC perspective, since it is specified in the MAC node. So, if we have e.g. PHY_INTERFACE_MODE_RGMII_TXID, then from the MAC perspective, we expect the device on the other end of the fixed link to be adding the transmit data line delay. Since we have a fixed link though, we have no way to communicate that to the other side - but the delays do need to be configured to conform with RGMII. An interesting point here, however, is the mv88e6xxx DSA driver - it appears to set the RGMII delays for _all_ ports based on what is in the DT node for the port. So, even if you have a port operating in RGMII with an external PHY, specifying a phy-mode of rgmii-txid results in that being configured at the DSA end of the RGMII link. Andrew - we may need to look at that since it doesn't conform to what we have in the documentation... -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-08-04 10:00 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-23 17:30 [PATCH v3 net-next 00/10] net: dsa: microchip: DSA driver support for LAN937x switch Prasanna Vengateshan 2021-07-23 17:30 ` [PATCH v3 net-next 01/10] dt-bindings: net: dsa: dt bindings for microchip lan937x Prasanna Vengateshan 2021-07-26 22:49 ` Rob Herring 2021-07-23 17:31 ` [PATCH v3 net-next 02/10] net: dsa: move mib->cnt_ptr reset code to ksz_common.c Prasanna Vengateshan 2021-07-23 18:53 ` Vladimir Oltean 2021-07-23 17:31 ` [PATCH v3 net-next 03/10] net: phy: Add support for LAN937x T1 phy driver Prasanna Vengateshan 2021-08-11 17:52 ` Prasanna Vengateshan 2021-07-23 17:31 ` [PATCH v3 net-next 04/10] net: dsa: tag_ksz: add tag handling for Microchip LAN937x Prasanna Vengateshan 2021-07-23 19:23 ` Vladimir Oltean 2021-07-23 17:31 ` [PATCH v3 net-next 05/10] net: dsa: microchip: add DSA support for microchip lan937x Prasanna Vengateshan 2021-07-31 15:04 ` Vladimir Oltean 2021-07-31 22:05 ` Andrew Lunn 2021-08-02 21:33 ` Vladimir Oltean 2021-08-03 14:43 ` Andrew Lunn 2021-08-03 15:05 ` Vladimir Oltean 2021-08-02 10:45 ` Prasanna Vengateshan 2021-08-02 12:15 ` Vladimir Oltean 2021-08-02 13:13 ` Andrew Lunn 2021-08-02 13:59 ` Vladimir Oltean 2021-08-02 20:47 ` Andrew Lunn 2021-08-03 16:54 ` Prasanna Vengateshan 2021-08-03 23:54 ` Vladimir Oltean 2021-08-04 9:59 ` Russell King (Oracle) [this message] 2021-08-04 10:46 ` Vladimir Oltean 2021-08-04 14:28 ` Prasanna Vengateshan 2021-08-04 14:51 ` Vladimir Oltean 2021-08-07 15:40 ` Andrew Lunn 2021-08-07 17:00 ` Vladimir Oltean 2021-08-11 17:44 ` Prasanna Vengateshan 2021-08-11 18:23 ` Andrew Lunn 2021-08-11 20:14 ` Russell King (Oracle) 2021-08-11 20:20 ` Vladimir Oltean 2021-08-11 20:22 ` Andrew Lunn 2021-07-23 17:31 ` [PATCH v3 net-next 06/10] net: dsa: microchip: add support for phylink management Prasanna Vengateshan 2021-07-31 15:27 ` Vladimir Oltean 2021-08-03 17:04 ` Prasanna Vengateshan 2021-07-23 17:31 ` [PATCH v3 net-next 07/10] net: dsa: microchip: add support for ethtool port counters Prasanna Vengateshan 2021-07-23 17:31 ` [PATCH v3 net-next 08/10] net: dsa: microchip: add support for port mirror operations Prasanna Vengateshan 2021-07-31 15:24 ` Vladimir Oltean 2021-07-23 17:31 ` [PATCH v3 net-next 09/10] net: dsa: microchip: add support for fdb and mdb management Prasanna Vengateshan 2021-07-31 15:19 ` Vladimir Oltean 2021-07-23 17:31 ` [PATCH v3 net-next 10/10] net: dsa: microchip: add support for vlan operations Prasanna Vengateshan 2021-07-31 15:08 ` Vladimir Oltean 2021-08-02 10:48 ` Prasanna Vengateshan
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=20210804095954.GN22278@shell.armlinux.org.uk \ --email@example.com \ --cc=UNGLinuxDriver@microchip.com \ --cc=Woojung.Huh@microchip.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v3 net-next 05/10] net: dsa: microchip: add DSA support for microchip lan937x' \ /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
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).