public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <jhovold@gmail.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Johan Hovold <jhovold@gmail.com>
Subject: [PATCH 2/2] mfd: Mark two lm3533 zone registers as volatile
Date: Fri, 18 May 2012 20:22:46 +0200	[thread overview]
Message-ID: <1337365366-14385-2-git-send-email-jhovold@gmail.com> (raw)
In-Reply-To: <1337365366-14385-1-git-send-email-jhovold@gmail.com>

Mark the two currently unused zone registers as volatile in regmap for
completeness.

Signed-off-by: Johan Hovold <jhovold@gmail.com>
---
 drivers/mfd/lm3533-core.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/mfd/lm3533-core.c b/drivers/mfd/lm3533-core.c
index 104faba..0b2879b 100644
--- a/drivers/mfd/lm3533-core.c
+++ b/drivers/mfd/lm3533-core.c
@@ -567,7 +567,7 @@ static bool lm3533_readable_register(struct device *dev, unsigned int reg)
 static bool lm3533_volatile_register(struct device *dev, unsigned int reg)
 {
 	switch (reg) {
-	case 0x34:		/* zone */
+	case 0x34 ... 0x36:	/* zone */
 	case 0x37 ... 0x38:	/* adc */
 	case 0xb0 ... 0xb1:	/* fault */
 		return true;
-- 
1.7.8.5


  reply	other threads:[~2012-05-18 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 18:22 [PATCH 1/2] mfd: Add r_select to lm3533 platform data Johan Hovold
2012-05-18 18:22 ` Johan Hovold [this message]
2012-05-20 13:20   ` [PATCH 2/2] mfd: Mark two lm3533 zone registers as volatile Samuel Ortiz
2012-05-20 13:13 ` [PATCH 1/2] mfd: Add r_select to lm3533 platform data Samuel Ortiz
2012-05-21  8:45   ` Johan Hovold
2012-05-21  9:08     ` Samuel Ortiz
2012-05-21  9:41       ` Johan Hovold
2012-05-22 21:52         ` Samuel Ortiz

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=1337365366-14385-2-git-send-email-jhovold@gmail.com \
    --to=jhovold@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    /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