From: Vinod Koul <vinod.koul@intel.com>
To: Wen He <wen.he_1@nxp.com>
Cc: kbuild test robot <lkp@intel.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
Leo Li <leoyang.li@nxp.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
Jiafei Pan <jiafei.pan@nxp.com>,
Jiaheng Fan <jiaheng.fan@nxp.com>
Subject: [V2] dmaengine: fsl-qdma: add NXP Layerscape qDMA engine driver support
Date: Thu, 11 Jan 2018 11:55:19 +0530 [thread overview]
Message-ID: <20180111062519.GI18649@localhost> (raw)
On Tue, Jan 09, 2018 at 03:30:43AM +0000, Wen He wrote:
>
>
> > -----Original Message-----
> > From: dmaengine-owner@vger.kernel.org
> > [mailto:dmaengine-owner@vger.kernel.org] On Behalf Of Vinod Koul
> > Sent: 2018年1月8日 18:42
> > To: Wen He <wen.he_1@nxp.com>
> > Cc: kbuild test robot <lkp@intel.com>; kbuild-all@01.org; Leo Li
> > <leoyang.li@nxp.com>; dmaengine@vger.kernel.org; Jiafei Pan
> > <jiafei.pan@nxp.com>; Jiaheng Fan <jiaheng.fan@nxp.com>
> > 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
next reply other threads:[~2018-01-11 6:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 6:25 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-11 9:17 [V2] dmaengine: fsl-qdma: add NXP Layerscape qDMA engine driver support Wen He
2018-01-09 3:30 Wen He
2018-01-08 10:42 Vinod Koul
2018-01-04 7:36 Wen He
2018-01-03 3:52 Vinod Koul
2017-12-27 2:27 Wen He
2017-12-27 1:34 kbuild test robot
2017-12-26 5:15 Wen He
2017-12-25 17:39 kbuild test robot
2017-12-25 7:39 Wen He
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180111062519.GI18649@localhost \
--to=vinod.koul@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=jiafei.pan@nxp.com \
--cc=jiaheng.fan@nxp.com \
--cc=kbuild-all@01.org \
--cc=leoyang.li@nxp.com \
--cc=lkp@intel.com \
--cc=wen.he_1@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).