From: Guenter Roeck <linux@roeck-us.net>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: jdelvare@suse.com, robh+dt@kernel.org, mark.rutland@arm.com,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] hwmon: (hih6130) add dtb compatibility tables
Date: Thu, 3 Jan 2019 20:25:45 -0800 [thread overview]
Message-ID: <20190104042545.GA22722@roeck-us.net> (raw)
In-Reply-To: <20181227151349.29753-2-andreas@kemnade.info>
On Thu, Dec 27, 2018 at 04:13:48PM +0100, Andreas Kemnade wrote:
> This allows the hih6130 to be used in devicetree files and auto-probed
> that way.
>
> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
Applie to hwmon-next.
Thanks,
Guenter
> ---
> drivers/hwmon/hih6130.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/hih6130.c b/drivers/hwmon/hih6130.c
> index 0ae1ee1dbf76..de1b50ddc740 100644
> --- a/drivers/hwmon/hih6130.c
> +++ b/drivers/hwmon/hih6130.c
> @@ -254,8 +254,17 @@ static const struct i2c_device_id hih6130_id[] = {
> };
> MODULE_DEVICE_TABLE(i2c, hih6130_id);
>
> +static const struct of_device_id hih6130_of_match[] = {
> + { .compatible = "honeywell,hih6130", },
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, hih6130_of_match);
> +
> static struct i2c_driver hih6130_driver = {
> - .driver.name = "hih6130",
> + .driver = {
> + .name = "hih6130",
> + .of_match_table = of_match_ptr(hih6130_of_match),
> + },
> .probe = hih6130_probe,
> .id_table = hih6130_id,
> };
next prev parent reply other threads:[~2019-01-04 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 15:13 [PATCH 0/2] hwmon: devicetree support for hih6130 Andreas Kemnade
2018-12-27 15:13 ` [PATCH 1/2] hwmon: (hih6130) add dtb compatibility tables Andreas Kemnade
2019-01-04 4:25 ` Guenter Roeck [this message]
2018-12-27 15:13 ` [PATCH 2/2] devicetree: hwmon: Add bindings documentation for HIH6130 Andreas Kemnade
2019-01-03 22:58 ` Rob Herring
2019-01-04 4:26 ` Guenter Roeck
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=20190104042545.GA22722@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andreas@kemnade.info \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).