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: <54B9B66C.70308@broadcom.com>
Date:	Fri, 16 Jan 2015 17:10:04 -0800
From:	Ray Jui <rjui@...adcom.com>
To:	Kishon Vijay Abraham I <kishon@...com>,
	<linux-kernel@...r.kernel.org>,
	Florian Fainelli <f.fainelli@...il.com>
Subject: How to handle access to multiple PHYs through MDIO

Hi,

Our SoC, Cygnus, uses a generic MDC/MDIO controller to talk to various
PHYs, including 2 x Ethernet GPHY, 2 x PCIe Serdes, and 3 x USB PHYs. In
this case, how should I work out a generic PHY driver to handle this?

I notice that most generic PHY drivers are in drivers/phy/*, but
Ethernet seems to have its own interface of talking to a PHY through
MDIO (drivers/net/phy/*).

I need a single driver to handle these so there isn't any race condition
for this single MDIO access in our system.

Thanks,

Ray
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ