From: Jonathan Cameron <jic23@kernel.org>
To: Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
lorenzo.bianconi@st.com
Subject: Re: [PATCH 3/9] iio: humidity: hts221: do not overwrite reserved data during power-down
Date: Sun, 9 Jul 2017 19:30:42 +0100 [thread overview]
Message-ID: <20170709193042.330fcd60@kernel.org> (raw)
In-Reply-To: <20170709165704.26311-4-lorenzo.bianconi@st.com>
On Sun, 9 Jul 2017 18:56:58 +0200
Lorenzo Bianconi <lorenzo.bianconi83@gmail.com> wrote:
> Fixes: e4a70e3e7d84 (iio: humidity: add support to hts221 rh/temp device)
> Fixes: b7079eeac5da (iio: humidity: hts221: add power management support)
> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@st.com>
This needs more description. What is the effect of this?
Which bits of data are we writing that we shouldn't be touching?
> ---
> drivers/iio/humidity/hts221_core.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iio/humidity/hts221_core.c b/drivers/iio/humidity/hts221_core.c
> index 9546b0ea6283..b36734b8070e 100644
> --- a/drivers/iio/humidity/hts221_core.c
> +++ b/drivers/iio/humidity/hts221_core.c
> @@ -305,11 +305,10 @@ int hts221_power_on(struct hts221_hw *hw)
>
> int hts221_power_off(struct hts221_hw *hw)
> {
> - __le16 data = 0;
> int err;
>
> - err = hw->tf->write(hw->dev, HTS221_REG_CNTRL1_ADDR, sizeof(data),
> - (u8 *)&data);
> + err = hts221_write_with_mask(hw, HTS221_REG_CNTRL1_ADDR,
> + HTS221_ENABLE_MASK, false);
> if (err < 0)
> return err;
>
> @@ -692,11 +691,10 @@ static int __maybe_unused hts221_suspend(struct device *dev)
> {
> struct iio_dev *iio_dev = dev_get_drvdata(dev);
> struct hts221_hw *hw = iio_priv(iio_dev);
> - __le16 data = 0;
> int err;
>
> - err = hw->tf->write(hw->dev, HTS221_REG_CNTRL1_ADDR, sizeof(data),
> - (u8 *)&data);
> + err = hts221_write_with_mask(hw, HTS221_REG_CNTRL1_ADDR,
> + HTS221_ENABLE_MASK, false);
>
> return err < 0 ? err : 0;
> }
next prev parent reply other threads:[~2017-07-09 18:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 16:56 [PATCH 0/9] hts221: add new features and fix power-off procedure Lorenzo Bianconi
2017-07-09 16:56 ` [PATCH 1/9] iio: humidity: hts221: refactor write_with_mask code Lorenzo Bianconi
2017-07-09 18:28 ` Jonathan Cameron
2017-07-09 21:18 ` Lorenzo Bianconi
2017-07-10 20:47 ` Jonathan Cameron
2017-07-09 16:56 ` [PATCH 2/9] iio: humidity: hts221: move BDU configuration in probe routine Lorenzo Bianconi
2017-07-09 18:29 ` Jonathan Cameron
2017-07-09 16:56 ` [PATCH 3/9] iio: humidity: hts221: do not overwrite reserved data during power-down Lorenzo Bianconi
2017-07-09 18:30 ` Jonathan Cameron [this message]
2017-07-09 21:26 ` Lorenzo Bianconi
2017-07-09 16:56 ` [PATCH 4/9] iio: humidity: hts221: avoid useless ODR reconfiguration Lorenzo Bianconi
2017-07-09 18:32 ` Jonathan Cameron
2017-07-09 21:27 ` Lorenzo Bianconi
2017-07-09 16:57 ` [PATCH 5/9] iio: humidity: hts221: support active-low interrupts Lorenzo Bianconi
2017-07-09 18:39 ` Jonathan Cameron
2017-07-10 9:36 ` Marc Zyngier
2017-07-11 18:52 ` Jonathan Cameron
2017-07-09 16:57 ` [PATCH 6/9] dt-bindings: " Lorenzo Bianconi
2017-07-11 2:49 ` Rob Herring
2017-07-09 16:57 ` [PATCH 7/9] iio: humidity: hts221: support open drain mode Lorenzo Bianconi
2017-07-09 16:57 ` [PATCH 8/9] dt-bindings: " Lorenzo Bianconi
2017-07-11 2:51 ` Rob Herring
2017-07-11 18:26 ` Jonathan Cameron
2017-07-11 18:42 ` Rob Herring
2017-07-11 18:56 ` Jonathan Cameron
2017-07-15 14:32 ` Lorenzo Bianconi
2017-07-17 11:49 ` Jonathan Cameron
2017-07-09 16:57 ` [PATCH 9/9] iio: humidity: hts221: move drdy enable logic in hts221_trig_set_state() Lorenzo Bianconi
2017-07-09 18:41 ` Jonathan Cameron
2017-07-09 21:28 ` Lorenzo Bianconi
2017-07-16 9:45 ` Lorenzo Bianconi
2017-07-16 19: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=20170709193042.330fcd60@kernel.org \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=lorenzo.bianconi@st.com \
/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;
as well as URLs for NNTP newsgroup(s).