netdev - Re: Information on DSA driver initialization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 13 Mar 2020 10:47:22 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Sriram Chadalavada <sriram.chadalavada@...dleap.ca>
Cc:     netdev@...r.kernel.org
Subject: Re: Information on DSA driver initialization

On Thu, Mar 12, 2020 at 06:38:24PM -0400, Sriram Chadalavada wrote:
> Hi Andrew,
>    Thank you for your response.
> 
>   Yes. There are patches applied.  I did scatter printks/pr_info but
> don't see anything yet from the Marvell 6176 switch without
> CONFIG_NET_DSA_LEGACY enabled.

CONFIG_NET_DSA_LEGACY is dead. Don't use it. Use the new binding.

> 
>     One question I have is if CONFIG_NET_DSA_LEGACY is NOT selected,
> what in the 4.19 kernel takes over the function of dsa_probe function
> in net/dsa/legacy.c and mv88e6xxx_drv_probe in
> drivers/net/dsa/mv88e6xxx/chip.c ?

When the mdio bus is registered, the mdio driver calls
of_mdiobus_register() passing a DT node for the bus. The bus is walked
and devices instantiated.

    Andrew