From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Sicelo A. Mhlongo" <absicsz@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Denis Ciocca <denis.ciocca@st.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v2 3/3] iio: accel: add support for LIS302DL variant
Date: Wed, 2 Mar 2022 15:59:16 +0200 [thread overview]
Message-ID: <Yh94NEO7jJrChx8z@smile.fi.intel.com> (raw)
In-Reply-To: <20220301225432.60844-4-absicsz@gmail.com>
On Wed, Mar 02, 2022 at 12:54:32AM +0200, Sicelo A. Mhlongo wrote:
> Add support for STMicroelectronics LIS302DL accelerometer to the st_accel
> framework.
> https://www.st.com/resource/en/datasheet/lis302dl.pdf
Can this be converted to Datasheet: tag, please?
> Signed-off-by: Sicelo A. Mhlongo <absicsz@gmail.com>
...
> drivers/iio/accel/st_accel_i2c.c | 5 +++++
Doesn't SPI also need to be updated? I believe those sensors are capable
of both interfaces, but correct me, if I'm wrong.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-03-02 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 22:54 [PATCH v2 0/3] Support LIS302DL in st_accel Sicelo A. Mhlongo
2022-03-01 22:54 ` [PATCH v2 1/3] dt-bindings: iio: st,st-sensors add LIS302DL Sicelo A. Mhlongo
2022-03-02 18:04 ` Rob Herring
2022-03-01 22:54 ` [PATCH v2 2/3] iio: accel: Remove unused enum in st_accel Sicelo A. Mhlongo
2022-03-01 23:49 ` Linus Walleij
2022-03-01 22:54 ` [PATCH v2 3/3] iio: accel: add support for LIS302DL variant Sicelo A. Mhlongo
2022-03-01 23:50 ` Linus Walleij
2022-03-02 13:59 ` Andy Shevchenko [this message]
2022-03-05 15:59 ` [PATCH v2 0/3] Support LIS302DL in st_accel Jonathan Cameron
2022-03-07 8:55 ` Sicelo
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=Yh94NEO7jJrChx8z@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=absicsz@gmail.com \
--cc=denis.ciocca@st.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--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 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).