Re: [DRIVER MODEL] Allow overlapping resources for platform devices

[Kumar Gala <galak@gate.crashing.org>]

On Mon, 28 Nov 2005, Russell King wrote:

> On Mon, Nov 28, 2005 at 10:15:39AM -0600, Kumar Gala wrote:
> > There are cases in which a device's memory mapped registers overlap
> > with another device's memory mapped registers.  On several PowerPC
> > devices this occurs for the MDIO bus, whose registers tended to overlap
> > with one of the ethernet controllers.
> 
> Hrm, shouldn't the MDIO device be registered by the ethernet driver then?
> The MDIO device is a child of the ethernet device - and this also brings
> up the question about PM ordering - should the MDIO device be suspended
> before or after the ethernet device.

Well the MDIO device actually is conceptually separate from the ethernet 
controller that shares register space with it.  For example, we may have a 
processor with 4 ethernet controllers on it.  We use the register set in 
controller 1 to get to the MDIO "device" for all four controllers.

Hopefully, Andy can provide further details about order issues and how the 
current PHY layer interacts with the ethernet controller.

However, the issue still exists that the MDIO devices registers live 
inside another devices register space.

- kumar

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