From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@googlegroups.com, kevin.z.m.zh@gmail.com,
sunny@allwinnertech.com, shuge@allwinnertech.com,
zhuzhenhua@allwinnertech.com, Arnd Bergmann <arnd@arndb.de>,
andriy.shevchenko@intel.com, dmaengine@vger.kernel.org
Subject: Re: [PATCH v11 0/2] Add support for the Allwinner A31 DMA Controller
Date: Mon, 28 Jul 2014 12:14:02 +0200 [thread overview]
Message-ID: <20140728101402.GD3952@lukather> (raw)
In-Reply-To: <20140725164218.GW8181@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2147 bytes --]
On Fri, Jul 25, 2014 at 10:12:18PM +0530, Vinod Koul wrote:
> On Fri, Jul 25, 2014 at 06:37:46PM +0200, Maxime Ripard wrote:
> > > Can you please send follow patches for these:
> > > - don't recall if I pointed earlier, but can we use direct conversion for
> > > calculating convert_burst() and convert_buswidth(), latter one at least
> > > seem doable
> >
> > Ok. Do you still want the error reporting for the invalid width and
> > burst size?
> I think for convert_buswidth() we can do away with a switch case and convert
> the numbers directly
Well, it's already using a switch. Do you want me to remove completely
the function and move the switch where it's used? It's used two times
now, so I'd like to avoid duplicating it.
> > > - don't use devm_request_irq(). You have irq enabled and you have killed
> > > tasklet. This is too racy. You need to ensure no irqs can be generated before killing
> > > tasklets.
> >
> > Ok, would calling disable_irq before killing the tasklet an option for
> > you ? that would allow to keep the devm_request_irq.
> disable_irq also does syncronize, so it might work. But then again if the
> probe fails after registering irq due to some other reason, and you get into
> races with unitialized driver as well.
>
> I think it might be easier to amnge by working with plain old request_irq()
Yes, devm_free_irq like Russell suggested seems to both address your
concerns, while not having to care about it at probe.
> > I'll also send patches for the various breakages and warnings spotted
> > by the autobuilders.
> Yes please, I havent seen the reports in detail yet, but they are reporting
> mainly due COMPILE_TEST. DO you really want that?
I don't know, I thought it was the new "default". And it allows to
catch issues like we've seen.
> Yes it did help me to compile for ARM, i didnt see any defconfig which has
> this MACH in arm/configs
I don't know what kernel you were looking at, but it's been introduced
in 3.16.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-28 10:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 19:46 [PATCH v11 0/2] Add support for the Allwinner A31 DMA Controller Maxime Ripard
2014-07-17 19:46 ` [PATCH v11 1/2] Documentation: dt: Add Allwinner A31 DMA controller bindings Maxime Ripard
2014-07-17 19:46 ` [PATCH v11 2/2] dmaengine: sun6i: Add driver for the Allwinner A31 DMA controller Maxime Ripard
2014-07-24 12:13 ` [PATCH v11 0/2] Add support for the Allwinner A31 DMA Controller Maxime Ripard
2014-07-24 23:44 ` Andrew Morton
2014-07-25 6:11 ` Vinod Koul
2014-07-25 6:13 ` Vinod Koul
2014-07-25 7:14 ` Andrew Morton
2014-07-25 13:12 ` Vinod Koul
2014-07-25 16:37 ` Maxime Ripard
2014-07-25 16:42 ` Vinod Koul
2014-07-28 10:14 ` Maxime Ripard [this message]
2014-07-28 14:18 ` Vinod Koul
2014-07-29 16:03 ` Maxime Ripard
2014-07-25 16:45 ` Russell King - ARM Linux
2014-07-28 9:41 ` Maxime Ripard
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=20140728101402.GD3952@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=andriy.shevchenko@intel.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=kevin.z.m.zh@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=shuge@allwinnertech.com \
--cc=sunny@allwinnertech.com \
--cc=vinod.koul@intel.com \
--cc=zhuzhenhua@allwinnertech.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).