| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAN1soZzytOwxnS8oNMhFs1rfwVPwFnZoVsXeaMUc4Kf_TnunkA@mail.gmail.com> Date: Mon, 6 Aug 2012 23:56:47 +0800 From: Haojian Zhuang <haojian.zhuang@...il.com> To: Mark Brown <broonie@...nsource.wolfsonmicro.com> Cc: sameo@...ux.intel.com, rpurdie@...ys.net, bryan.wu@...onical.com, linux-kernel@...r.kernel.org, Bergmann Arnd <arnd@...db.de>, Russell King <rmk@....linux.org.uk> Subject: Re: [PATCH 0/5] mfd: replace IORESOURCE_IO by IORESOURCE_MEM On Mon, Aug 6, 2012 at 11:46 PM, Mark Brown <broonie@...nsource.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 majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists