On Tue, Jan 09, 2018 at 03:30:43AM +0000, Wen He wrote: > > > > -----Original Message----- > > From: dmaengine-owner@xxxxxxxxxxxxxxx > > [mailto:dmaengine-owner@xxxxxxxxxxxxxxx] On Behalf Of Vinod Koul > > Sent: 2018年1月8日 18:42 > > To: Wen He <wen.he_1@xxxxxxx> > > Cc: kbuild test robot <lkp@xxxxxxxxx>; kbuild-all@xxxxxx; Leo Li > > <leoyang.li@xxxxxxx>; dmaengine@xxxxxxxxxxxxxxx; Jiafei Pan > > <jiafei.pan@xxxxxxx>; Jiaheng Fan <jiaheng.fan@xxxxxxx> > > Subject: Re: [V2] dmaengine: fsl-qdma: add NXP Layerscape qDMA engine > > driver support > > > > On Thu, Jan 04, 2018 at 07:36:09AM +0000, Wen He wrote: > > > Hi Vinod, > > > > Hi, > > > > Please wrap you replies to 80 chars, I have reflow below.. > > okay > > > > > > > I don't know what's them compile? Does means 'the driver has public > > > driver, so any arch will compile it'? > > > > Today it does compile on all archs > > > > > > > > If so, the compile qdma module need enable config options > > > 'CONFIG_FSl_QDMA' and other architecture should be hide the options. > > > The driver supported arm or arm64 arch, If I change Kconfig to solve > > > compile issues, Can I do that? > > > > yes but as a last resort, it would still help if driver has no dependency on arch > > and is able to compile on others.. > > > > Hi, > > I want to do the same, but I can only verify in x86/x86_64, arm/arm64 and powerpc. > > For now, the issues is ioread32/64 ioread32/64be and iowrite32/64 iowrite32/64be depends on arch defined. > most arch defined it, but other not defined(such as x86,s390..). > > do you have any good ideas? ah okay that sounds okay then, I think putting "depends on ARM || ARM64" sounds fair to me -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
