From: Jonathan Cameron <jic23@kernel.org>
To: Stefan Wahren <stefan.wahren@chargebyte.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Evgeniy Polyakov <zbr@ioremap.net>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-imx@nxp.com, Li Yang <leoyang.li@nxp.com>,
Denis Ciocca <denis.ciocca@st.com>,
soc@kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
stefan.wahren@i2se.com
Subject: Re: [PATCH V2 5/8] iio: accel: add support for IIS328DQ variant
Date: Sat, 18 Mar 2023 15:58:11 +0000 [thread overview]
Message-ID: <20230318155811.0bcf85e1@jic23-huawei> (raw)
In-Reply-To: <20230317103323.7741-6-stefan.wahren@chargebyte.com>
On Fri, 17 Mar 2023 11:33:20 +0100
Stefan Wahren <stefan.wahren@chargebyte.com> wrote:
> Since the ST IIS328DQ accelerometer is compatible to the ST LIS331DL,
> just add the new compatible to the st_accel framework.
>
> Link: https://www.st.com/resource/en/datasheet/iis328dq.pdf
> Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
Hi Stefan,
Assuming the DT binding is fine with the DT maintainers, I plan to
pick the pair of IIO fixes up through my tree. Is there any strong
reason they should go via another route?
It's common for the dts files to go via ARM soc in cases like this
and we tend not to worry that they are 'broken' until the binding docs
are visible via other trees. Other than that I can't see an obvious
reason not to split these up.
Thanks,
Jonathan
> ---
> drivers/iio/accel/st_accel.h | 1 +
> drivers/iio/accel/st_accel_core.c | 1 +
> drivers/iio/accel/st_accel_i2c.c | 5 +++++
> drivers/iio/accel/st_accel_spi.c | 5 +++++
> 4 files changed, 12 insertions(+)
>
> diff --git a/drivers/iio/accel/st_accel.h b/drivers/iio/accel/st_accel.h
> index 56ed0c776d4a..e7525615712b 100644
> --- a/drivers/iio/accel/st_accel.h
> +++ b/drivers/iio/accel/st_accel.h
> @@ -39,6 +39,7 @@
> #define LIS302DL_ACCEL_DEV_NAME "lis302dl"
> #define LSM303C_ACCEL_DEV_NAME "lsm303c_accel"
> #define SC7A20_ACCEL_DEV_NAME "sc7a20"
> +#define IIS328DQ_ACCEL_DEV_NAME "iis328dq"
>
>
> #ifdef CONFIG_IIO_BUFFER
> diff --git a/drivers/iio/accel/st_accel_core.c b/drivers/iio/accel/st_accel_core.c
> index 6b8562f684d5..5f7d81b44b1d 100644
> --- a/drivers/iio/accel/st_accel_core.c
> +++ b/drivers/iio/accel/st_accel_core.c
> @@ -517,6 +517,7 @@ static const struct st_sensor_settings st_accel_sensors_settings[] = {
> .wai_addr = ST_SENSORS_DEFAULT_WAI_ADDRESS,
> .sensors_supported = {
> [0] = H3LIS331DL_ACCEL_DEV_NAME,
> + [1] = IIS328DQ_ACCEL_DEV_NAME,
> },
> .ch = (struct iio_chan_spec *)st_accel_12bit_channels,
> .odr = {
> diff --git a/drivers/iio/accel/st_accel_i2c.c b/drivers/iio/accel/st_accel_i2c.c
> index 3f02fd5d5946..fb9e2d6f4210 100644
> --- a/drivers/iio/accel/st_accel_i2c.c
> +++ b/drivers/iio/accel/st_accel_i2c.c
> @@ -119,6 +119,10 @@ static const struct of_device_id st_accel_of_match[] = {
> .compatible = "silan,sc7a20",
> .data = SC7A20_ACCEL_DEV_NAME,
> },
> + {
> + .compatible = "st,iis328dq",
> + .data = IIS328DQ_ACCEL_DEV_NAME,
> + },
> {},
> };
> MODULE_DEVICE_TABLE(of, st_accel_of_match);
> @@ -157,6 +161,7 @@ static const struct i2c_device_id st_accel_id_table[] = {
> { LIS302DL_ACCEL_DEV_NAME },
> { LSM303C_ACCEL_DEV_NAME },
> { SC7A20_ACCEL_DEV_NAME },
> + { IIS328DQ_ACCEL_DEV_NAME },
> {},
> };
> MODULE_DEVICE_TABLE(i2c, st_accel_id_table);
> diff --git a/drivers/iio/accel/st_accel_spi.c b/drivers/iio/accel/st_accel_spi.c
> index 5740dc1820bd..f72a24f45322 100644
> --- a/drivers/iio/accel/st_accel_spi.c
> +++ b/drivers/iio/accel/st_accel_spi.c
> @@ -100,6 +100,10 @@ static const struct of_device_id st_accel_of_match[] = {
> .compatible = "st,lsm303c-accel",
> .data = LSM303C_ACCEL_DEV_NAME,
> },
> + {
> + .compatible = "st,iis328dq",
> + .data = IIS328DQ_ACCEL_DEV_NAME,
> + },
> {}
> };
> MODULE_DEVICE_TABLE(of, st_accel_of_match);
> @@ -157,6 +161,7 @@ static const struct spi_device_id st_accel_id_table[] = {
> { LIS3DE_ACCEL_DEV_NAME },
> { LIS302DL_ACCEL_DEV_NAME },
> { LSM303C_ACCEL_DEV_NAME },
> + { IIS328DQ_ACCEL_DEV_NAME },
> {},
> };
> MODULE_DEVICE_TABLE(spi, st_accel_id_table);
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-18 15:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 10:33 [PATCH V2 0/8] ARM: dts: imx6ull: Add chargebyte Tarragon support Stefan Wahren
2023-03-17 10:33 ` [PATCH V2 1/8] dt-bindings: vendor-prefixes: add chargebyte Stefan Wahren
2023-03-17 10:33 ` [PATCH V2 2/8] dt-bindings: Add DS2482/DS2484 as trivial device Stefan Wahren
2023-03-17 10:33 ` [PATCH V2 3/8] w1: ds2482: add i2c id for DS2484 Stefan Wahren
2023-03-17 10:33 ` [PATCH V2 4/8] dt-bindings: iio: st-sensors: Add IIS328DQ accelerometer Stefan Wahren
2023-03-18 15:55 ` Jonathan Cameron
2023-03-19 12:40 ` Krzysztof Kozlowski
2023-03-19 15:42 ` Jonathan Cameron
2023-03-27 10:57 ` Stefan Wahren
2023-04-01 15:38 ` Jonathan Cameron
2023-03-17 10:33 ` [PATCH V2 5/8] iio: accel: add support for IIS328DQ variant Stefan Wahren
2023-03-18 15:58 ` Jonathan Cameron [this message]
2023-03-18 17:35 ` Stefan Wahren
2023-03-19 15:42 ` Jonathan Cameron
2023-03-17 10:33 ` [PATCH V2 6/8] dt-bindings: ARM: fsl: Add chargebyte Tarragon Stefan Wahren
2023-03-19 12:41 ` Krzysztof Kozlowski
2023-03-17 10:33 ` [PATCH V2 7/8] ARM: dts: imx6ull: Add chargebyte Tarragon support Stefan Wahren
2023-03-27 5:02 ` Shawn Guo
2023-03-17 10:33 ` [PATCH V2 8/8] ARM: imx_v6_v7_defconfig: Enable Tarragon peripheral drivers Stefan Wahren
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=20230318155811.0bcf85e1@jic23-huawei \
--to=jic23@kernel.org \
--cc=arnd@arndb.de \
--cc=denis.ciocca@st.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=soc@kernel.org \
--cc=stefan.wahren@chargebyte.com \
--cc=stefan.wahren@i2se.com \
--cc=zbr@ioremap.net \
/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).