[PATCH 1/2] mfd: max8925: request resource region

[broonie@opensource.wolfsonmicro.com (Mark Brown)]

On Wed, May 09, 2012 at 03:03:22PM +0000, Arnd Bergmann wrote:

> I mean that each device providing resources of the new type would need
> to register its resources to the same root resource with non-conclicting

Oh, right - I see what you mean.  I was thinking of creating a
per-chip parent for each tree rather than trying to make them a unified
tree, though I guess it's useful for diagnostics.  Multi-level resources
might be slightly fun with this though I'm not sure how realistic they
are.

> addresses. Having resources hanging in the air without a parent pointer
> is not good, although we seem to be doing that for a lot of platform
> devices these days, where we just pass the struct resource from platform
> code to a driver without ever registering it at each end.

They should all be being registered by the platform core when the
platform device is registered I think?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120509/c99a5363/attachment-0001.sig>