Re: [PATCH net-next 08/30] net: dsa: mt7530: change p{5,6}_interface to... | linux-arm-kernel

(off-list ancestor, not in this archive)

On Sat, Jun 03, 2023 at 03:15:52PM +0300, Arınç ÜNAL wrote:
On 26.05.2023 16:01, Vladimir Oltean wrote:
Ok, but given the premise of this patch set, that phylink is always available,
does it make sense for mt7531_cpu_port_config() and mt7988_cpu_port_config()
to manually call phylink methods?
All I know is that that's how the implementation of phylink's PCS support in
this driver works. It expects the MAC to be set up before calling
mt753x_phylink_pcs_link_up() and mt753x_phylink_mac_link_up().
No, but I mean, won't phylink call mt7531_mac_config(), mt753x_phylink_pcs_link_up()
and mt753x_phylink_mac_link_up() automatically and in the expected order already,
and if not, what prevents that from happening? I just don't understand why the
cpu_port_config() methods of MT7531 and MT7988 call phylink methods manually
from the driver.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help

Re: [PATCH net-next 08/30] net: dsa: mt7530: change p{5,6}_interface to p{5,6}_configured

Possibly related (same subject, not in this thread)