> -----Original Message----- > From: Parthiban.Veerasooran@xxxxxxxxxxxxx > <Parthiban.Veerasooran@xxxxxxxxxxxxx> > Sent: Dienstag, 19. September 2023 11:04 > To: Hennerich, Michael <Michael.Hennerich@xxxxxxxxxx>; Regus, Ciprian > <Ciprian.Regus@xxxxxxxxxx>; andrew@xxxxxxx; jtm@xxxxxxxxxxxxx > Cc: davem@xxxxxxxxxxxxx; edumazet@xxxxxxxxxx; kuba@xxxxxxxxxx; > pabeni@xxxxxxxxxx; robh+dt@xxxxxxxxxx; > krzysztof.kozlowski+dt@xxxxxxxxxx; conor+dt@xxxxxxxxxx; corbet@xxxxxxx; > Steen.Hegelund@xxxxxxxxxxxxx; rdunlap@xxxxxxxxxxxxx; > horms@xxxxxxxxxx; casper.casan@xxxxxxxxx; netdev@xxxxxxxxxxxxxxx; > devicetree@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux- > doc@xxxxxxxxxxxxxxx; Horatiu.Vultur@xxxxxxxxxxxxx; > Woojung.Huh@xxxxxxxxxxxxx; Nicolas.Ferre@xxxxxxxxxxxxx; > UNGLinuxDriver@xxxxxxxxxxxxx; Thorsten.Kummermehr@xxxxxxxxxxxxx; > ada@xxxxxxxxxxx > Subject: Fwd: [RFC PATCH net-next 0/6] Add support for OPEN Alliance > 10BASE-T1x MACPHY Serial Interface > > > Hi, > > @Andrew: As you pointed out in another email, I have included Jay > Monkman as well in this email to discuss further. > > @Jay Monkman: Yesterday, Andrew noticed that you submitted a patch > series for NCN26010 which is a 10BASE-T1S MACPHY which uses OPEN > Alliance spec. > > @Michael Hennerich: I am forwarding this email to you so that you will get > the history behind this conversation. Please have a look in the below email > for the clarification we need. > > Microchip's product link is below, > > https://urldefense.com/v3/__https://www.microchip.com/en- > us/product/lan8650__;!!A3Ni8CS0y2Y!5NnVuSzLYTgWJs0VW1cJjMAU2tR1j6 > ucjHFmGLl52wzcuOYJoxo3Itq5kSPqVg90KxBFbe_wLoTJeEofKEWagrJ46WjzIF > 7hQuY$ > > We already pushed the driver patches for supporting the above Microchip's > LAN865x MACPHY and the OPEN Alliance spec to the mainline and it is under > review. Please refer the below link to get a complete picture of this patch > series. > > https://urldefense.com/v3/__https://lore.kernel.org/netdev/202309131526 > 25.73e32789@wsk/T/__;!!A3Ni8CS0y2Y!5NnVuSzLYTgWJs0VW1cJjMAU2tR1 > j6ucjHFmGLl52wzcuOYJoxo3Itq5kSPqVg90KxBFbe_wLoTJeEofKEWagrJ46Wjz > AjlY1vs$ > > We have developed 10BASE-T1x MAC_PHY Serial Interface Specification > defined by OPEN Alliance TC6 group as a separate framework/generic lib and > included in this patch series so that all the 10BASE-T1x MACPHY vendors can > make use of it. > > As Andrew suggested, it would be nice if we all work together to make it > better. Please feel free to share your comments/ideas to improve the > framework. There was some side conversation off-list to this topic as well - our developer Alexandru who mainlined the ADIN1110 driver also worked on the TC6-10BASE-T1x MACPHY version. Since this came after he finished the standard SPI version, the non OA version was mainlined first. He aimed to send his implementation to the mailing list almost a year ago, but wanted to polish it a bit more. And how this always happens he got sidetracked by some other project and then unfortunately left. Our Open Alliance implementation was tested and also this wiki landing page was created: https://wiki.analog.com/resources/tools-software/linux-drivers/net-mac-phy/open_alliance The patches and files can be found on the tip of this branch here: https://github.com/analogdevicesinc/linux/commits/adin1110-open-alliance So this might be an alternative implementation. I'm sure we'll settle a common one. Ciprian will take over responsibilities from Alexandru. Best regards, Michael > > From my next reply on-wards I will include Michael.Hennerich, Ciprian Regus > and Jay Monkman in the "--to" or "--cc" so that we can share our ideas and > comments. > > I have brought everyone in this email so that we all in sync discussing the > same topic and sharing our ideas. Please stick with this email or other patch > series email for further communications to share all our ideas. > > I hope this helps. Please let me know if you have any query on this. > > Best Regards, > Parthiban V > > -------- Forwarded Message -------- > Subject: Fwd: [RFC PATCH net-next 0/6] Add support for OPEN Alliance > 10BASE-T1x MACPHY Serial Interface > Date: Mon, 18 Sep 2023 14:32:24 +0530 > From: Parthiban Veerasooran <Parthiban.Veerasooran@xxxxxxxxxxxxx> > To: Lennart Franzen <lennart@xxxxxxxxxxxx>, Alexander Dahl > <ada@xxxxxxxxxxx>, Andrew Lunn <andrew@xxxxxxx> > CC: davem@xxxxxxxxxxxxx, edumazet@xxxxxxxxxx, kuba@xxxxxxxxxx, > pabeni@xxxxxxxxxx, robh+dt@xxxxxxxxxx, > krzysztof.kozlowski+dt@xxxxxxxxxx, conor+dt@xxxxxxxxxx, corbet@xxxxxxx, > steen.hegelund@xxxxxxxxxxxxx, rdunlap@xxxxxxxxxxxxx, > horms@xxxxxxxxxx, casper.casan@xxxxxxxxx, netdev@xxxxxxxxxxxxxxx, > devicetree@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux- > doc@xxxxxxxxxxxxxxx, horatiu.vultur@xxxxxxxxxxxxx, > Woojung.Huh@xxxxxxxxxxxxx, Nicolas.Ferre@xxxxxxxxxxxxx, > UNGLinuxDriver@xxxxxxxxxxxxx, Thorsten.Kummermehr@xxxxxxxxxxxxx > > Hi Lennart, > > I am forwarding this email to you as we are not able to reach the module > author Alexandru Tachici <alexandru.tachici@xxxxxxxxxx> and getting the > below email delivery error. > > ----cut here----- > Delivery has failed to these recipients or groups: > > alexandru.tachici@xxxxxxxxxx<mailto:alexandru.tachici@xxxxxxxxxx> > The email address you entered couldn't be found. Please check the > recipient's email address and try to resend the message. If the problem > continues, please contact your email admin. > ----cut here------ > > We got your your email address from the commit > bc93e19d088bb14e116756ab270deea6ee62d782. Regarding the below > topic, are you the right contact parson to continue further on this topic or > else do you have any other contact to approach? Please let us know. > > Best Regards, > Parthiban V > -------- Forwarded Message -------- > Subject: Re: [RFC PATCH net-next 0/6] Add support for OPEN Alliance > 10BASE-T1x MACPHY Serial Interface > Date: Mon, 18 Sep 2023 11:42:33 +0530 > From: Parthiban Veerasooran <Parthiban.Veerasooran@xxxxxxxxxxxxx> > To: ada@xxxxxxxxxxx, Alexandru Tachici <alexandru.tachici@xxxxxxxxxx>, > Andrew Lunn <andrew@xxxxxxx> > CC: davem@xxxxxxxxxxxxx, edumazet@xxxxxxxxxx, kuba@xxxxxxxxxx, > pabeni@xxxxxxxxxx, robh+dt@xxxxxxxxxx, > krzysztof.kozlowski+dt@xxxxxxxxxx, conor+dt@xxxxxxxxxx, corbet@xxxxxxx, > steen.hegelund@xxxxxxxxxxxxx, rdunlap@xxxxxxxxxxxxx, > horms@xxxxxxxxxx, casper.casan@xxxxxxxxx, netdev@xxxxxxxxxxxxxxx, > devicetree@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux- > doc@xxxxxxxxxxxxxxx, horatiu.vultur@xxxxxxxxxxxxx, > Woojung.Huh@xxxxxxxxxxxxx, Nicolas.Ferre@xxxxxxxxxxxxx, > UNGLinuxDriver@xxxxxxxxxxxxx, Thorsten.Kummermehr@xxxxxxxxxxxxx > > Hi Alexander, > > Thanks for the information. Please see my reply below. > > On 15/09/23 7:26 pm, Alexander Dahl wrote: > > [Some people who received this message don't often get email from > > ada@xxxxxxxxxxx. Learn why this is important at > > https://urldefense.com/v3/__https://aka.ms/LearnAboutSenderIdentificat > > > ion__;!!A3Ni8CS0y2Y!5NnVuSzLYTgWJs0VW1cJjMAU2tR1j6ucjHFmGLl52wzc > uOYJox > > o3Itq5kSPqVg90KxBFbe_wLoTJeEofKEWagrJ46WjzdmvJN08$ ] > > > > EXTERNAL EMAIL: Do not click links or open attachments unless you know > > the content is safe > > > > Hello, > > > > this is interesting, by chance I just looked at a chip claiming > > similar features today, which already has a driver in kernel: Analog > > Devices ADIN1110. > Microchip's LAN865x is a 10BASE-T1S MACPHY and Analog Devices's > ADIN1110 is a 10BASE-T1L MACPHY. So as you said 10BASE-T1x MAC_PHY > Serial Interface Specification defined by OPEN Alliance TC6 group can be > applicable for both of the devices. I also noticed that ADI's datasheet says > ADIN1110 supports OPEN Alliance 10BASE-T1x MAC-PHY serial interface. > https://www.analog.com/media/en/technical-documentation/data- > sheets/adin1110.pdf > > But in my first glance in their driver code, I don't see any code block which > implements 10BASE-T1x MAC_PHY Serial Interface Specification defined by > OPEN Alliance TC6 group. Or do I miss anything here?. My code reference is > below FYR, > https://urldefense.com/v3/__https://elixir.bootlin.com/linux/v6.6- > rc2/source/drivers/net/ethernet/adi/adin1110.c__;!!A3Ni8CS0y2Y!5NnVuSzL > YTgWJs0VW1cJjMAU2tR1j6ucjHFmGLl52wzcuOYJoxo3Itq5kSPqVg90KxBFbe_ > wLoTJeEofKEWagrJ46Wjz-SM4EnA$ > > OPEN Alliance 10BASE-T1x MAC_PHY Serial Interface Specification cab be > downloaded from the below link, > https://urldefense.com/v3/__https://opensig.org/automotive-ethernet- > specifications/__;!!A3Ni8CS0y2Y!5NnVuSzLYTgWJs0VW1cJjMAU2tR1j6ucjHF > mGLl52wzcuOYJoxo3Itq5kSPqVg90KxBFbe_wLoTJeEofKEWagrJ46Wjz3BeXFz > c$ > > I think Alexandru Tachici from ADI would be able to give us more information > on this direction. > > > > Am Fri, Sep 08, 2023 at 07:59:13PM +0530 schrieb Parthiban Veerasooran: > >> This patch series contain the below updates, > >> - Adds support for OPEN Alliance 10BASE-T1x MACPHY Serial Interface in > the > >> net/ethernet/oa_tc6.c. > > > > So this implements the "10BASE-T1x MAC-PHY Serial Interface > > Specification" which is Ethernet over SPI if I understand correctly? > > The above mentioned chip claims do use the same interface and the same > > standard. How does its driver work then? Do you add code for a thing > > already present in the kernel or does the other driver do something > > completely different and I just misunderstood? > As I mentioned above, in my first glance in their driver code, I don't see any > code block which implements 10BASE-T1x MAC_PHY Serial Interface > Specification defined by OPEN Alliance TC6 group. Let's Alexandru Tachici > from ADI gives us more info on this. > > > > Can the drivers for ADIN1110 and for LAN865X share code because they > > use the same specified interface? The patch set does not look like > > it? > Of course, if their device supports OPEN Alliance then we can use this > oa_tc6.c framework to support other 10BASE-T1x MACPHY's as well. > > > > (Added the other driver author to Cc.) > Ok thanks. > > Best Regards, > Parthiban V > > > > Greets > > Alex > > > >> - Adds driver support for Microchip LAN8650/1 Rev.B0 10BASE-T1S > MACPHY > >> Ethernet driver in the net/ethernet/microchip/lan865x.c. > >> > >> Parthiban Veerasooran (6): > >> net: ethernet: implement OPEN Alliance control transaction interface > >> net: ethernet: add mac-phy interrupt support with reset complete > >> handling > >> net: ethernet: implement OA TC6 configuration function > >> net: ethernet: implement data transaction interface > >> microchip: lan865x: add driver support for Microchip's LAN865X > MACPHY > >> microchip: lan865x: add device-tree support for Microchip's LAN865X > >> MACPHY > >> > >> .../bindings/net/microchip,lan865x.yaml | 54 ++ > >> Documentation/networking/oa-tc6-framework.rst | 231 +++++ > >> MAINTAINERS | 15 + > >> drivers/net/ethernet/microchip/Kconfig | 10 + > >> drivers/net/ethernet/microchip/Makefile | 3 + > >> drivers/net/ethernet/microchip/lan865x.c | 589 +++++++++++++ > >> drivers/net/ethernet/oa_tc6.c | 807 ++++++++++++++++++ > >> include/linux/oa_tc6.h | 130 +++ > >> 8 files changed, 1839 insertions(+) > >> create mode 100644 > Documentation/devicetree/bindings/net/microchip,lan865x.yaml > >> create mode 100644 Documentation/networking/oa-tc6-framework.rst > >> create mode 100644 drivers/net/ethernet/microchip/lan865x.c > >> create mode 100644 drivers/net/ethernet/oa_tc6.c > >> create mode 100644 include/linux/oa_tc6.h > >> > >> -- > >> 2.34.1 > >> > >>
