[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1650596292790607a5739fa295fd259e@kernel.org>
Date: Thu, 04 Jan 2024 10:18:59 +0100
From: Michael Walle <mwalle@...nel.org>
To: Benjamin Bara <bbara93@...il.com>
Cc: Wolfram Sang <wsa@...nel.org>, Lee Jones <lee@...nel.org>, Dmitry
Osipenko <dmitry.osipenko@...labora.com>, peterz@...radead.org, Tor Vic
<torvic9@...lbox.org>, Erhard Furtner <erhard_f@...lbox.org>,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org, Benjamin Bara
<benjamin.bara@...data.com>, stable@...r.kernel.org
Subject: Re: [PATCH] i2c: core: Fix atomic xfer check for non-preempt config
> From: Benjamin Bara <benjamin.bara@...data.com>
>
> Since commit aa49c90894d0 ("i2c: core: Run atomic i2c xfer when
> !preemptible"), the whole reboot/power off sequence on non-preempt
> kernels
> is using atomic i2c xfer, as !preemptible() always results to 1.
>
> During device_shutdown(), the i2c might be used a lot and not all
> busses
> have implemented an atomic xfer handler. This results in a lot of
> avoidable noise, like:
>
> [ 12.687169] No atomic I2C transfer handler for 'i2c-0'
> [ 12.692313] WARNING: CPU: 6 PID: 275 at drivers/i2c/i2c-core.h:40
> i2c_smbus_xfer+0x100/0x118
> ...
>
> Fix this by allowing non-atomic xfer when the interrupts are enabled,
> as
> it was before.
>
> Fixes: aa49c90894d0 ("i2c: core: Run atomic i2c xfer when
> !preemptible")
> Cc: stable@...r.kernel.org # v5.2+
> Signed-off-by: Benjamin Bara <benjamin.bara@...data.com>
Tested-by: Michael Walle <mwalle@...nel.org>
Thanks for the fix, if there will be a -rc9 this should definitely go
in.
-michael
Powered by blists - more mailing lists