netdev - Fixed PHY Device Tree usage?

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

Message-ID: <20130709183312.6c4d052d@skate>
Date:	Tue, 9 Jul 2013 18:33:12 +0200
From:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
To:	netdev@...r.kernel.org
Cc:	Florian Fainelli <florian@...nwrt.org>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Gregory Clément 
	<gregory.clement@...e-electrons.com>,
	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
	Lior Amsalem <alior@...vell.com>
Subject: Fixed PHY Device Tree usage?

Hello,

We have a case of an hardware platform that uses the mvneta network
driver, but instead of the SoC being connected to a PHY, it's connected
directly to a switch, so my understanding is that there's no MDIO bus,
and we should have a kind of a "fake PHY" to make the mvneta driver
believe that the link is up, at a given speed.

Looking at this problem, I stumbled across the "fixed PHY" driver in
drivers/net/phy/fixed.c, which registers a fake "Fixed MDIO bus", and
then provides a fixed_phy_add() API to add one "fake" PHY. This seems
to fit my need, except that my ARM platform is obviously Device Tree
based, so I'm wondering what I should do. One option is to implement a
Device Tree binding for the fixed PHY driver (the exact DT binding
would have to be discussed), but I'm wondering whether describing a
fixed PHY in the DT is actually correct, because describing a fixed PHy
is not really describing the hardware, the hardware is actually a
switch.

Do you have some thoughts about this situation? Maybe there's already
some solutions that I'm not aware of?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
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