From: Eddie James <eajames@linux.ibm.com>
To: linux-iio@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
lars@metafoo.de, jic23@kernel.org, miltonm@us.ibm.com,
eajames@linux.ibm.com
Subject: [PATCH v2 0/2] iio: humidity: si7020: Check device property for skipping reset in probe
Date: Thu, 12 May 2022 11:20:18 -0500 [thread overview]
Message-ID: <20220512162020.33450-1-eajames@linux.ibm.com> (raw)
I2C commands issued after the SI7020 is starting up or after reset
can potentially upset the startup sequence. Therefore, the host
needs to wait for the startup sequence to finish before issuing
further i2c commands. This is impractical in cases where the SI7020
is on a shared bus or behind a mux, which may switch channels at
any time (generating I2C traffic). Therefore, check for a device
property that indicates that the driver should skip resetting the
device when probing.
Changes since v1:
- Fix dt binding document
Eddie James (2):
dt-bindings: iio: humidity: Add si7020 bindings
iio: humidity: si7020: Check device property for skipping reset in probe
.../bindings/iio/humidity/silabs,si7020.yaml | 47 +++++++++++++++++++
.../devicetree/bindings/trivial-devices.yaml | 2 -
drivers/iio/humidity/si7020.c | 14 +++---
3 files changed, 55 insertions(+), 8 deletions(-)
create mode 100644 Documentation/devicetree/bindings/iio/humidity/silabs,si7020.yaml
--
2.27.0
next reply other threads:[~2022-05-12 16:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 16:20 Eddie James [this message]
2022-05-12 16:20 ` [PATCH v2 1/2] dt-bindings: iio: humidity: Add si7020 bindings Eddie James
2022-05-12 16:51 ` Jonathan Cameron
2022-05-12 17:08 ` Eddie James
2022-05-13 16:47 ` Jonathan Cameron
2022-05-13 8:55 ` Krzysztof Kozlowski
2022-05-12 16:20 ` [PATCH v2 2/2] iio: humidity: si7020: Check device property for skipping reset in probe Eddie James
2022-05-12 16:48 ` [PATCH v2 0/2] " Jonathan Cameron
2022-05-12 17:08 ` Eddie James
2022-05-13 16:45 ` Jonathan Cameron
2022-05-13 22:48 ` Peter Rosin
2022-05-14 13:43 ` Jonathan Cameron
2022-05-14 15:02 ` Peter Rosin
2022-05-18 15:28 ` Eddie James
2022-05-18 15:51 ` Eddie James
2022-05-12 19:11 ` Eddie James
2022-05-14 13:40 ` 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=20220512162020.33450-1-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miltonm@us.ibm.com \
--cc=robh+dt@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.