Skip to contentSkip to conversation

dmaengine: fsl-qdma: add NXP Layerscape qDMA engine driver support

PATCH Superseded Vinod Koul 1 participant 1 message Jan 11, 2018 dmaengine

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore

Vinod Koul

author
#0 lore raw

PATCH v2 1/1 dmaengine: fsl-qdma: add NXP Layerscape qDMA engine driver support

Quoted 38 lines · Wen He
Quoted 13 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Vinod Koul
Sent: 2018年1月8日 18:42
To: Wen He <[email protected]>
Cc: kbuild test robot <[email protected]>; [email protected]; Leo Li <[email protected]>; [email protected]; Jiafei Pan <[email protected]>; Jiaheng Fan <[email protected]>
Subject: Re: [V2] dmaengine: fsl-qdma: add NXP Layerscape qDMA engine driver support

Quoted 6 lines
Quoted 1 line · Wen He

Hi Vinod,

Hi,

Please wrap you replies to 80 chars, I have reflow below..

okay

Quoted 7 lines
Quoted 3 lines

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

Quoted 1 line
Quoted 8 lines
Quoted 4 lines

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..

Quoted 8 lines

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