netdev - Re: RFC: DSA device/driver model revamp

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] [day] [month] [year] [list]

Message-Id: <20140912.175022.8867946355734452.davem@davemloft.net>
Date:	Fri, 12 Sep 2014 17:50:22 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	f.fainelli@...il.com
Cc:	netdev@...r.kernel.org, jogo@...nwrt.org, nbd@...nwrt.org,
	alexander.duyck@...il.com, jhs@...atatu.com, kernel@...tstofly.org
Subject: Re: RFC: DSA device/driver model revamp

From: Florian Fainelli <f.fainelli@...il.com>
Date: Wed, 10 Sep 2014 15:11:50 -0700

> Proposed solution:

No objections from me.

> Open questions:
> 
> There is some legacy code that will instantiate the special "dsa"
> platform device in arch/arm/mach-orion5x/*, this code needs to be
> transitioned one way or the other.
> 
> The switches used by these Orion5x platforms are MDIO-connected
> switches, with the proposal above, these switch drivers will become PHY
> drivers matching a particular PHY ID on the MDIO bus.
> 
> We currently do not have a way to attach platform specific data that is
> not coming from Device Tree to these PHY devices, something potentially
> not too intrusive could be to extend phy_register_fixup() with a void *
> argument to pass specific platform data, or create
> phy_register_fixup_with_data().

I'd rather you create a new interface which is strongly typed than
anything using void pointers.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html