From: Felipe Balbi <balbi@ti.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2 v3] usb: fix renesas_usbhs to not schedule in atomic context
Date: Tue, 14 Feb 2012 11:46:03 +0000 [thread overview]
Message-ID: <20120214114602.GE24201@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1202141134580.443@axis700.grange>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
On Tue, Feb 14, 2012 at 11:37:21AM +0100, Guennadi Liakhovetski wrote:
> The current renesas_usbhs driver triggers
>
> BUG: scheduling while atomic: ksoftirqd/0/3/0x00000102
>
> with enabled CONFIG_DEBUG_ATOMIC_SLEEP, by submitting DMA transfers from
> an atomic (tasklet) context, which is not supported by the shdma dmaengine
> driver. Fix it by switching to a work.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
applied, thanks
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-02-14 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 10:37 [PATCH 2/2 v3] usb: fix renesas_usbhs to not schedule in atomic context Guennadi Liakhovetski
2012-02-14 11:46 ` Felipe Balbi [this message]
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=20120214114602.GE24201@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=linux-sh@vger.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).