linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] mfd: max665x: Differentiate between MAX665X devices
Date: Wed, 12 Feb 2014 16:58:06 +0000	[thread overview]
Message-ID: <1392224286-31084-1-git-send-email-lee.jones@linaro.org> (raw)

This driver is pretty sparse at the moment, but once we start to add
more functionality it's highly probable that we'll be required to
differentiate between supported devices. To enable us to do that
efficiently via Device Tree we need to separate out the compatible
strings, one per variant.

Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
 drivers/mfd/max665x.c               | 3 ++-
 include/linux/mfd/max665x-private.h | 5 +++++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/drivers/mfd/max665x.c b/drivers/mfd/max665x.c
index 54fdc11..3bcb765b0 100644
--- a/drivers/mfd/max665x.c
+++ b/drivers/mfd/max665x.c
@@ -71,7 +71,8 @@ static int max665x_remove(struct i2c_client *i2c)
 }
 
 static struct of_device_id max665x_dt_match[] = {
-	{ .compatible = "maxim,max665x" },
+	{ .compatible = "maxim,max6650", .data = (void *)MAX6550 },
+	{ .compatible = "maxim,max6651", .data = (void *)MAX6551 },
 	{},
 };
 MODULE_DEVICE_TABLE(of, max665x_dt_match);
diff --git a/include/linux/mfd/max665x-private.h b/include/linux/mfd/max665x-private.h
index 293db4b..1578a04 100644
--- a/include/linux/mfd/max665x-private.h
+++ b/include/linux/mfd/max665x-private.h
@@ -23,6 +23,11 @@
 #include <linux/i2c.h>
 #include <linux/regmap.h>
 
+enum max655x_id {
+	MAX6550 = 0,
+	MAX6551,
+}
+
 struct max665x_dev {
 	struct device *dev;
 	struct mutex iolock;
-- 
1.8.3.2

                 reply	other threads:[~2014-02-12 16:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1392224286-31084-1-git-send-email-lee.jones@linaro.org \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).