public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Nicolas Boichat <drinkcat@chromium.org>
Cc: gwendal@chromium.org, ejcaruso@chromium.org,
	Olof Johansson <olof@lixom.net>,
	linux-kernel@vger.kernel.org, groeck@chromium.org
Subject: Re: [PATCH 1/3] mfd: cros_ec: Add EC console read structures definitions
Date: Wed, 31 Aug 2016 12:45:17 +0100	[thread overview]
Message-ID: <20160831114517.GC8649@dell> (raw)
In-Reply-To: <1471926859-21263-2-git-send-email-drinkcat@chromium.org>

On Tue, 23 Aug 2016, Nicolas Boichat wrote:

> ec_params_console_read_v1 is used to capture EC logs from kernel,
> and ec_params_get_cmd_versions_v1 is used to probe whether EC
> supports that command.
> 
> Signed-off-by: Nicolas Boichat <drinkcat@chromium.org>
> ---
>  include/linux/mfd/cros_ec_commands.h | 21 ++++++++++++++++++++-

Acked-by: Lee Jones <lee.jones@linaro.org>

I guess this will be taken through Olof's tree?

>  1 file changed, 20 insertions(+), 1 deletion(-)
> 
> diff --git a/include/linux/mfd/cros_ec_commands.h b/include/linux/mfd/cros_ec_commands.h
> index 7e7a8d4..74c84e82 100644
> --- a/include/linux/mfd/cros_ec_commands.h
> +++ b/include/linux/mfd/cros_ec_commands.h
> @@ -625,6 +625,10 @@ struct ec_params_get_cmd_versions {
>  	uint8_t cmd;      /* Command to check */
>  } __packed;
>  
> +struct ec_params_get_cmd_versions_v1 {
> +	uint16_t cmd;     /* Command to check */
> +} __packed;
> +
>  struct ec_response_get_cmd_versions {
>  	/*
>  	 * Mask of supported versions; use EC_VER_MASK() to compare with a
> @@ -2003,13 +2007,28 @@ struct ec_params_charge_control {
>  #define EC_CMD_CONSOLE_SNAPSHOT 0x97
>  
>  /*
> - * Read next chunk of data from saved snapshot.
> + * Read data from the saved snapshot. If the subcmd parameter is
> + * CONSOLE_READ_NEXT, this will return data starting from the beginning of
> + * the latest snapshot. If it is CONSOLE_READ_RECENT, it will start from the
> + * end of the previous snapshot.
> + *
> + * The params are only looked at in version >= 1 of this command. Prior
> + * versions will just default to CONSOLE_READ_NEXT behavior.
>   *
>   * Response is null-terminated string.  Empty string, if there is no more
>   * remaining output.
>   */
>  #define EC_CMD_CONSOLE_READ 0x98
>  
> +enum ec_console_read_subcmd {
> +	CONSOLE_READ_NEXT = 0,
> +	CONSOLE_READ_RECENT
> +};
> +
> +struct ec_params_console_read_v1 {
> +	uint8_t subcmd; /* enum ec_console_read_subcmd */
> +} __packed;
> +
>  /*****************************************************************************/
>  
>  /*

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2016-08-31 11:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23  4:34 [PATCH 0/3] mfd: cros_ec: Add debugfs directory to capture logs/panicinfo Nicolas Boichat
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 [this message]
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=20160831114517.GC8649@dell \
    --to=lee.jones@linaro.org \
    --cc=drinkcat@chromium.org \
    --cc=ejcaruso@chromium.org \
    --cc=groeck@chromium.org \
    --cc=gwendal@chromium.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