All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Eddie James <eajames@linux.ibm.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	lars@metafoo.de, joel@jms.id.au
Subject: Re: [PATCH v2 0/2] iio: pressure: dps310: Reset chip if MEAS_CFG is corrupt
Date: Sun, 22 May 2022 12:41:39 +0100	[thread overview]
Message-ID: <20220522124139.5d3f6ac5@jic23-huawei> (raw)
In-Reply-To: <20220518144818.12957-1-eajames@linux.ibm.com>

On Wed, 18 May 2022 09:48:16 -0500
Eddie James <eajames@linux.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. Include a patch to move the
> startup procedure into a function.
> 
> Changes since v1:
>  - Separate into two patches
>  - Rename 'dps310_verify_meas_cfg' to 'dps310_check_reset_meas_cfg'

Looks good to me. I'll leave this a little longer on list to give Joel
and others the opportunity to take a look.

If I seem to have lost it in a few weeks time, feel free to ping me
(it's been known to happen though I think my tracking is much less
error prone now I have moved to patchwork + my local system).

Jonathan

> 
> Eddie James (2):
>   iio: pressure: dps310: Refactor startup procedure
>   iio: pressure: dps310: Reset chip if MEAS_CFG is corrupt
> 
>  drivers/iio/pressure/dps310.c | 281 +++++++++++++++++++++-------------
>  1 file changed, 174 insertions(+), 107 deletions(-)
> 


      parent reply	other threads:[~2022-05-22 11:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 14:48 [PATCH v2 0/2] iio: pressure: dps310: Reset chip if MEAS_CFG is corrupt Eddie James
2022-05-18 14:48 ` [PATCH v2 1/2] iio: pressure: dps310: Refactor startup procedure Eddie James
2022-05-18 14:48 ` [PATCH v2 2/2] iio: pressure: dps310: Reset chip if MEAS_CFG is corrupt Eddie James
2022-05-24  2:12   ` Joel Stanley
2022-05-24 14:18     ` Eddie James
2022-05-22 11:41 ` Jonathan Cameron [this message]

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=20220522124139.5d3f6ac5@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=eajames@linux.ibm.com \
    --cc=joel@jms.id.au \
    --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 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.