From: Vinod Koul <vinod.koul@linaro.org>
To: Angelo Dureghello <angelo@sysam.it>
Cc: Vinod Koul <vinod.koul@intel.com>,
dmaengine@vger.kernel.org, gerg@linux-m68k.org,
linux-m68k@vger.kernel.org, vkoul@kernel.org
Subject: dmaengine: mcf-edma: add ColdFire mcf5441x eDMA support
Date: Mon, 7 May 2018 19:45:35 +0530 [thread overview]
Message-ID: <20180507141535.GD14832@vkoul-mobl> (raw)
On Fri, May 04, 2018 at 09:18:19PM +0200, Angelo Dureghello wrote:
> Hi Vinod,
>
> thanks for the review,
>
> On Thu, May 03, 2018 at 10:18:30PM +0530, Vinod Koul wrote:
> > On Wed, Apr 25, 2018 at 10:08:17PM +0200, Angelo Dureghello wrote:
> > > This patch adds dma support for NXP mcf5441x (ColdFire) family.
> > >
> > > ColdFire mcf5441x implements an edma hw module similar to the
> >
> > Is it similar to to edma ?
> >
>
> It is similar to Freescale "edma" but with a different number of
> channels, a bit different register set, different interrupt
> structure, no channel multiplexer.
ok
> > > one implemented in Vybrid VFxxx controllers, but with a slightly
> > > different register set, more dma channels (64 instead of 32),
> > > a different interrupt mechanism and some other minor differences.
> > >
> > > For the above reasons, modfying fsl-edma.c was too complex and
> > > likely too ugly. From here, the decision to create a different
> > > driver, but starting from fsl-edma.
> >
> > can the common stuff be made into a lib and shared between then two rather
> > than having a same driver or different drivers?
>
> It should be possible to collect some common code in a kind of
> mcf_edma_core.c common module, but in this case i cannot then test
> the Vybrid edma after the changes since i miss that hardware.
Sure you should send the patches and folks who care about fsl driver
would look it up and test
> Would be maybe possible for you to diff fsl-edma and this mcf-edma,
> just to confirm if i can still stay this way, or if moving to a
> library becomes mandatory ?
well since you know the IP you would make a better guess on that, best is
to check register sets in drivers
> > > +// SPDX-License-Identifier: GPL-2.0
> >
> > Copyright info should be here in c99 style comments
> >
>
> Seems checkpatch.pl, for C files, does not like the C style
> initial line comment:
>
> WARNING: Missing or malformed SPDX-License-Identifier tag in line 1
> #87: FILE: drivers/dma/mcf-edma.c:1:
> +/* SPDX-License-Identifier: GPL-2.0 */
>
> While c++ type is accepted.
>
> In contrary, in .h files it wants cpp // style and not C style.
SC99 comments style is
// SPDX-License-Identifier: GPL-2.0
Point is the copyright should be added is same formar i.e.,
// Copyright 20018 - foo bar
this line should follow the spdx line
> > > +
> > > +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> >
> > why do you need this, why not use dev_xxx
> >
>
> Well, pr_ style seems to simplify the call a bit, should be allowed
> but if you prefer i can move all to dev_ format.
in hindsight dev_ makes better sense, been there done that :)
next reply other threads:[~2018-05-07 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 14:15 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-30 20:59 dmaengine: mcf-edma: add ColdFire mcf5441x eDMA support Angelo Dureghello
2018-05-28 4:01 Vinod Koul
2018-05-26 20:50 Angelo Dureghello
2018-05-23 5:37 Vinod Koul
2018-05-22 21:28 Angelo Dureghello
2018-05-04 19:18 Angelo Dureghello
2018-05-03 16:48 Vinod Koul
2018-04-25 20:08 Angelo Dureghello
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=20180507141535.GD14832@vkoul-mobl \
--to=vinod.koul@linaro.org \
--cc=angelo@sysam.it \
--cc=dmaengine@vger.kernel.org \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=vinod.koul@intel.com \
--cc=vkoul@kernel.org \
/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).