From: <Parthiban.Veerasooran@microchip.com>
To: <Michael.Hennerich@analog.com>, <Ciprian.Regus@analog.com>,
<andrew@lunn.ch>, <jtm@lopingdog.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<corbet@lwn.net>, <Steen.Hegelund@microchip.com>,
<rdunlap@infradead.org>, <horms@kernel.org>,
<casper.casan@gmail.com>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <Horatiu.Vultur@microchip.com>,
<Woojung.Huh@microchip.com>, <Nicolas.Ferre@microchip.com>,
<UNGLinuxDriver@microchip.com>,
<Thorsten.Kummermehr@microchip.com>, <ada@thorsis.com>
Subject: Fwd: [RFC PATCH net-next 0/6] Add support for OPEN Alliance 10BASE-T1x MACPHY Serial Interface
Date: Tue, 19 Sep 2023 09:03:51 +0000 [thread overview]
Message-ID: <41b6eb40-117c-cdcf-b986-b6f6cf3f21ca@microchip.com> (raw)
In-Reply-To: <f6858856-53c4-5eb8-ab52-350aab280735@microchip.com>
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://www.microchip.com/en-us/product/lan8650
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://lore.kernel.org/netdev/20230913152625.73e32789@wsk/T/
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.
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@microchip.com>
To: Lennart Franzen <lennart@lfdomain.com>, Alexander Dahl
<ada@thorsis.com>, Andrew Lunn <andrew@lunn.ch>
CC: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, corbet@lwn.net,
steen.hegelund@microchip.com, rdunlap@infradead.org, horms@kernel.org,
casper.casan@gmail.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, horatiu.vultur@microchip.com,
Woojung.Huh@microchip.com, Nicolas.Ferre@microchip.com,
UNGLinuxDriver@microchip.com, Thorsten.Kummermehr@microchip.com
Hi Lennart,
I am forwarding this email to you as we are not able to reach the module
author Alexandru Tachici <alexandru.tachici@analog.com> and getting the
below email delivery error.
----cut here-----
Delivery has failed to these recipients or groups:
alexandru.tachici@analog.com<mailto:alexandru.tachici@analog.com>
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@microchip.com>
To: ada@thorsis.com, Alexandru Tachici <alexandru.tachici@analog.com>,
Andrew Lunn <andrew@lunn.ch>
CC: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, corbet@lwn.net,
steen.hegelund@microchip.com, rdunlap@infradead.org, horms@kernel.org,
casper.casan@gmail.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, horatiu.vultur@microchip.com,
Woojung.Huh@microchip.com, Nicolas.Ferre@microchip.com,
UNGLinuxDriver@microchip.com, Thorsten.Kummermehr@microchip.com
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@thorsis.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> 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://elixir.bootlin.com/linux/v6.6-rc2/source/drivers/net/ethernet/adi/adin1110.c
OPEN Alliance 10BASE-T1x MAC_PHY Serial Interface Specification cab be
downloaded from the below link,
https://opensig.org/automotive-ethernet-specifications/
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
>>
>>
next prev parent reply other threads:[~2023-09-19 9:04 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:29 [RFC PATCH net-next 0/6] Add support for OPEN Alliance 10BASE-T1x MACPHY Serial Interface Parthiban Veerasooran
2023-09-08 14:29 ` [RFC PATCH net-next 1/6] net: ethernet: implement OPEN Alliance control transaction interface Parthiban Veerasooran
2023-09-09 13:33 ` Andrew Lunn
2023-09-12 13:03 ` Parthiban.Veerasooran
2023-09-13 1:32 ` Andrew Lunn
2023-09-21 12:27 ` Parthiban.Veerasooran
2023-09-21 19:16 ` Andrew Lunn
2023-09-22 4:31 ` Parthiban.Veerasooran
2023-09-13 1:36 ` Andrew Lunn
2023-09-19 11:40 ` Parthiban.Veerasooran
2023-09-13 2:11 ` Andrew Lunn
2023-09-19 11:38 ` Parthiban.Veerasooran
2023-09-19 15:13 ` Andrew Lunn
2023-09-20 12:40 ` Parthiban.Veerasooran
2023-09-20 13:37 ` Andrew Lunn
2023-09-21 9:15 ` Parthiban.Veerasooran
2023-09-13 2:16 ` Andrew Lunn
2023-09-19 11:13 ` Parthiban.Veerasooran
2023-09-19 12:58 ` Andrew Lunn
2023-09-21 12:36 ` Parthiban.Veerasooran
2023-09-21 19:19 ` Andrew Lunn
2023-09-22 4:39 ` Parthiban.Veerasooran
2023-09-26 12:54 ` Fwd: " Parthiban.Veerasooran
2023-09-08 14:29 ` [RFC PATCH net-next 2/6] net: ethernet: add mac-phy interrupt support with reset complete handling Parthiban Veerasooran
2023-09-09 13:39 ` Andrew Lunn
2023-09-12 12:44 ` Parthiban.Veerasooran
2023-09-13 2:19 ` Andrew Lunn
2023-09-19 11:04 ` Parthiban.Veerasooran
2023-09-11 12:51 ` Ziyang Xuan (William)
2023-09-12 12:10 ` Andrew Lunn
2023-09-12 12:28 ` Parthiban.Veerasooran
2023-09-13 2:39 ` Andrew Lunn
2023-09-19 13:07 ` Parthiban.Veerasooran
2023-09-19 13:21 ` Lukasz Majewski
2023-09-13 8:44 ` Lukasz Majewski
2023-09-13 12:36 ` Andrew Lunn
2023-09-13 13:26 ` Lukasz Majewski
2023-09-19 13:40 ` Parthiban.Veerasooran
2023-09-19 13:51 ` Lukasz Majewski
2023-09-08 14:29 ` [RFC PATCH net-next 3/6] net: ethernet: implement OA TC6 configuration function Parthiban Veerasooran
2023-09-14 0:46 ` Andrew Lunn
2023-09-19 10:57 ` Parthiban.Veerasooran
2023-09-19 12:54 ` Andrew Lunn
2023-09-20 12:42 ` Parthiban.Veerasooran
2023-09-08 14:29 ` [RFC PATCH net-next 4/6] net: ethernet: implement data transaction interface Parthiban Veerasooran
2023-09-10 17:58 ` Simon Horman
2023-09-12 13:47 ` Parthiban.Veerasooran
2023-09-11 12:59 ` Ziyang Xuan (William)
2023-09-12 10:32 ` Parthiban.Veerasooran
2023-09-14 1:18 ` Andrew Lunn
2023-09-18 10:02 ` Parthiban.Veerasooran
2023-09-18 13:01 ` Andrew Lunn
2023-09-19 10:12 ` Parthiban.Veerasooran
2023-09-08 14:29 ` [RFC PATCH net-next 5/6] microchip: lan865x: add driver support for Microchip's LAN865X MACPHY Parthiban Veerasooran
2023-09-10 17:44 ` Simon Horman
2023-09-12 10:53 ` Parthiban.Veerasooran
2023-09-11 13:17 ` Ziyang Xuan (William)
2023-09-12 11:41 ` Parthiban.Veerasooran
2023-09-14 1:51 ` Andrew Lunn
2023-09-19 9:18 ` Parthiban.Veerasooran
2023-09-19 12:50 ` Andrew Lunn
2023-09-20 12:53 ` Parthiban.Veerasooran
2023-09-14 1:55 ` Andrew Lunn
2023-09-18 11:23 ` Parthiban.Veerasooran
2023-09-15 13:01 ` David Wretman
2023-09-18 11:22 ` Parthiban.Veerasooran
2023-09-08 14:29 ` [RFC PATCH net-next 6/6] microchip: lan865x: add device-tree " Parthiban Veerasooran
2023-09-10 10:55 ` Krzysztof Kozlowski
2023-09-12 12:15 ` Parthiban.Veerasooran
2023-09-12 13:17 ` Krzysztof Kozlowski
2023-09-19 10:51 ` Parthiban.Veerasooran
2023-09-14 2:07 ` Andrew Lunn
2023-09-19 10:40 ` Parthiban.Veerasooran
2023-09-10 10:55 ` [RFC PATCH net-next 0/6] Add support for OPEN Alliance 10BASE-T1x MACPHY Serial Interface Krzysztof Kozlowski
[not found] ` <fab8908e-ce74-eff0-8e67-6259b3ad5e1e@microchip.com>
2023-09-13 15:45 ` Krzysztof Kozlowski
2023-09-18 9:23 ` Parthiban.Veerasooran
2023-09-15 13:56 ` Alexander Dahl
2023-09-15 14:22 ` Andrew Lunn
2023-09-18 6:16 ` Parthiban.Veerasooran
2023-09-18 6:12 ` Parthiban.Veerasooran
2023-09-18 9:02 ` Fwd: " Parthiban.Veerasooran
2023-09-19 9:03 ` Parthiban.Veerasooran [this message]
2023-09-19 16:23 ` Jay Monkman
2023-09-19 18:09 ` Hennerich, Michael
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=41b6eb40-117c-cdcf-b986-b6f6cf3f21ca@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=Ciprian.Regus@analog.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Michael.Hennerich@analog.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Steen.Hegelund@microchip.com \
--cc=Thorsten.Kummermehr@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=ada@thorsis.com \
--cc=andrew@lunn.ch \
--cc=casper.casan@gmail.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jtm@lopingdog.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--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).