linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
To: krzk@kernel.org, sre@kernel.org, dbaryshkov@gmail.com,
	dwmw2@infradead.org
Cc: cw00.choi@samsung.com, b.zolnierkie@samsung.com,
	broonie@kernel.org, lgirdwood@gmail.com, lee.jones@linaro.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
Subject: [PATCH 1/3] mfd: max77693: Add defines for charger current control
Date: Tue, 27 Sep 2016 01:31:08 +0200	[thread overview]
Message-ID: <1474932670-11953-2-git-send-email-wolfgit@wiedmeyer.de> (raw)
In-Reply-To: <1474932670-11953-1-git-send-email-wolfgit@wiedmeyer.de>

This prepares for an updated regulator and charger driver. The defines
are needed to set the maximum input current and the fast charge
current.

Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
---
 include/linux/mfd/max77693-private.h | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/include/linux/mfd/max77693-private.h b/include/linux/mfd/max77693-private.h
index 3c7a63b..ca18344 100644
--- a/include/linux/mfd/max77693-private.h
+++ b/include/linux/mfd/max77693-private.h
@@ -222,6 +222,9 @@ enum max77693_charger_battery_state {
 #define CHG_CNFG_00_CHG_MASK		0x1
 #define CHG_CNFG_00_BUCK_MASK		0x4
 
+/* MAX77693 CHG_CNFG_02 register */
+#define CHG_CNFG_02_CC_MASK		0x3F
+
 /* MAX77693_CHG_REG_CHG_CNFG_01 register */
 #define CHG_CNFG_01_FCHGTIME_SHIFT	0
 #define CHG_CNFG_01_CHGRSTRT_SHIFT	4
@@ -258,6 +261,10 @@ enum max77693_charger_battery_state {
 
 /* MAX77693 CHG_CNFG_09 Register */
 #define CHG_CNFG_09_CHGIN_ILIM_MASK	0x7F
+#define CHG_CNFG_09_CHGIN_ILIM_500_MAX	500000
+#define CHG_CNFG_09_CHGIN_ILIM_500_MIN	470000
+#define CHG_CNFG_09_CHGIN_ILIM_0_MAX	60000
+#define CHG_CNFG_09_CHGIN_ILIM_0_MIN	0
 
 /* MAX77693 CHG_CTRL Register */
 #define SAFEOUT_CTRL_SAFEOUT1_MASK	0x3
-- 
2.8.0.rc3

  reply	other threads:[~2016-09-26 23:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 23:31 [PATCH 0/3] max77693: USB event listener for charger Wolfgang Wiedmeyer
2016-09-26 23:31 ` Wolfgang Wiedmeyer [this message]
2016-09-27  8:06   ` [PATCH 1/3] mfd: max77693: Add defines for charger current control Krzysztof Kozlowski
2016-09-27 13:54     ` Wolfgang Wiedmeyer
2016-09-26 23:31 ` [PATCH 2/3] regulator: max77693: Also manipulate the fast charge current Wolfgang Wiedmeyer
2016-09-27  8:03   ` Krzysztof Kozlowski
2016-09-27 13:50     ` Wolfgang Wiedmeyer
2016-09-27 16:15       ` Mark Brown
2016-09-27 17:51         ` Wolfgang Wiedmeyer
2016-09-28  8:04           ` Krzysztof Kozlowski
2016-09-26 23:31 ` [PATCH 3/3] power_supply: max77693: Listen for cable events and enable charging Wolfgang Wiedmeyer
2016-09-27  8:13   ` Krzysztof Kozlowski
2016-09-27 13:34     ` Wolfgang Wiedmeyer
2016-09-28  7:56       ` 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=1474932670-11953-2-git-send-email-wolfgit@wiedmeyer.de \
    --to=wolfgit@wiedmeyer.de \
    --cc=b.zolnierkie@samsung.com \
    --cc=broonie@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=dbaryshkov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=krzk@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@kernel.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).