> -----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? Regards, Wen > > > > config FSL_QDMA > > tristate "NXP Layerscape qDMA engine support" > > + depends on ARM || ARM64 > > select DMA_ENGINE > > select DMA_VIRTUAL_CHANNELS > > select DMA_ENGINE_RAID > > select ASYNC_TX_ENABLE_CHANNEL_SWITCH > > help > > Support the NXP Layerscape qDMA engine with command > queue and legacy mode. > > Channel virtualization is supported through enqueuing of DMA > jobs to, > > or dequeuing DMA jobs from, different work queues. > > This module can be found on NXP Layerscape SoCs. > > > > Best Regards > > Wen He > -- > ~Vinod > -- > To unsubscribe from this list: send the line "unsubscribe dmaengine" in the > body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvger. > kernel.org%2Fmajordomo-info.html&data=02%7C01%7Cwen.he_1%40nxp.co > m%7C9fa4d470c6bd48ae5d0508d55683eb2a%7C686ea1d3bc2b4c6fa92cd99 > c5c301635%7C0%7C0%7C636510046973718477&sdata=RGTwdiOE28%2BIX > uLboWivcKLgG%2BULmsNL9JOMAOMrvRk%3D&reserved=0 ?韬{.n?????%??檩??w?{.n???Ё?撖)?骅w*jg????????G??⒏⒎?:+v????????????"??????