From: Jonathan Cameron <jic23@kernel.org>
To: Richard Lai <richard@richardman.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: chemical: ccs811: Corrected firmware boot/application mode transition
Date: Sat, 24 Feb 2018 12:14:09 +0000 [thread overview]
Message-ID: <20180224121409.79b38e0a@archlinux> (raw)
In-Reply-To: <1518885013-1852-1-git-send-email-richard@richardman.com>
On Sat, 17 Feb 2018 16:28:24 +0000
Richard Lai <richard@richardman.com> wrote:
> CCS811 has different I2C register maps in boot and application mode. When
> CCS811 is in boot mode, register APP_START (0xF4) is used to transit the
> firmware state from boot to application mode. However, APP_START is not a
> valid register location when CCS811 is in application mode (refer to
> "CCS811 Bootloader Register Map" and "CCS811 Application Register Map" in
> CCS811 datasheet). The driver should not attempt to perform a write to
> APP_START while CCS811 is in application mode, as this is not a valid or
> documented register location.
>
> When prob function is being called, the driver assumes the CCS811 sensor
> is in boot mode, and attempts to perform a write to APP_START. Although
> CCS811 powers-up in boot mode, it may have already been transited to
> application mode by previous instances, e.g. unload and reload device
> driver by the system, or explicitly by user. Depending on the system
> design, CCS811 sensor may be permanently connected to system power source
> rather than power controlled by GPIO, hence it is possible that the sensor
> is never power reset, thus the firmware could be in either boot or
> application mode at any given time when driver prob function is being
> called.
>
> This patch checks the STATUS register before attempting to send a write to
> APP_START. Only if the firmware is not in application mode and has valid
> firmware application loaded, then it will continue to start transiting the
> firmware boot to application mode.
>
> Signed-off-by: Richard Lai <richard@richardman.com>
Applied to the fixes-togreg branch of iio.git and marked for stable.
Thanks,
Jonathan
> ---
> Changes in v2:
> - Removed unnecessary macros introduced in previous patch
>
> drivers/iio/chemical/ccs811.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/iio/chemical/ccs811.c b/drivers/iio/chemical/ccs811.c
> index 840a6cb..6ad8a42 100644
> --- a/drivers/iio/chemical/ccs811.c
> +++ b/drivers/iio/chemical/ccs811.c
> @@ -129,6 +129,9 @@ static int ccs811_start_sensor_application(struct i2c_client *client)
> if (ret < 0)
> return ret;
>
> + if ((ret & CCS811_STATUS_FW_MODE_APPLICATION))
> + return 0;
> +
> if ((ret & CCS811_STATUS_APP_VALID_MASK) !=
> CCS811_STATUS_APP_VALID_LOADED)
> return -EIO;
prev parent reply other threads:[~2018-02-24 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 22:02 [PATCH] iio: chemical: ccs811: Corrected firmware boot/application mode transition Richard Lai
2018-02-17 14:25 ` Jonathan Cameron
2018-02-17 16:28 ` [PATCH v2] " Richard Lai
2018-02-24 12:14 ` 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=20180224121409.79b38e0a@archlinux \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=richard@richardman.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).