Re: [PATCH 0/5] mfd: replace IORESOURCE_IO by IORESOURCE_MEM

From: Arnd Bergmann
Date: Tue Aug 07 2012 - 16:51:31 EST


On Tuesday 07 August 2012, Geert Uytterhoeven wrote:
>Don't you need an extra file in /proc, too (cfr. /proc/ioports and /proc/iomem)?
>
> And as Arnd pointed out, if resources will be used for various new buses,
> "IORESOURCE_FOO" or "IORESOURCE_OTHER" is a bit vague.
> What about conflicts where one driver means i2c addresses and another
> one means gpio addresses? The resource system will reject them?

The platform code currently only inserts the resources of type IO or
MEM. For the new type, we would not insert them to any resource
tree and they consequently are not available in any /proc file.

No driver should ever try to request access to those resources either.
The only thing we do with them is attach them to a platform device
in the mfd driver and take them out of it again in the child driver.

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