From: Nicolas Boichat <drinkcat@chromium.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: gwendal@chromium.org, ejcaruso@chromium.org,
Olof Johansson <olof@lixom.net>,
linux-kernel@vger.kernel.org, groeck@chromium.org
Subject: [PATCH 0/3] mfd: cros_ec: Add debugfs directory to capture logs/panicinfo
Date: Tue, 23 Aug 2016 12:34:16 +0800 [thread overview]
Message-ID: <1471926859-21263-1-git-send-email-drinkcat@chromium.org> (raw)
This series makes it possible to capture EC console and panicinfo by reading
files in /sys/kernel/debug/cros_ec/*. This is very useful for debugging
purpose (e.g. when a user files a feedback on Chrome OS).
Eric Caruso (1):
mfd: cros_ec: add debugfs, console log file
Nicolas Boichat (2):
mfd: cros_ec: Add EC console read structures definitions
mfd: cros_ec: Add support for dumping panic information
drivers/platform/chrome/Makefile | 3 +-
drivers/platform/chrome/cros_ec_debugfs.c | 401 ++++++++++++++++++++++++++++++
drivers/platform/chrome/cros_ec_debugfs.h | 27 ++
drivers/platform/chrome/cros_ec_dev.c | 7 +
include/linux/mfd/cros_ec.h | 4 +
include/linux/mfd/cros_ec_commands.h | 21 +-
6 files changed, 461 insertions(+), 2 deletions(-)
create mode 100644 drivers/platform/chrome/cros_ec_debugfs.c
create mode 100644 drivers/platform/chrome/cros_ec_debugfs.h
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-08-23 4:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 4:34 Nicolas Boichat [this message]
2016-08-23 4:34 ` [PATCH 1/3] mfd: cros_ec: Add EC console read structures definitions Nicolas Boichat
2016-08-23 21:15 ` Guenter Roeck
2016-08-31 11:45 ` Lee Jones
2016-10-13 3:24 ` Nicolas Boichat
2016-10-13 18:06 ` Olof Johansson
2016-10-13 20:32 ` Nicolas Boichat
2016-08-23 4:34 ` [PATCH 2/3] mfd: cros_ec: add debugfs, console log file Nicolas Boichat
2016-08-23 21:17 ` Guenter Roeck
2016-08-31 11:45 ` Lee Jones
2017-02-22 21:49 ` Doug Anderson
2016-08-23 4:34 ` [PATCH 3/3] mfd: cros_ec: Add support for dumping panic information Nicolas Boichat
2016-08-23 21:19 ` Guenter Roeck
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=1471926859-21263-1-git-send-email-drinkcat@chromium.org \
--to=drinkcat@chromium.org \
--cc=ejcaruso@chromium.org \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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®