From: Hans de Goede <hdegoede@redhat.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Hartmut Knaack <knaack.h@gmx.de>,
linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Jonathan Cameron <jic23@kernel.org>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Subject: Re: [PATCH] iio: accel: bmc150: Add OF device ID table
Date: Mon, 4 Dec 2017 09:29:38 +0100 [thread overview]
Message-ID: <313108f3-2815-b030-4fa6-614efc31a8a9@redhat.com> (raw)
In-Reply-To: <20171201111058.13483-1-javierm@redhat.com>
Hi,
On 01-12-17 12:10, Javier Martinez Canillas wrote:
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the assumption that a
> I2C device registered via OF will always match a legacy I2C device ID and
> that the MODALIAS reported will always be of the form i2c:<device>.
>
> But this could change in the future so the correct approach is to have an
> OF device ID table if the devices are registered via OF.
>
> The I2C device ID table entries have the .driver_data field set, but they
> are not used in the driver so weren't set in the OF device table entries.
>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> ---
>
> drivers/iio/accel/bmc150-accel-i2c.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/iio/accel/bmc150-accel-i2c.c b/drivers/iio/accel/bmc150-accel-i2c.c
> index f85014fbaa12..8ffc308d5fd0 100644
> --- a/drivers/iio/accel/bmc150-accel-i2c.c
> +++ b/drivers/iio/accel/bmc150-accel-i2c.c
> @@ -81,9 +81,21 @@ static const struct i2c_device_id bmc150_accel_id[] = {
>
> MODULE_DEVICE_TABLE(i2c, bmc150_accel_id);
>
> +static const struct of_device_id bmc150_accel_of_match[] = {
> + { .compatible = "bosch,bmc150_accel" },
> + { .compatible = "bosch,bmi055_accel" },
These look a bit weird, there is no reason to mirror the i2c_device_ids
here and typically for devicetree / of we only list
the chip model without some postfix like _accel.
Also if you're doing this you should probably add a:
Documentation/devicetree/bindings/iio/accel/bmc150.txt
file documenting the compatible strings, and Cc:
devicetree@vger.kernel.org for the next version,
so that the devicetree maintainers get a chance to review
this.
> + { .compatible = "bosch,bma255" },
> + { .compatible = "bosch,bma250e" },
> + { .compatible = "bosch,bma222e" },
> + { .compatible = "bosch,bma280" },
> + { },
> +};
> +MODULE_DEVICE_TABLE(of, bmc150_accel_of_match);
> +
> static struct i2c_driver bmc150_accel_driver = {
> .driver = {
> .name = "bmc150_accel_i2c",
> + .of_match_table = bmc150_accel_of_match,
> .acpi_match_table = ACPI_PTR(bmc150_accel_acpi_match),
> .pm = &bmc150_accel_pm_ops,
> },
>
Otherwise looks good to me,
Regards,
Hans
next prev parent reply other threads:[~2017-12-04 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 11:10 Javier Martinez Canillas
2017-12-02 12:02 ` Jonathan Cameron
2017-12-03 1:11 ` Javier Martinez Canillas
2017-12-04 8:29 ` Hans de Goede [this message]
2017-12-04 9:01 ` Javier Martinez Canillas
2017-12-04 9:36 ` Hans de Goede
[not found] ` <20171204092259.00006250@huawei.com>
2017-12-04 9:47 ` Hans de Goede
2017-12-04 10:24 ` Javier Martinez Canillas
2017-12-10 16:12 ` Jonathan Cameron
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=313108f3-2815-b030-4fa6-614efc31a8a9@redhat.com \
--to=hdegoede@redhat.com \
--cc=javierm@redhat.com \
--cc=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 \
/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
Powered by JetHome