mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve Twiss <stwiss.opensource@diasemi.com>
To: LINUX-KERNEL <linux-kernel@vger.kernel.org>,
	Lee Jones <lee.jones@linaro.org>
Cc: Support Opensource <support.opensource@diasemi.com>
Subject: [PATCH V1] mfd: da9061: fix to remove BBAT_CONT register from chip model
Date: Mon, 5 Jun 2017 15:35:10 +0100	[thread overview]
Message-ID: <20170605144304.16EE23FB98@swsrvapps-01.diasemi.com> (raw)

From: Steve Twiss <stwiss.opensource@diasemi.com>

Remove the register DA9062AA_BBAT_CONT (0x0C5) from the DA9061 chip model
regmap access ranges. This applies to both da9061_aa_readable_ranges[]
and da9061_aa_writeable_ranges[].

This change is to correct the DA9061 chip model and align it with the
latest DA9061 Datasheet.

This register previously appeared in the DA9061 Datasheet, Revision 3.2,
01-Mar-2016 and has been removed from later DA9061 datasheet from Dialog,
Revision 3.3, 04-Apr-2017.

Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>

---

Hi Lee,

This is a fix to remove DA9062AA_BBAT_CONT register from the DA9061
regmap read/write access tables. It only applies to the DA9061 chip,
and does not affect the DA9062.

No existing kernel code tries to access this register, so the change is
just a formality to correct the DA9061 chip model and align it with the
DA9061 Datasheet.

This patch applies against linux-next and v4.12-rc3

Regards,
Steve Twiss, Dialog Semiconductor


 drivers/mfd/da9062-core.c | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/drivers/mfd/da9062-core.c b/drivers/mfd/da9062-core.c
index 7f5e8be..fe18115 100644
--- a/drivers/mfd/da9062-core.c
+++ b/drivers/mfd/da9062-core.c
@@ -429,9 +429,6 @@ static int da9062_get_device_type(struct da9062 *chip)
 		.range_min = DA9062AA_VLDO1_B,
 		.range_max = DA9062AA_VLDO4_B,
 	}, {
-		.range_min = DA9062AA_BBAT_CONT,
-		.range_max = DA9062AA_BBAT_CONT,
-	}, {
 		.range_min = DA9062AA_INTERFACE,
 		.range_max = DA9062AA_CONFIG_E,
 	}, {
@@ -514,9 +511,6 @@ static int da9062_get_device_type(struct da9062 *chip)
 		.range_min = DA9062AA_VLDO1_B,
 		.range_max = DA9062AA_VLDO4_B,
 	}, {
-		.range_min = DA9062AA_BBAT_CONT,
-		.range_max = DA9062AA_BBAT_CONT,
-	}, {
 		.range_min = DA9062AA_GP_ID_0,
 		.range_max = DA9062AA_GP_ID_19,
 	},
-- 
end-of-patch for PATCH V1

             reply	other threads:[~2017-06-05 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 14:35 Steve Twiss [this message]
2017-06-06  7:16 ` Lee Jones
2017-08-14 13:12   ` Steve Twiss
2017-08-15  8:29     ` Lee Jones

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=20170605144304.16EE23FB98@swsrvapps-01.diasemi.com \
    --to=stwiss.opensource@diasemi.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=support.opensource@diasemi.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

all inboxes | Powered by JetHome®