On Mon, Aug 6, 2012 at 11:46 PM, Mark Brown <broo...@opensource.wolfsonmicro.com> wrote: > On Mon, Aug 06, 2012 at 10:42:12PM +0800, Haojian Zhuang wrote: >> On Mon, Aug 6, 2012 at 10:30 PM, Mark Brown > >> > This isn't much more appropriate - _MEM is for memory ranges so isn't >> > directly relevant to register addresses either. If anything _IO is >> > slightly nearer. > >> I use register resource to distinguish different components now. For >> example, component driver >> needs to access the registers in PMIC. These registers offsets are set >> in 88pm860x-core.c. > > I understand this. > >> So I think that it may not be called _IO. > > Right, but _MEM isn't terribly relevant either. If anything _IO is a > bit better as ioports are *somewhat* similar to registers.
The problem is that each bit is already used in 32-bit IORESOURCE. I can't find a empty bit to define the new IORESOURCE. Regards Haojian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
