From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: dirk.behme@gmail.com
Cc: rtc-linux <rtc-linux@googlegroups.com>,
Dirk Behme <dirk.behme@de.bosch.com>,
Oleksij Rempel <linux@rempel-privat.de>
Subject: [rtc-linux] Re: rtc: RV8803: BUG: scheduling while atomic
Date: Wed, 3 Feb 2016 12:07:05 +0100 [thread overview]
Message-ID: <20160203105717.GA20165@piout.net> (raw)
In-Reply-To: <460eec38-0a09-4faa-b601-de64803ed5f3@googlegroups.com>
Hi,
On 03/02/2016 at 01:31:21 -0800, dirk.behme@gmail.com wrote :
> Testing the RV8803 driver [1] we are getting several "BUG: scheduling while
> atomic" [2].
>
> Having a quick look this might be from rv8803_set_time() holding a spinlock
> during the call to i2c_smbus_read_byte_data()?
>
> Any ideas?
>
Yes, that is probably the case. As this is already a threaded irq, it
can probably be changed into a mutex this would solve the issue. Can you
try that? I don't have much time to do it myself right now.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-02-03 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 9:31 [rtc-linux] rtc: RV8803: BUG: scheduling while atomic dirk.behme
2016-02-03 11:07 ` Alexandre Belloni [this message]
2016-02-03 12:58 ` [rtc-linux] " dirk.behme
2016-02-03 14:18 ` Alexandre Belloni
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=20160203105717.GA20165@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=dirk.behme@de.bosch.com \
--cc=dirk.behme@gmail.com \
--cc=linux@rempel-privat.de \
--cc=rtc-linux@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.