[PATCH] [v2] netdev/phy: add MDIO bus multiplexer driven by a memory-mapped device

David Miller davem at davemloft.net
Sat Aug 25 05:07:40 EST 2012


From: Stephen Warren <swarren at wwwdotorg.org>
Date: Fri, 24 Aug 2012 12:56:05 -0600

> In the I2C case, the address spaces are disjoint, so there's never any
> mapping between them, so there's no need for ranges.
> 
> Any time the child address space is intended to be part of the parent's
> address space, I believe ranges is supposed to be specified, perhaps
> even mandatory, even if the translation is 1:1.

Regardless, you really can't just generically translate ranges
in some universal way and expect it to work in all cases.

You need bus specific drivers to deal with various special
cases.

See the *_map() methods implemented in:

	arch/sparc/kernel/of_device_64.c

for example.


More information about the devicetree-discuss mailing list