[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49c4ced9-0429-4730-b0d2-1f679415a53c@microchip.com>
Date: Mon, 3 Jun 2024 06:55:25 +0000
From: <Parthiban.Veerasooran@...rochip.com>
To: <andrew@...n.ch>
CC: <Pier.Beruto@...emi.com>, <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@...emi.com>,
<Arndt.Schuebel@...emi.com>
Subject: Re: [PATCH net-next v4 00/12] Add support for OPEN Alliance
10BASE-T1x MACPHY Serial Interface
Hi Andrew,
On 31/05/24 6:07 pm, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
>> 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.
Great. Thanks for your opinion on this.
>
> https://patchwork.kernel.org/project/netdevbpf/patch/20240418125648.372526-2-Parthiban.Veerasooran@microchip.com/
>
> 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.
Sure I will start preparing the v5 now.
>
> I think we should disable vendor interrupts by default, since we
> currently have no way to handle them.
OK, I will remove the patch which enables the interrupts.
>
> 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.
Sure, thanks for the confirmation.
Best regards,
Parthiban V
>
> 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