[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1bba2342-a591-cbe0-bfa7-975abd91041a@fi.rohmeurope.com>
Date: Wed, 3 May 2023 09:19:00 +0000
From: "Vaittinen, Matti" <Matti.Vaittinen@...rohmeurope.com>
To: Matti Vaittinen <mazziesaccount@...il.com>
CC: Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] iio: bu27034: Ensure reset is written
On 5/2/23 19:00, Matti Vaittinen wrote:
> The reset bit must be always written to the hardware no matter what value
> is in a cache or register. Ensure this by using regmap_write_bits()
> instead of the regmap_update_bits(). Furthermore, the RESET bit may be
> self-clearing, so mark the SYSTEM_CONTROL register volatile to guarantee
> we do also read the right state - should we ever need to read it.
>
> Signed-off by: Matti Vaittinen <mazziesaccount@...il.com>
I misspelled the Signed-off-by. Sorry folks. I'll re-spin.
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
Powered by blists - more mailing lists