Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1709074 > unrolled thread
| Started by | Thierry Escande <thierry.escande@collabora.com> |
|---|---|
| First post | 2017-08-11 00:20 +0200 |
| Last post | 2017-08-11 06:10 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH 0/8] platform/chrome: cros_ec: Fixes and improvements Thierry Escande <thierry.escande@collabora.com> - 2017-08-11 00:20 +0200
[PATCH 5/8] mfd: cros_ec: fail early if we cannot identify the EC Thierry Escande <thierry.escande@collabora.com> - 2017-08-11 00:20 +0200
Re: [PATCH 5/8] mfd: cros_ec: fail early if we cannot identify the EC Benson Leung <bleung@google.com> - 2017-08-11 06:10 +0200
| From | Thierry Escande <thierry.escande@collabora.com> |
|---|---|
| Date | 2017-08-11 00:20 +0200 |
| Subject | [PATCH 0/8] platform/chrome: cros_ec: Fixes and improvements |
| Message-ID | <ud3Y5-3tF-3@gated-at.bofh.it> |
Hi,
This series contains various fixes and improvements for the ChromeOS
Embedded Controller drivers. These concern PM suspend/resume fixes,
sysfs interface, and module initialization.
Regards,
Thierry
Daniel Hung-yu Wu (1):
platform/chrome: cros_ec: register shutdown function for debugfs
Douglas Anderson (1):
mfd: cros_ec: Stop the debugfs work when suspended
Gwendal Grignou (3):
iio: cros_ec: Relax sampling frequency before suspending
platform/chrome: cros_ec: Add sysfs entry to set keyboard wake lid
angle
platform/chrome: cros_ec: sysfs: Modify error handling
Joseph Lo (1):
mfd: cros_ec_i2c: move the system sleep pm ops to late
Vincent Palatin (1):
mfd: cros_ec: fail early if we cannot identify the EC
Wei-Ning Huang (1):
mfd: cros_ec_i2c: add ACPI module device table
.../iio/common/cros_ec_sensors/cros_ec_sensors.c | 1 +
.../common/cros_ec_sensors/cros_ec_sensors_core.c | 52 +++++++++++
.../common/cros_ec_sensors/cros_ec_sensors_core.h | 2 +
drivers/iio/light/cros_ec_light_prox.c | 1 +
drivers/mfd/cros_ec.c | 6 +-
drivers/mfd/cros_ec_i2c.c | 17 +++-
drivers/platform/chrome/cros_ec_debugfs.c | 18 ++++
drivers/platform/chrome/cros_ec_debugfs.h | 2 +
drivers/platform/chrome/cros_ec_dev.c | 45 +++++----
drivers/platform/chrome/cros_ec_sysfs.c | 104 ++++++++++++++++-----
include/linux/mfd/cros_ec.h | 1 +
11 files changed, 206 insertions(+), 43 deletions(-)
--
2.7.4
[toc] | [next] | [standalone]
| From | Thierry Escande <thierry.escande@collabora.com> |
|---|---|
| Date | 2017-08-11 00:20 +0200 |
| Subject | [PATCH 5/8] mfd: cros_ec: fail early if we cannot identify the EC |
| Message-ID | <ud3Y6-3tF-29@gated-at.bofh.it> |
| In reply to | #1709074 |
From: Vincent Palatin <vpalatin@chromium.org>
If we cannot communicate with the EC chip to detect the protocol version
and its features, it's very likely useless to continue. Else we will
commit all kind of uninformed mistakes (using the wrong protocol, the
wrong buffer size, mixing the EC with other chips).
Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
Signed-off-by: Thierry Escande <thierry.escande@collabora.com>
---
drivers/mfd/cros_ec.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/cros_ec.c b/drivers/mfd/cros_ec.c
index b0ca5a4c..c5528ae 100644
--- a/drivers/mfd/cros_ec.c
+++ b/drivers/mfd/cros_ec.c
@@ -112,7 +112,11 @@ int cros_ec_register(struct cros_ec_device *ec_dev)
mutex_init(&ec_dev->lock);
- cros_ec_query_all(ec_dev);
+ err = cros_ec_query_all(ec_dev);
+ if (err) {
+ dev_err(dev, "Cannot identify the EC: error %d\n", err);
+ return err;
+ }
if (ec_dev->irq) {
err = request_threaded_irq(ec_dev->irq, NULL, ec_irq_thread,
--
2.7.4
[toc] | [prev] | [next] | [standalone]
| From | Benson Leung <bleung@google.com> |
|---|---|
| Date | 2017-08-11 06:10 +0200 |
| Subject | Re: [PATCH 5/8] mfd: cros_ec: fail early if we cannot identify the EC |
| Message-ID | <ud9qN-74Q-5@gated-at.bofh.it> |
| In reply to | #1709077 |
[Multipart message — attachments visible in raw view] — view raw
Hi Thierry,
On Fri, Aug 11, 2017 at 12:16:47AM +0200, Thierry Escande wrote:
> From: Vincent Palatin <vpalatin@chromium.org>
>
> If we cannot communicate with the EC chip to detect the protocol version
> and its features, it's very likely useless to continue. Else we will
> commit all kind of uninformed mistakes (using the wrong protocol, the
> wrong buffer size, mixing the EC with other chips).
>
> Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
> Signed-off-by: Thierry Escande <thierry.escande@collabora.com>
Acked-by: Benson Leung <bleung@chromium.org>
> ---
> drivers/mfd/cros_ec.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mfd/cros_ec.c b/drivers/mfd/cros_ec.c
> index b0ca5a4c..c5528ae 100644
> --- a/drivers/mfd/cros_ec.c
> +++ b/drivers/mfd/cros_ec.c
> @@ -112,7 +112,11 @@ int cros_ec_register(struct cros_ec_device *ec_dev)
>
> mutex_init(&ec_dev->lock);
>
> - cros_ec_query_all(ec_dev);
> + err = cros_ec_query_all(ec_dev);
> + if (err) {
> + dev_err(dev, "Cannot identify the EC: error %d\n", err);
> + return err;
> + }
>
> if (ec_dev->irq) {
> err = request_threaded_irq(ec_dev->irq, NULL, ec_irq_thread,
> --
> 2.7.4
>
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web