[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220820125049.4e35e721@jic23-huawei>
Date: Sat, 20 Aug 2022 12:50:49 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Eddie James <eajames@...ux.ibm.com>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
linux-iio <linux-iio@...r.kernel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Joel Stanley <joel@....id.au>
Subject: Re: [PATCH v4 2/2] iio: pressure: dps310: Reset chip if MEAS_CFG is
corrupt
On Mon, 15 Aug 2022 08:59:03 -0500
Eddie James <eajames@...ux.ibm.com> wrote:
> On 8/12/22 17:13, Andy Shevchenko wrote:
> > On Wed, Aug 10, 2022 at 12:12 AM Eddie James <eajames@...ux.ibm.com> wrote:
> >> Corruption of the MEAS_CFG register has been observed soon after
> >> system boot. In order to recover this scenario, check MEAS_CFG if
> >> measurement isn't ready, and if it's incorrect, reset the DPS310
> >> and execute the startup procedure.
> > Looks like both patches miss the Fixes tag. Can you add them?
>
>
> Well this isn't really a software fix - there's no identifiable bug in
> the driver. Just trying to recover the chip in this observed mystery
> scenario.
The tag is useful as well for where to backport this to.
Probably just tag the driver introduction.
Your description makes it clear we aren't finding faults in the
driver - just that it didn't cover this undocumented case!
Jonathan
Powered by blists - more mailing lists