Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1430303

[PATCH v5 3/7] max8903: cleans up confusing relationship between dc_valid, dok and dcm.

Path csiph.com!weretis.net!feeder4.news.weretis.net!storethat.news.telefonica.de!telefonica.de!news.panservice.it!bofh.it!news.nic.it!robomod
From Chris Lapa <chris@lapa.com.au>
Newsgroups linux.kernel
Subject [PATCH v5 3/7] max8903: cleans up confusing relationship between dc_valid, dok and dcm.
Date Fri, 24 Jun 2016 04:30:01 +0200
Message-ID <rNp2x-263-9@gated-at.bofh.it> (permalink)
References <rFuC5-2sz-13@gated-at.bofh.it> <rNp2x-263-5@gated-at.bofh.it>
X-Original-To k.kozlowski@samsung.com, dwmw2@infradead.org, dbaryshkov@gmail.com, sre@kernel.org, mark.rutland@arm.com, robh+dt@kernel.org
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=lapa-com-au.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :in-reply-to:references; bh=BNrojdQrjkdjVW4NkJjpvxhFGbNoI/mDTRtRGd8Bv2o=; b=VF1A1zvPE4gg3awDQocUE/AgyVWyzeMi3cipbOf3mttSuXFIu+xlMOWRK91Zw9Wwc3 dGDsXxPmNaovOv096Hc6k9ZBusgd0GdF6p4/Oy4l1rifCy2ufRKGqViLuTIJraMMuFmr /wuFYhIDolNeyTBhgKaQBZSUh1W9Dm/2hZUJpd3v15lc/HHlsO46QOj5vE9RLl2BChEd iiG7Fmlww6CyOsJ3SbTKE0Nxgkrp5rpU7asG+rWt04827aSFYwtjNm9bPdfV5DSAH4Uu 9vrUy8DHUQBJVzUWxM/Oy1BUolsdvFRVQaH0MWXWM4eRpJwpk8rmclOsLUS8rGXbOLi3 tuIQ==
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:in-reply-to:references; bh=BNrojdQrjkdjVW4NkJjpvxhFGbNoI/mDTRtRGd8Bv2o=; b=XY2Ew+DXd2TNorDd0RVux0vEg/UErMe2673gOZcaw/cvge0VpCg1E9VWZwZpoyBt0g jL+7S76GMVZ+ZvRD2z7kYAxN8i67rN4L5O18IK0YtVGDKLn2ZxCIDN94aXuv4o8fDnCb HYEz5PlPmCzNs+vwhPgl28sJO3C9uk6RhxlY0ZLClFe2zolTjgmgZ1HLXfaKMsjiAgq+ G2cA2iX+M/DaTtX8O1oZLySGy7017sv10a6zGLId2bFWiAuuHXoaw+GsINqDEyOLdZg+ wg3qTDJEePv46eZJhcIz7KJfXzJ+LyuOKscIQcKiRHrN9TWs+u0u4TjCdSEMbsLoc8Dl eHIw==
X-Gm-Message-State ALyK8tJDgvDB1XN/z1l7pAjbq1mzqn5o0jeOADk2V+EEIH3PJ6O+TjokG7QHdzHdlIRzsA==
X-Received by 10.66.21.132 with SMTP id v4mr3180108pae.54.1466735194413; Thu, 23 Jun 2016 19:26:34 -0700 (PDT)
X-Google-Original-From Chris Lapa
X-Mailer git-send-email 1.9.1
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 90
Organization linux.* mail to news gateway
X-Original-Cc devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, Chris Lapa <chris@lapa.com.au>
X-Original-Date Fri, 24 Jun 2016 12:26:08 +1000
X-Original-Message-ID <1466735172-13372-4-git-send-email-chris@cpdesign.com.au>
X-Original-References <1464849897-21527-3-git-send-email-chris@lapa.com.au> <1466735172-13372-1-git-send-email-chris@cpdesign.com.au>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1430303

Show key headers only | View raw


From: Chris Lapa <chris@lapa.com.au>

The max8903_charger.h file indicated that dcm and dok were not optional
when dc_valid is set.

It makes sense to have dok as a compulsory pin when dc_valid is given.
However dcm can be optionally wired to a fixed level especially when the
circuit is configured for dc power exclusively.

The previous implementation already allowed for this somewhat, however no
error was given if dok wasn't given whilst dc_valid was.

The new implementation enforces dok presence when dc_valid is given. Whilst
allowing dcm to be optional.

Signed-off-by: Chris Lapa <chris@lapa.com.au>

Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
---
 drivers/power/max8903_charger.c       | 22 +++++++++-------------
 include/linux/power/max8903_charger.h |  6 +++---
 2 files changed, 12 insertions(+), 16 deletions(-)

diff --git a/drivers/power/max8903_charger.c b/drivers/power/max8903_charger.c
index 0a5b0e1..6ec705f 100644
--- a/drivers/power/max8903_charger.c
+++ b/drivers/power/max8903_charger.c
@@ -211,27 +211,23 @@ static int max8903_probe(struct platform_device *pdev)
 	}
 
 	if (pdata->dc_valid) {
-		if (pdata->dok && gpio_is_valid(pdata->dok) &&
-				pdata->dcm && gpio_is_valid(pdata->dcm)) {
+		if (pdata->dok && gpio_is_valid(pdata->dok)) {
 			gpio = pdata->dok; /* PULL_UPed Interrupt */
 			ta_in = gpio_get_value(gpio) ? 0 : 1;
+		} else {
+			dev_err(dev, "When DC is wired, DOK should be wired as well.\n");
+			return -EINVAL;
+		}
+	}
 
+	if (pdata->dcm) {
+		if (gpio_is_valid(pdata->dcm)) {
 			gpio = pdata->dcm; /* Output */
 			gpio_set_value(gpio, ta_in);
 		} else {
-			dev_err(dev, "When DC is wired, DOK and DCM should"
-					" be wired as well.\n");
+			dev_err(dev, "Invalid pin: dcm.\n");
 			return -EINVAL;
 		}
-	} else {
-		if (pdata->dcm) {
-			if (gpio_is_valid(pdata->dcm))
-				gpio_set_value(pdata->dcm, 0);
-			else {
-				dev_err(dev, "Invalid pin: dcm.\n");
-				return -EINVAL;
-			}
-		}
 	}
 
 	if (pdata->usb_valid) {
diff --git a/include/linux/power/max8903_charger.h b/include/linux/power/max8903_charger.h
index 24f51db..89d3f1c 100644
--- a/include/linux/power/max8903_charger.h
+++ b/include/linux/power/max8903_charger.h
@@ -26,8 +26,8 @@
 struct max8903_pdata {
 	/*
 	 * GPIOs
-	 * cen, chg, flt, and usus are optional.
-	 * dok, dcm, and uok are not optional depending on the status of
+	 * cen, chg, flt, dcm and usus are optional.
+	 * dok and uok are not optional depending on the status of
 	 * dc_valid and usb_valid.
 	 */
 	int cen;	/* Charger Enable input */
@@ -41,7 +41,7 @@ struct max8903_pdata {
 	/*
 	 * DC(Adapter/TA) is wired
 	 * When dc_valid is true,
-	 *	dok and dcm should be valid.
+	 *	dok should be valid.
 	 *
 	 * At least one of dc_valid or usb_valid should be true.
 	 */
-- 
1.9.1

Back to linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

[PATCH v5 3/7] max8903: cleans up confusing relationship between dc_valid, dok and dcm. Chris Lapa <chris@lapa.com.au> - 2016-06-24 04:30 +0200

csiph-web