linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, james.quinlan@broadcom.com,
	Jonathan.Cameron@Huawei.com, dave.martin@arm.com,
	lukasz.luba@arm.com
Subject: Re: [PATCH v8 9/9] firmware: arm_scmi: Add Base notifications support
Date: Mon, 8 Jun 2020 18:02:39 +0100	[thread overview]
Message-ID: <20200608170239.GA13622@bogus> (raw)
In-Reply-To: <20200520081118.54897-10-cristian.marussi@arm.com>

On Wed, May 20, 2020 at 09:11:18AM +0100, Cristian Marussi wrote:
> Make SCMI Base protocol register with the notification core.
>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> ---
> V6 --> V7
> - fixed report.timestamp type
> - fix max_payld_sz initialization
> - fix report layout and initialization
> - expose SCMI_EVENT_ in linux/scmi_protocol.h
> V5 --> V6
> - added handle argument to fill_custom_report()
> V4 --> V5
> - fixed unsual return construct
> V3 --> V4
> - scmi_event field renamed
> V2 --> V3
> - added handle awareness
> V1 --> V2
> - simplified .set_notify_enabled() implementation moving the ALL_SRCIDs
>   logic out of protocol. ALL_SRCIDs logic is now in charge of the
>   notification core, together with proper reference counting of enables
> - switched to devres protocol-registration
> ---
>  drivers/firmware/arm_scmi/base.c | 118 +++++++++++++++++++++++++++++--
>  include/linux/scmi_protocol.h    |   9 +++
>  2 files changed, 123 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/firmware/arm_scmi/base.c b/drivers/firmware/arm_scmi/base.c
> index ce7d9203e41b..dcb098d8d823 100644
> --- a/drivers/firmware/arm_scmi/base.c
> +++ b/drivers/firmware/arm_scmi/base.c
> @@ -5,7 +5,13 @@
>   * Copyright (C) 2018 ARM Ltd.
>   */
>
> +#include <linux/scmi_protocol.h>
> +
>  #include "common.h"
> +#include "notify.h"
> +
> +#define SCMI_BASE_NUM_SOURCES		1
> +#define SCMI_BASE_MAX_CMD_ERR_COUNT	1024
>

I am not sure of this, see below.

>  enum scmi_base_protocol_cmd {
>  	BASE_DISCOVER_VENDOR = 0x3,
> @@ -19,16 +25,25 @@ enum scmi_base_protocol_cmd {
>  	BASE_RESET_AGENT_CONFIGURATION = 0xb,
>  };
>
> -enum scmi_base_protocol_notify {
> -	BASE_ERROR_EVENT = 0x0,
> -};
> -
>  struct scmi_msg_resp_base_attributes {
>  	u8 num_protocols;
>  	u8 num_agents;
>  	__le16 reserved;
>  };
>
> +struct scmi_msg_base_error_notify {
> +	__le32 event_control;
> +#define BASE_TP_NOTIFY_ALL	BIT(0)
> +};
> +
> +struct scmi_base_error_notify_payld {
> +	__le32 agent_id;
> +	__le32 error_status;
> +#define IS_FATAL_ERROR(x)	((x) & BIT(31))
> +#define ERROR_CMD_COUNT(x)	FIELD_GET(GENMASK(9, 0), (x))
> +	__le64 msg_reports[SCMI_BASE_MAX_CMD_ERR_COUNT];

This entire payload needs to fit in shmem and having huge shmem just
for this sounds not so good to me. If this can be large, it needs to
be iterated multiple times to get the full log.

> +};
> +
>  /**
>   * scmi_base_attributes_get() - gets the implementation details
>   *	that are associated with the base protocol.
> @@ -222,6 +237,95 @@ static int scmi_base_discover_agent_get(const struct scmi_handle *handle,
>  	return ret;
>  }
>
> +static int scmi_base_error_notify(const struct scmi_handle *handle, bool enable)
> +{
> +	int ret;
> +	u32 evt_cntl = enable ? BASE_TP_NOTIFY_ALL : 0;
> +	struct scmi_xfer *t;
> +	struct scmi_msg_base_error_notify *cfg;
> +
> +	ret = scmi_xfer_get_init(handle, BASE_NOTIFY_ERRORS,
> +				 SCMI_PROTOCOL_BASE, sizeof(*cfg), 0, &t);
> +	if (ret)
> +		return ret;
> +
> +	cfg = t->tx.buf;
> +	cfg->event_control = cpu_to_le32(evt_cntl);
> +
> +	ret = scmi_do_xfer(handle, t);
> +
> +	scmi_xfer_put(handle, t);
> +	return ret;
> +}
> +
> +static bool scmi_base_set_notify_enabled(const struct scmi_handle *handle,
> +					 u8 evt_id, u32 src_id, bool enable)
> +{
> +	int ret;
> +
> +	ret = scmi_base_error_notify(handle, enable);
> +	if (ret)
> +		pr_warn("SCMI Notifications - Proto:%X - FAIL_ENABLED - evt[%X] ret:%d\n",
> +			SCMI_PROTOCOL_BASE, evt_id, ret);
> +

I would make all these debug as they are not fatal. The users can decide
if they are fatal and log it appropriately.

> +	return !ret;
> +}
> +
> +static void *scmi_base_fill_custom_report(const struct scmi_handle *handle,
> +					  u8 evt_id, u64 timestamp,
> +					  const void *payld, size_t payld_sz,
> +					  void *report, u32 *src_id)
> +{
> +	void *rep = NULL;
> +
> +	switch (evt_id) {
> +	case SCMI_EVENT_BASE_ERROR_EVENT:

Drop switch for now, just check for evt_id to be SCMI_EVENT_BASE_ERROR_EVENT.

> +	{
> +		int i;
> +		const struct scmi_base_error_notify_payld *p = payld;
> +		struct scmi_base_error_report *r = report;
> +
> +		/*
> +		 * BaseError notification payload is variable in size but
> +		 * up to a maximum length determined by the struct ponted by p.
> +		 * Instead payld_sz is the effective length of this notification
> +		 * payload so cannot be greater of the maximum allowed size as
> +		 * pointed by p.
> +		 */
> +		if (sizeof(*p) < payld_sz)
> +			break;
> +
> +		r->timestamp = timestamp;
> +		r->agent_id = le32_to_cpu(p->agent_id);
> +		r->fatal = IS_FATAL_ERROR(le32_to_cpu(p->error_status));
> +		r->cmd_count = ERROR_CMD_COUNT(le32_to_cpu(p->error_status));
> +		for (i = 0; i < r->cmd_count; i++)
> +			r->reports[i] = le64_to_cpu(p->msg_reports[i]);
> +		*src_id = 0;
> +		rep = r;
> +		break;
> +	}
> +	default:
> +		break;
> +	}
> +
> +	return rep;
> +}
> +
> +static const struct scmi_event base_events[] = {
> +	{
> +		.id = SCMI_EVENT_BASE_ERROR_EVENT,
> +		.max_payld_sz = sizeof(struct scmi_base_error_notify_payld),
> +		.max_report_sz = sizeof(struct scmi_base_error_report) +
> +				  SCMI_BASE_MAX_CMD_ERR_COUNT * sizeof(u64),
> +	},
> +};
> +
> +static const struct scmi_protocol_event_ops base_event_ops = {
> +	.set_notify_enabled = scmi_base_set_notify_enabled,
> +	.fill_custom_report = scmi_base_fill_custom_report,
> +};
> +
>  int scmi_base_protocol_init(struct scmi_handle *h)
>  {
>  	int id, ret;
> @@ -256,6 +360,12 @@ int scmi_base_protocol_init(struct scmi_handle *h)
>  	dev_dbg(dev, "Found %d protocol(s) %d agent(s)\n", rev->num_protocols,
>  		rev->num_agents);
>
> +	scmi_register_protocol_events(handle,
> +				      SCMI_PROTOCOL_BASE, (4 * PAGE_SIZE),

The size 4 * PAGE_SZ is not clear. For me this can't be more that
max_msg_size.

The comments in this patch applies to last 5 patches(all protocols basically)

--
Regards,
Sudeep

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-06-08 17:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20  8:11 [PATCH v8 0/9] SCMI Notifications Core Support Cristian Marussi
2020-05-20  8:11 ` [PATCH v8 1/9] firmware: arm_scmi: Add notification protocol-registration Cristian Marussi
2020-06-08 17:02   ` Sudeep Holla
2020-06-16 19:58     ` Cristian Marussi
2020-05-20  8:11 ` [PATCH v8 2/9] firmware: arm_scmi: Add notification callbacks-registration Cristian Marussi
2020-06-08 17:03   ` Sudeep Holla
2020-06-17 23:20     ` Cristian Marussi
2020-05-20  8:11 ` [PATCH v8 3/9] firmware: arm_scmi: Add notification dispatch and delivery Cristian Marussi
2020-06-08 17:03   ` Sudeep Holla
2020-06-17 23:31     ` Cristian Marussi
2020-06-18  8:37       ` Lukasz Luba
2020-05-20  8:11 ` [PATCH v8 4/9] firmware: arm_scmi: Enable notification core Cristian Marussi
2020-05-20  8:11 ` [PATCH v8 5/9] firmware: arm_scmi: Add Power notifications support Cristian Marussi
2020-05-20  8:11 ` [PATCH v8 6/9] firmware: arm_scmi: Add Perf " Cristian Marussi
2020-05-20  8:11 ` [PATCH v8 7/9] firmware: arm_scmi: Add Sensor " Cristian Marussi
2020-05-20  8:11 ` [PATCH v8 8/9] firmware: arm_scmi: Add Reset " Cristian Marussi
2020-05-20  8:11 ` [PATCH v8 9/9] firmware: arm_scmi: Add Base " Cristian Marussi
2020-06-08 17:02   ` Sudeep Holla [this message]
2020-06-18 17:24     ` Cristian Marussi
2020-06-08 17:05 ` [PATCH v8 0/9] SCMI Notifications Core Support Sudeep Holla

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=20200608170239.GA13622@bogus \
    --to=sudeep.holla@arm.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=cristian.marussi@arm.com \
    --cc=dave.martin@arm.com \
    --cc=james.quinlan@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz.luba@arm.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).