[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160426182335.GE30107@lunn.ch>
Date: Tue, 26 Apr 2016 20:23:35 +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
> 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...
Andrew
Powered by blists - more mailing lists