devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Stuart Longland <stuartl@vrt.com.au>
Cc: Roman Fietze <roman.fietze@telemotive.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] drivers/rtc/rtc-isl12022.c: Device tree support
Date: Wed, 16 Jul 2014 09:59:04 +0100	[thread overview]
Message-ID: <20140716085904.GA26951@leverpostej> (raw)
In-Reply-To: <1405477705-16885-2-git-send-email-stuartl@vrt.com.au>

On Wed, Jul 16, 2014 at 03:28:25AM +0100, Stuart Longland wrote:
> Add some support for configuring isl12020/isl12022 devices using the
> Device Tree blob.
> 
> Signed-off-by: Stuart Longland <stuartl@vrt.com.au>

Please document this as with isl,isl12057, in
Documentation/devicetree/bindings/i2c/trivial-devices.txt

The string itself looks fine.

> ---
>  drivers/rtc/rtc-isl12022.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/drivers/rtc/rtc-isl12022.c b/drivers/rtc/rtc-isl12022.c
> index 03b8911..aa55f08 100644
> --- a/drivers/rtc/rtc-isl12022.c
> +++ b/drivers/rtc/rtc-isl12022.c
> @@ -17,6 +17,8 @@
>  #include <linux/slab.h>
>  #include <linux/module.h>
>  #include <linux/err.h>
> +#include <linux/of.h>
> +#include <linux/of_device.h>
>  
>  #define DRV_VERSION "0.1"
>  
> @@ -271,6 +273,13 @@ static int isl12022_probe(struct i2c_client *client,
>  	return PTR_ERR_OR_ZERO(isl12022->rtc);
>  }
>  
> +#ifdef CONFIG_OF
> +static struct of_device_id isl12022_dt_match[] = {
> +	{ .compatible = "isl,isl12022" },
> +	{ },
> +};
> +#endif
> +
>  static const struct i2c_device_id isl12022_id[] = {
>  	{ "isl12022", 0 },
>  	{ }
> @@ -280,6 +289,9 @@ MODULE_DEVICE_TABLE(i2c, isl12022_id);
>  static struct i2c_driver isl12022_driver = {
>  	.driver		= {
>  		.name	= "rtc-isl12022",
> +#ifdef CONFIG_OF
> +		.of_match_table = of_match_ptr(isl12022_dt_match),
> +#endif

You can drop the ifdef here, of_match_ptr(x) is NULL if !CONFIG_OF.

Thanks,
Mark.

  reply	other threads:[~2014-07-16  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  2:28 Add device tree support to ISL12022 driver Stuart Longland
     [not found] ` <1405477705-16885-1-git-send-email-stuartl-EoQOJlg3kTYQrrorzV6ljw@public.gmane.org>
2014-07-16  2:28   ` [PATCH] drivers/rtc/rtc-isl12022.c: Device tree support Stuart Longland
2014-07-16  8:59     ` Mark Rutland [this message]
2014-07-16  9:35       ` Stuart Longland
2014-07-16 21:31       ` [REVISED PATCH] " Stuart Longland
2014-07-16 21:31         ` [PATCH 1/2] " Stuart Longland
2014-07-16 21:31         ` [PATCH 2/2] devicetree: Document binding for isl12022 driver Stuart Longland
     [not found]     ` <1405477705-16885-2-git-send-email-stuartl-EoQOJlg3kTYQrrorzV6ljw@public.gmane.org>
2014-07-21 23:25       ` [PATCH] drivers/rtc/rtc-isl12022.c: Device tree support Andrew Morton

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=20140716085904.GA26951@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roman.fietze@telemotive.de \
    --cc=stuartl@vrt.com.au \
    /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).