From: Eddie James <eajames@linux.ibm.com>
To: linux-iio@vger.kernel.org
Cc: jic23@kernel.org, lars@metafoo.de, linux-kernel@vger.kernel.org,
andy.shevchenko@gmail.com, joel@jms.id.au, eajames@linux.ibm.com
Subject: [PATCH v4 0/2] iio: pressure: dps310: Reset chip if MEAS_CFG is corrupt
Date: Tue, 9 Aug 2022 16:12:44 -0500 [thread overview]
Message-ID: <20220809211246.251006-1-eajames@linux.ibm.com> (raw)
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 v3:
- Don't check regmap* return codes for < 0
- Fix comment spelling
Changes since v2:
- Add some comments
- Fix the clunky control flow
Changes since v1:
- Separate into two patches
- Rename 'dps310_verify_meas_cfg' to 'dps310_check_reset_meas_cfg'
Eddie James (2):
iio: pressure: dps310: Refactor startup procedure
iio: pressure: dps310: Reset chip if MEAS_CFG is corrupt
drivers/iio/pressure/dps310.c | 276 +++++++++++++++++++++-------------
1 file changed, 172 insertions(+), 104 deletions(-)
--
2.31.1
next reply other threads:[~2022-08-09 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 21:12 Eddie James [this message]
2022-08-09 21:12 ` [PATCH v4 1/2] iio: pressure: dps310: Refactor startup procedure Eddie James
2022-08-12 22:03 ` Andy Shevchenko
2022-08-15 13:42 ` Eddie James
2022-08-19 9:42 ` Andy Shevchenko
2022-08-20 11:49 ` Jonathan Cameron
2022-09-06 19:48 ` Eddie James
2022-09-11 9:56 ` Jonathan Cameron
2022-08-09 21:12 ` [PATCH v4 2/2] iio: pressure: dps310: Reset chip if MEAS_CFG is corrupt Eddie James
2022-08-12 22:13 ` Andy Shevchenko
2022-08-15 13:59 ` Eddie James
2022-08-20 11:50 ` Jonathan Cameron
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=20220809211246.251006-1-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox