From: Brian Norris <briannorris@chromium.org>
To: Lee Jones <lee.jones@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Olof Johansson <olof@lixom.net>
Cc: linux-kernel@vger.kernel.org,
Doug Anderson <dianders@chromium.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Stephen Barber <smbarber@chromium.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo <enric.balletbo@collabora.co.uk>,
Randall Spangler <rspangler@chromium.org>,
Shawn Nematbakhsh <shawnn@chromium.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Todd Broch <tbroch@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Brian Norris <briannorris@chromium.org>
Subject: [PATCH v3 1/4] mfd: cros_ec: Add cros_ec_cmd_xfer_status helper
Date: Fri, 17 Jun 2016 12:58:12 -0700 [thread overview]
Message-ID: <1466193495-95801-2-git-send-email-briannorris@chromium.org> (raw)
In-Reply-To: <1466193495-95801-1-git-send-email-briannorris@chromium.org>
From: Tomeu Vizoso <tomeu.vizoso@collabora.com>
So that callers of cros_ec_cmd_xfer don't have to repeat boilerplate
code when checking for errors from the EC side.
Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Reviewed-by: Benson Leung <bleung@chromium.org>
Signed-off-by: Brian Norris <briannorris@chromium.org>
Acked-by: Lee Jones <lee.jones@linaro.org>
Tested-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
---
v3:
* successfully spell success
v2:
* no change
---
drivers/platform/chrome/cros_ec_proto.c | 15 +++++++++++++++
include/linux/mfd/cros_ec.h | 18 ++++++++++++++++++
2 files changed, 33 insertions(+)
diff --git a/drivers/platform/chrome/cros_ec_proto.c b/drivers/platform/chrome/cros_ec_proto.c
index b6e161f71b26..ecc544c728f0 100644
--- a/drivers/platform/chrome/cros_ec_proto.c
+++ b/drivers/platform/chrome/cros_ec_proto.c
@@ -380,3 +380,18 @@ int cros_ec_cmd_xfer(struct cros_ec_device *ec_dev,
return ret;
}
EXPORT_SYMBOL(cros_ec_cmd_xfer);
+
+int cros_ec_cmd_xfer_status(struct cros_ec_device *ec_dev,
+ struct cros_ec_command *msg)
+{
+ int ret;
+
+ ret = cros_ec_cmd_xfer(ec_dev, msg);
+ if (ret < 0)
+ dev_err(ec_dev->dev, "Command xfer error (err:%d)\n", ret);
+ else if (msg->result != EC_RES_SUCCESS)
+ return -EECRESULT - msg->result;
+
+ return ret;
+}
+EXPORT_SYMBOL(cros_ec_cmd_xfer_status);
diff --git a/include/linux/mfd/cros_ec.h b/include/linux/mfd/cros_ec.h
index 64184d27e3cd..7671704aa2d5 100644
--- a/include/linux/mfd/cros_ec.h
+++ b/include/linux/mfd/cros_ec.h
@@ -40,6 +40,9 @@
#define EC_MAX_REQUEST_OVERHEAD 1
#define EC_MAX_RESPONSE_OVERHEAD 2
+/* ec_command return value for non-success result from EC */
+#define EECRESULT 1000
+
/*
* Command interface between EC and AP, for LPC, I2C and SPI interfaces.
*/
@@ -226,6 +229,21 @@ int cros_ec_cmd_xfer(struct cros_ec_device *ec_dev,
struct cros_ec_command *msg);
/**
+ * cros_ec_cmd_xfer_status - Send a command to the ChromeOS EC
+ *
+ * This function is identical to cros_ec_cmd_xfer, except it returns success
+ * status only if both the command was transmitted successfully and the EC
+ * replied with success status. It's not necessary to check msg->result when
+ * using this function.
+ *
+ * @ec_dev: EC device
+ * @msg: Message to write
+ * @return: Num. of bytes transferred on success, <0 on failure
+ */
+int cros_ec_cmd_xfer_status(struct cros_ec_device *ec_dev,
+ struct cros_ec_command *msg);
+
+/**
* cros_ec_remove - Remove a ChromeOS EC
*
* Call this to deregister a ChromeOS EC, then clean up any private data.
--
2.8.0.rc3.226.g39d4020
next prev parent reply other threads:[~2016-06-17 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 19:58 [PATCH v3 0/4] pwm: add support for ChromeOS EC PWM Brian Norris
2016-06-17 19:58 ` Brian Norris [this message]
2016-06-17 21:41 ` [v3,1/4] mfd: cros_ec: Add cros_ec_cmd_xfer_status helper Guenter Roeck
2016-06-18 1:08 ` Brian Norris
2016-06-18 4:12 ` Guenter Roeck
[not found] ` <5764CA24.1080803-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-06-20 17:32 ` Brian Norris
2016-06-18 17:09 ` Guenter Roeck
[not found] ` <5765805A.5070407-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-06-20 13:46 ` Javier Martinez Canillas
2016-06-20 17:44 ` Brian Norris
2016-06-20 18:10 ` Brian Norris
[not found] ` <20160620181020.GA46079-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-06-20 18:24 ` Javier Martinez Canillas
2016-06-17 19:58 ` [PATCH v3 2/4] mfd: cros_ec: add EC_PWM function definitions Brian Norris
2016-06-28 15:31 ` Lee Jones
2016-06-17 19:58 ` [PATCH v3 3/4] doc: dt: pwm: add binding for ChromeOS EC PWM Brian Norris
2016-06-17 19:58 ` [PATCH v3 4/4] pwm: add ChromeOS EC PWM driver Brian Norris
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=1466193495-95801-2-git-send-email-briannorris@chromium.org \
--to=briannorris@chromium.org \
--cc=bleung@chromium.org \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.co.uk \
--cc=gwendal@chromium.org \
--cc=javier@osg.samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rspangler@chromium.org \
--cc=shawnn@chromium.org \
--cc=smbarber@chromium.org \
--cc=tbroch@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=tomeu.vizoso@collabora.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;
as well as URLs for NNTP newsgroup(s).