From: Jonathan Cameron <jic23@kernel.org>
To: Marius Hoch <mail@mariushoch.de>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Denis Ciocca <denis.ciocca@st.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Marius Hoch <marius@mariushoch.de>
Subject: Re: [PATCH v3 4/6] iio: st_sensors: Add ACPI support for lsm303d to the LSM9DS0 IMU driver
Date: Sun, 7 May 2023 14:50:22 +0100 [thread overview]
Message-ID: <20230507145022.1465b89d@jic23-huawei> (raw)
In-Reply-To: <e669d656-1474-ad95-4667-3a6ae79605e3@mariushoch.de>
On Tue, 2 May 2023 16:51:42 +0200
Marius Hoch <mail@mariushoch.de> wrote:
> Hi,
>
> On 16/04/2023 01:11, Marius Hoch wrote:
> <snip>
> > diff --git a/drivers/iio/imu/st_lsm9ds0/st_lsm9ds0_spi.c b/drivers/iio/imu/st_lsm9ds0/st_lsm9ds0_spi.c
> > index 997b5ff792be..55f3738193af 100644
> > --- a/drivers/iio/imu/st_lsm9ds0/st_lsm9ds0_spi.c
> > +++ b/drivers/iio/imu/st_lsm9ds0/st_lsm9ds0_spi.c
> > @@ -37,6 +37,12 @@ static const struct spi_device_id st_lsm9ds0_id_table[] = {
> > };
> > MODULE_DEVICE_TABLE(spi, st_lsm9ds0_id_table);
> >
> > +static const struct acpi_device_id st_lsm9ds0_acpi_match[] = {
> > + {"ACCL0001", (kernel_ulong_t)LSM303D_IMU_DEV_NAME},
> > + { },
> > +};
> > +MODULE_DEVICE_TABLE(acpi, st_lsm9ds0_acpi_match);
> > +
> > static const struct regmap_config st_lsm9ds0_regmap_config = {
> > .reg_bits = 8,
> > .val_bits = 8,
> > @@ -72,6 +78,7 @@ static struct spi_driver st_lsm9ds0_driver = {
> > .driver = {
> > .name = "st-lsm9ds0-spi",
> > .of_match_table = st_lsm9ds0_of_match,
> > + .acpi_match_table = st_lsm9ds0_acpi_match,
> > },
> > .probe = st_lsm9ds0_spi_probe,
> > .id_table = st_lsm9ds0_id_table,
> I just realized that these changes (the SPI ones, not the I2C ones) are
> entirely superfluous, and I'm not sure why I added this in the first
> place. In the Lenovo Yoga Tablet 2 series (which seem to be the only
> devices exposing this as "ACCL0001"), the device is accessible via I2C.
> Just to make sure, I re-tested the patch chain without this change.
>
> @Jonathan: Shall I upload an entirely new patch set (v4), do this in a
> separate new clean up commit, or do you want to just drop these changes
> to drivers/iio/imu/st_lsm9ds0/st_lsm9ds0_spi.c? I'm fine with any of
> these options.
I'll drop it and push out a new version of the togreg tree.
Thanks for pointing this out.
Jonathan
>
> Cheers,
> Marius
next prev parent reply other threads:[~2023-05-07 13:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 23:11 [PATCH v3 0/6] iio: st_sensors: Add lsm303d support Marius Hoch
2023-04-15 23:11 ` [PATCH v3 1/6] iio: accel: st_accel: Add LSM303D Marius Hoch
2023-04-21 8:41 ` Linus Walleij
2023-04-15 23:11 ` [PATCH v3 2/6] iio: magnetometer: " Marius Hoch
2023-04-21 8:41 ` Linus Walleij
2023-04-15 23:11 ` [PATCH v3 3/6] iio: st_sensors: Add lsm303d support to the LSM9DS0 IMU driver Marius Hoch
2023-04-21 8:42 ` Linus Walleij
2023-04-15 23:11 ` [PATCH v3 4/6] iio: st_sensors: Add ACPI support for lsm303d " Marius Hoch
2023-04-21 8:43 ` Linus Walleij
2023-05-02 14:51 ` Marius Hoch
2023-05-07 13:50 ` Jonathan Cameron [this message]
2023-04-15 23:11 ` [PATCH v3 5/6] iio: Comment that the LSM303D also has the Magnetometer DRDY Marius Hoch
2023-04-21 8:43 ` Linus Walleij
2023-04-15 23:11 ` [PATCH v3 6/6] dt-bindings: iio: st-sensors: Add LSM303D accelerometer+magnetometer Marius Hoch
2023-04-16 7:29 ` Krzysztof Kozlowski
2023-04-16 12:23 ` Jonathan Cameron
2023-04-16 20:19 ` [PATCH v3 0/6] iio: st_sensors: Add lsm303d support Hans de Goede
2023-04-20 17:21 ` Marius Hoch
2023-04-21 7:55 ` Hans de Goede
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=20230507145022.1465b89d@jic23-huawei \
--to=jic23@kernel.org \
--cc=denis.ciocca@st.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@mariushoch.de \
--cc=marius@mariushoch.de \
--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