linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vaibhav.hiremath@linaro.org (Vaibhav Hiremath)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] mfd: 88pm80x: Add 88pm860 chip type support
Date: Thu,  9 Jul 2015 17:17:06 +0530	[thread overview]
Message-ID: <1436442431-3471-2-git-send-email-vaibhav.hiremath@linaro.org> (raw)
In-Reply-To: <1436442431-3471-1-git-send-email-vaibhav.hiremath@linaro.org>

Add chip identification support for 88PM860 device
to the pm80x_chip_mapping table.

Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
---
 drivers/mfd/88pm80x.c       | 2 ++
 include/linux/mfd/88pm80x.h | 1 +
 2 files changed, 3 insertions(+)

diff --git a/drivers/mfd/88pm80x.c b/drivers/mfd/88pm80x.c
index 5e72f65..63445ea 100644
--- a/drivers/mfd/88pm80x.c
+++ b/drivers/mfd/88pm80x.c
@@ -33,6 +33,8 @@ static struct pm80x_chip_mapping chip_mapping[] = {
 	{0x3,	CHIP_PM800},
 	/* 88PM805 chip id number */
 	{0x0,	CHIP_PM805},
+	/* 88PM860 chip id number */
+	{0x4,	CHIP_PM860},
 };
 
 /*
diff --git a/include/linux/mfd/88pm80x.h b/include/linux/mfd/88pm80x.h
index 9c5773b..2e25fb1 100644
--- a/include/linux/mfd/88pm80x.h
+++ b/include/linux/mfd/88pm80x.h
@@ -21,6 +21,7 @@ enum {
 	CHIP_INVALID = 0,
 	CHIP_PM800,
 	CHIP_PM805,
+	CHIP_PM860,
 	CHIP_MAX,
 };
 
-- 
1.9.1

  reply	other threads:[~2015-07-09 11:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 11:47 [PATCH 0/6] mfd: 88pm800: Add 88pm860 device support Vaibhav Hiremath
2015-07-09 11:47 ` Vaibhav Hiremath [this message]
2015-07-11  6:54   ` [PATCH 1/6] mfd: 88pm80x: Add 88pm860 chip type support Krzysztof Kozlowski
2015-07-09 11:47 ` [PATCH 2/6] mfd: 88pm800: Add init time initial configuration support Vaibhav Hiremath
2015-07-11  6:53   ` Krzysztof Kozlowski
2015-07-13  7:10     ` Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 3/6] mfd: devicetree: bindings: 88pm800: Add DT property for 32KHz output enable Vaibhav Hiremath
2015-07-11  7:11   ` Krzysztof Kozlowski
2015-07-13  7:24     ` Vaibhav Hiremath
2015-07-13  7:31       ` Krzysztof Kozlowski
2015-07-13  7:38         ` Vaibhav Hiremath
2015-07-13  7:44           ` Krzysztof Kozlowski
2015-07-09 11:47 ` [PATCH 4/6] mfd: 88pm800: Enable 32KHZ XO low jitter clock out Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 5/6] mfd: devicetree: bindings: 88pm800: Add DT property for dual phase enable Vaibhav Hiremath
2015-07-11  7:16   ` Krzysztof Kozlowski
2015-07-13  7:50     ` Vaibhav Hiremath
2015-07-13  8:10       ` Krzysztof Kozlowski
2015-07-13 14:27         ` Vaibhav Hiremath
2015-07-09 11:47 ` [PATCH 6/6] mfd: 88pm800: Add support for configuration of dual phase on BUCK1 Vaibhav Hiremath
2015-07-09 12:04 ` [PATCH 0/6] mfd: 88pm800: Add 88pm860 device support Krzysztof Kozlowski
2015-07-09 12:44   ` Vaibhav Hiremath
2015-07-09 12:53     ` Vaibhav Hiremath
2015-07-09 13:28       ` Krzysztof Kozlowski
2015-07-10 12:03         ` Vaibhav Hiremath
2015-07-11  6:46           ` Krzysztof Kozlowski

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=1436442431-3471-2-git-send-email-vaibhav.hiremath@linaro.org \
    --to=vaibhav.hiremath@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).