[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<BY5PR02MB6786649AEE8D66E4472BB9679DFC2@BY5PR02MB6786.namprd02.prod.outlook.com>
Date: Fri, 31 May 2024 15:13:15 +0000
From: Piergiorgio Beruto <Pier.Beruto@...emi.com>
To: Andrew Lunn <andrew@...n.ch>,
"Parthiban.Veerasooran@...rochip.com"
<Parthiban.Veerasooran@...rochip.com>
CC: Selvamani Rajagopal <Selvamani.Rajagopal@...emi.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com"
<edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"horms@...nel.org"
<horms@...nel.org>,
"saeedm@...dia.com" <saeedm@...dia.com>,
"anthony.l.nguyen@...el.com" <anthony.l.nguyen@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"corbet@....net" <corbet@....net>,
"linux-doc@...r.kernel.org"
<linux-doc@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org" <krzysztof.kozlowski+dt@...aro.org>,
"conor+dt@...nel.org" <conor+dt@...nel.org>,
"devicetree@...r.kernel.org"
<devicetree@...r.kernel.org>,
"Horatiu.Vultur@...rochip.com"
<Horatiu.Vultur@...rochip.com>,
"ruanjinjie@...wei.com"
<ruanjinjie@...wei.com>,
"Steen.Hegelund@...rochip.com"
<Steen.Hegelund@...rochip.com>,
"vladimir.oltean@....com"
<vladimir.oltean@....com>,
"UNGLinuxDriver@...rochip.com"
<UNGLinuxDriver@...rochip.com>,
"Thorsten.Kummermehr@...rochip.com"
<Thorsten.Kummermehr@...rochip.com>,
"Nicolas.Ferre@...rochip.com"
<Nicolas.Ferre@...rochip.com>,
"benjamin.bigler@...nformulastudent.ch"
<benjamin.bigler@...nformulastudent.ch>,
Viliam Vozar
<Viliam.Vozar@...emi.com>,
Arndt Schuebel <Arndt.Schuebel@...emi.com>
Subject: RE: [PATCH net-next v4 00/12] Add support for OPEN Alliance
10BASE-T1x MACPHY Serial Interface
Hi Andrew,
We're currently working on re-factoring our driver onto the framework.
I will make sure we can give you a feedback ASAP.
We're also trying to asses the performance difference between what we have now and what we can achieve after re-factorng.
Thanks,
Piergiorgio
-----Original Message-----
From: Andrew Lunn <andrew@...n.ch>
Sent: 31 May, 2024 14:37
To: Parthiban.Veerasooran@...rochip.com
Cc: Piergiorgio Beruto <Pier.Beruto@...emi.com>; Selvamani Rajagopal <Selvamani.Rajagopal@...emi.com>; davem@...emloft.net; edumazet@...gle.com; kuba@...nel.org; pabeni@...hat.com; horms@...nel.org; saeedm@...dia.com; anthony.l.nguyen@...el.com; netdev@...r.kernel.org; linux-kernel@...r.kernel.org; corbet@....net; linux-doc@...r.kernel.org; robh+dt@...nel.org; krzysztof.kozlowski+dt@...aro.org; conor+dt@...nel.org; devicetree@...r.kernel.org; Horatiu.Vultur@...rochip.com; ruanjinjie@...wei.com; Steen.Hegelund@...rochip.com; vladimir.oltean@....com; UNGLinuxDriver@...rochip.com; Thorsten.Kummermehr@...rochip.com; Nicolas.Ferre@...rochip.com; benjamin.bigler@...nformulastudent.ch; Viliam Vozar <Viliam.Vozar@...emi.com>; Arndt Schuebel <Arndt.Schuebel@...emi.com>
Subject: Re: [PATCH net-next v4 00/12] Add support for OPEN Alliance 10BASE-T1x MACPHY Serial Interface
[External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links.
> So I would request all of you to give your comments on the existing
> implementation in the patch series to improve better. Once this
> version is mainlined we will discuss further to implement further
> features supported. I feel the current discussion doesn't have any
> impact on the existing implementation which supports basic 10Base-T1S
> Ethernet communication.
Agreed. Lets focus on what we have now.
https://urldefense.com/v3/__https://patchwork.kernel.org/project/netdevbpf/patch/20240418125648.372526-2-Parthiban.Veerasooran@microchip.com/__;!!KkVubWw!n9QOIA72sKA9z72UFogHeBRnA8Hse9gmIqzNv27f7Tc-4dYH1KA__DfMSmln-uBotO-bnw3PC2qXbfRn$
Version 4 failed to apply. So we are missing all the CI tests. We need a v5 which cleanly applies to net-next in order for those tests to run.
I think we should disable vendor interrupts by default, since we currently have no way to handle them.
I had a quick look at the comments on the patches. I don't think we have any other big issues not agreed on. So please post a v5 with them all addressed and we will see what the CI says.
Piergiorgio, if you have any real problems getting basic support for your device working with this framework, now would be a good time to raise the problems.
Andrew
Powered by blists - more mailing lists