From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
kernel <kernel@axis.com>, Lars-Peter Clausen <lars@metafoo.de>,
linux-iio <linux-iio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: buffer: Silence lock nesting splat
Date: Tue, 23 Aug 2022 10:10:45 +0200 [thread overview]
Message-ID: <YwSLhWFbGb26B3mx@axis.com> (raw)
In-Reply-To: <20220820120800.519b5eb5@jic23-huawei>
On Sat, Aug 20, 2022 at 01:08:00PM +0200, Jonathan Cameron wrote:
> On Fri, 19 Aug 2022 11:03:55 +0300
> Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > On top of that, Fixes tag?
> It's going to be tricky to identify - the interface predates usecases that were IIO
> drivers by a long way. I guess introduction of first IIO driver that used
> a callback buffer? No idea which one that was :(
AFAICS there's only one IIO driver upstream using a callback buffer, and
it's lmp91000, so I can point the fixes tag to the patch which added
that.
By the way, note that lmp91000 actually fails to probe in mainline
without extra patches, and it seems to have been that way for a while
now. I noticed this lockdep splat when working on a new driver which
also uses a callback buffer. I can post the fixes I used to get
lmp91000 to probe successfully (in roadtest) separately.
next prev parent reply other threads:[~2022-08-23 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 8:08 [PATCH] iio: buffer: Silence lock nesting splat Vincent Whitchurch
2022-08-19 8:03 ` Andy Shevchenko
2022-08-20 11:08 ` Jonathan Cameron
2022-08-23 8:10 ` Vincent Whitchurch [this message]
2022-08-28 15:32 ` Jonathan Cameron
2022-09-01 7:04 ` Vincent Whitchurch
2022-08-20 11:06 ` Jonathan Cameron
2022-08-20 11:08 ` Lars-Peter Clausen
2022-08-23 8:12 ` Vincent Whitchurch
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=YwSLhWFbGb26B3mx@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--cc=kernel@axis.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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