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
| ||
|
Date: Tue, 26 Apr 2016 21:41:02 +0200 From: Andrew Lunn <andrew@...n.ch> To: Arnd Bergmann <arnd@...db.de> Cc: Florian Fainelli <f.fainelli@...il.com>, Pramod Kumar <pramod.kumar@...adcom.com>, Rob Herring <robh+dt@...nel.org>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <will.deacon@....com>, Masahiro Yamada <yamada.masahiro@...ionext.com>, Chen-Yu Tsai <wens@...e.org>, Mark Rutland <mark.rutland@....com>, devicetree@...r.kernel.org, Pawel Moll <pawel.moll@....com>, Suzuki K Poulose <suzuki.poulose@....com>, netdev@...r.kernel.org, Punit Agrawal <punit.agrawal@....com>, linux-kernel@...r.kernel.org, BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>, linux-arm-kernel@...ts.infradead.org, Anup Patel <anup.patel@...adcom.com>, Kishon Vijay Abraham I <kishon@...com> Subject: Re: [PATCH 1/6] bus: Add shared MDIO bus framework On Tue, Apr 26, 2016 at 09:24:34PM +0200, Arnd Bergmann wrote: > On Tuesday 26 April 2016 20:23:35 Andrew Lunn wrote: > > > A more complex problem would be having a PHY driver for a device > > > that can be either an ethernet phy or some other phy. > > > > I doubt that ever happens. You can have up to 32 different devices on > > an MDIO bus. Since an Ethernet PHY and a "some other sort of PHY" are > > completely different things, why would a hardware engineer place them > > on the same address? It is like saying your ATA controller and VGA > > controller share the same slot on the PCI bus... > > To clarify: what I meant is a device that is designed as a PHY for > similar hardware (e.g. SATA, USB3 and PCIe) and that has a common > register set and a single driver, but that driver can operate > in multiple modes. You typically have multiple instances of > such hardware, with each instance linked to exactly one host > device, but one driver for all of them. > > See Documentation/devicetree/bindings/phy/apm-xgene-phy.txt > and drivers/phy/phy-xgene.c for one such example. Interesting. Also, that this lists SGMII. I assume this is a phy in the MAC in order to talk to the Ethernet PHY. I still don't see it being a big problem if a phy driver implements an Ethernet PHY. It just needs to call phy_device_create() and phy_device_register(). Andrew
Powered by blists - more mailing lists