mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
	"Vladimir Oltean" <olteanv@gmail.com>,
	"Luiz Angelo Daros de Luca" <luizluca@gmail.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	mithat.guner@xeront.com, erkin.bozoglu@xeront.com,
	"Alvin Šipraga" <ALSI@bang-olufsen.dk>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: dsa: remove OF-based MDIO bus registration from DSA core
Date: Mon, 29 Jan 2024 08:08:28 -0800	[thread overview]
Message-ID: <120646e5-bd05-48bd-a308-e0e8685633e9@gmail.com> (raw)
In-Reply-To: <816442dc-b420-4413-a29f-c73b95f1026b@arinc9.com>



On 1/29/2024 7:53 AM, Arınç ÜNAL wrote:
> On 29.01.2024 17:56, Vladimir Oltean wrote:
>> On Sat, Jan 27, 2024 at 11:23:33PM -0300, Luiz Angelo Daros de Luca 
>> wrote:
>>>>> IIUC, Luiz made the original patch for the realtek switches. Shouldn't
>>>>> we wait until realtek registers ds->user_mii_bus on its own, before
>>>>> reverting? Otherwise, you're basically saying that Luiz made the DSA
>>>>> core patch without needing it.
>>>>
>>>> My findings point to that. Luiz made the patch to optionally 
>>>> register the
>>>> MDIO bus of the MDIO controlled Realtek switches OF-based. So it's not
>>>> necessary to wait.
>>>
>>> Back in the time when I wrote that code, with the phy_read/write in
>>> dsa_switch_ops, the OF node was only required to associate IRQ to each
>>> port. Until my patch to register its own mdiobus driver lands (I hope
>>> that happens before the next version), the port status will fall back
>>> to polling. I don't think it is a critical feature but I'll let the
>>> maintainers decide. ACK for me.
>>>
>>> Regards,
>>>
>>> Luiz
>>
>> It isn't really great that this loses IRQ support for Realtek internal 
>> PHYs,
>> especially since Arınç's commit message did not estimate this would 
>> happen.
>>
>> I don't see why this patch could not wait until you resubmit the realtek
>> consolidation set and it gets accepted.
> 
> I agree. I didn't anticipate that realtek-mdio didn't set IRQs on PHYs for
> the MDIO bus registered non-OF-based. I'd much rather wait and then send v2
> with the mention to realtek-mdio removed.

Sounds good, thanks!
-- 
Florian

  reply	other threads:[~2024-01-29 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22  5:33 Arınç ÜNAL
2024-01-23 15:44 ` Vladimir Oltean
2024-01-24  5:30   ` Arınç ÜNAL
2024-01-25  9:00     ` Vladimir Oltean
2024-01-28  2:23     ` Luiz Angelo Daros de Luca
2024-01-29 14:56       ` Vladimir Oltean
2024-01-29 15:53         ` Arınç ÜNAL
2024-01-29 16:08           ` Florian Fainelli [this message]
2024-02-12 20:48             ` Luiz Angelo Daros de Luca

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=120646e5-bd05-48bd-a308-e0e8685633e9@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=ALSI@bang-olufsen.dk \
    --cc=andrew@lunn.ch \
    --cc=arinc.unal@arinc9.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=erkin.bozoglu@xeront.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luizluca@gmail.com \
    --cc=mithat.guner@xeront.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    /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

all inboxes | Powered by JetHome®