[PATCH] staging: iio: ad5933: finalized device-tree support

7 views
Skip to first unread message

Marcelo Schmitt

unread,
Nov 23, 2018, 6:52:05 PM11/23/18
to la...@metafoo.de, Michael....@analog.com, ji...@kernel.org, knaa...@gmx.de, pme...@pmeerw.net, gre...@linuxfoundation.org, linu...@vger.kernel.org, de...@driverdev.osuosl.org, linux-...@vger.kernel.org, kerne...@googlegroups.com
Added a of_device_id struct variable and subsequent call to
MODULE_DEVICE_TABLE macro to complete device-tree support for this
driver.

Signed-off-by: Marcelo Schmitt <marcelo....@gmail.com>
---
drivers/staging/iio/impedance-analyzer/ad5933.c | 9 +++++++++
1 file changed, 9 insertions(+)

diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c b/drivers/staging/iio/impedance-analyzer/ad5933.c
index edb8b540bbf1..19e8b6d2865c 100644
--- a/drivers/staging/iio/impedance-analyzer/ad5933.c
+++ b/drivers/staging/iio/impedance-analyzer/ad5933.c
@@ -771,9 +771,18 @@ static const struct i2c_device_id ad5933_id[] = {

MODULE_DEVICE_TABLE(i2c, ad5933_id);

+static const struct of_device_id ad5933_of_match[] = {
+ { .compatible = "analog-devices,ad5933" },
+ { .compatible = "analog-devices,ad5934" },
+ { },
+};
+
+MODULE_DEVICE_TABLE(of, ad5933_of_match);
+
static struct i2c_driver ad5933_driver = {
.driver = {
.name = "ad5933",
+ .of_match_table = ad5933_of_match,
},
.probe = ad5933_probe,
.remove = ad5933_remove,
--
2.17.1

Rodrigo Siqueira

unread,
Nov 23, 2018, 7:35:23 PM11/23/18
to Marcelo Schmitt, la...@metafoo.de, Michael....@analog.com, ji...@kernel.org, knaa...@gmx.de, pme...@pmeerw.net, gre...@linuxfoundation.org, linu...@vger.kernel.org, de...@driverdev.osuosl.org, linux-...@vger.kernel.org, kerne...@googlegroups.com
Hi Marcelo,

I believe that a proper commit message for this patch could be something
like "Add device tree support".
> --
> You received this message because you are subscribed to the Google Groups "Kernel USP" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to kernel-usp+...@googlegroups.com.
> To post to this group, send email to kerne...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kernel-usp/20181123235159.hh43xnvvwsil4on2%40smtp.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

--
Rodrigo Siqueira
https://siqueira.tech
https://twitter.com/siqueirajordao
Graduate Student
Department of Computer Science
University of São Paulo
signature.asc

Slawomir Stepien

unread,
Nov 24, 2018, 3:21:19 AM11/24/18
to Marcelo Schmitt, la...@metafoo.de, Michael....@analog.com, ji...@kernel.org, knaa...@gmx.de, pme...@pmeerw.net, gre...@linuxfoundation.org, linu...@vger.kernel.org, de...@driverdev.osuosl.org, linux-...@vger.kernel.org, kerne...@googlegroups.com
On lis 23, 2018 21:51, Marcelo Schmitt wrote:
> Added a of_device_id struct variable and subsequent call to
> MODULE_DEVICE_TABLE macro to complete device-tree support for this
> driver.
>
> Signed-off-by: Marcelo Schmitt <marcelo....@gmail.com>
> ---
> drivers/staging/iio/impedance-analyzer/ad5933.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c b/drivers/staging/iio/impedance-analyzer/ad5933.c
> index edb8b540bbf1..19e8b6d2865c 100644
> --- a/drivers/staging/iio/impedance-analyzer/ad5933.c
> +++ b/drivers/staging/iio/impedance-analyzer/ad5933.c
> @@ -771,9 +771,18 @@ static const struct i2c_device_id ad5933_id[] = {
>
> MODULE_DEVICE_TABLE(i2c, ad5933_id);
>
> +static const struct of_device_id ad5933_of_match[] = {
> + { .compatible = "analog-devices,ad5933" },
> + { .compatible = "analog-devices,ad5934" },

Why "analog-devices", rather than "adi"? My understanding is that analog devices
have "adi" as a manufacture part in compatible.

> + { },
> +};
> +
> +MODULE_DEVICE_TABLE(of, ad5933_of_match);
> +
> static struct i2c_driver ad5933_driver = {
> .driver = {
> .name = "ad5933",
> + .of_match_table = ad5933_of_match,
> },
> .probe = ad5933_probe,
> .remove = ad5933_remove,

--
Slawomir Stepien
Reply all
Reply to author
Forward
0 new messages