From: Boris Brezillon <boris.brezillon@collabora.com>
To: Vitor Soares <Vitor.Soares@synopsys.com>
Cc: linux-iio@vger.kernel.org, linux-i3c@lists.infradead.org,
linux-kernel@vger.kernel.org, lorenzo@kernel.org,
gregkh@linuxfoundation.org, rafael@kernel.org,
bbrezillon@kernel.org, Joao.Pinto@synopsys.com
Subject: Re: [PATCH v4 0/3] Add ST lsm6dso i3c support
Date: Fri, 12 Jul 2019 17:58:03 +0200 [thread overview]
Message-ID: <20190712175803.3e1f3ac8@linux.home> (raw)
In-Reply-To: <cover.1562931742.git.vitor.soares@synopsys.com>
On Fri, 12 Jul 2019 13:53:27 +0200
Vitor Soares <Vitor.Soares@synopsys.com> wrote:
> This patch series add i3c support for STM LSM6DSO and LSM6DSR sensors.
>
> It is also introduced i3c support on regmap api. Due the lack of
> i3c devices HDR capables on the market the support for now is only for
> i3c sdr mode by using i3c_device_do_priv_xfers() method.
>
> The i3c regmap api is already available in the Git repository at:
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
> tags/regmap-i3c
>
> Change in v4:
> remover hw_id variable from st_lsm6dsx_i3c_probe()
>
> Change in v3:
> Update st_lsm6dsx_probe() call
> Remove i3c_get_device_id() and use i3c_device_match_id()
Did not receive this v3...
>
> Changes in v2:
> Change i3c_get_device_id() to drivers/i3c/device.c
> Add support for LSM6DSR
>
> Vitor Soares (3):
> regmap: add i3c bus support
> i3c: add i3c_get_device_id helper
> iio: imu: st_lsm6dsx: add i3c basic support for LSM6DSO and LSM6DSR
>
> drivers/base/regmap/Kconfig | 6 ++-
> drivers/base/regmap/Makefile | 1 +
> drivers/base/regmap/regmap-i3c.c | 60 +++++++++++++++++++++++++++++
> drivers/i3c/device.c | 46 ++++++++++++++++++++++
> drivers/i3c/master.c | 45 ----------------------
> drivers/iio/imu/st_lsm6dsx/Kconfig | 8 +++-
> drivers/iio/imu/st_lsm6dsx/Makefile | 1 +
> drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_i3c.c | 58 ++++++++++++++++++++++++++++
> include/linux/i3c/device.h | 4 ++
> include/linux/regmap.h | 20 ++++++++++
> 10 files changed, 202 insertions(+), 47 deletions(-)
> create mode 100644 drivers/base/regmap/regmap-i3c.c
> create mode 100644 drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_i3c.c
>
prev parent reply other threads:[~2019-07-12 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 11:53 [PATCH v4 0/3] Add ST lsm6dso i3c support Vitor Soares
2019-07-12 11:53 ` [PATCH v4 1/3] regmap: add i3c bus support Vitor Soares
2019-07-12 15:59 ` Boris Brezillon
2019-07-12 16:14 ` Vitor Soares
2019-07-12 11:53 ` [PATCH v4 2/3] i3c: move i3c_device_match_id to device.c and export it Vitor Soares
2019-07-12 16:03 ` Boris Brezillon
2019-07-12 16:21 ` Vitor Soares
2019-07-12 16:34 ` Boris Brezillon
2019-07-12 11:53 ` [PATCH v4 3/3] iio: imu: st_lsm6dsx: add i3c basic support for LSM6DSO and LSM6DSR Vitor Soares
2019-07-12 16:14 ` Boris Brezillon
2019-07-12 16:28 ` Vitor Soares
2019-07-12 16:43 ` Boris Brezillon
2019-07-12 18:40 ` Vitor Soares
2019-07-12 20:03 ` Boris Brezillon
2019-07-16 13:22 ` Vitor Soares
2019-07-16 13:40 ` Boris Brezillon
2019-07-12 15:58 ` Boris Brezillon [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=20190712175803.3e1f3ac8@linux.home \
--to=boris.brezillon@collabora.com \
--cc=Joao.Pinto@synopsys.com \
--cc=Vitor.Soares@synopsys.com \
--cc=bbrezillon@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=rafael@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).