From: Peter Hilber <peter.hilber@opensynergy.com>
To: Cristian Marussi <cristian.marussi@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: sudeep.holla@arm.com, james.quinlan@broadcom.com,
Jonathan.Cameron@Huawei.com, f.fainelli@gmail.com,
etienne.carriere@linaro.org, vincent.guittot@linaro.org,
souvik.chakravarty@arm.com
Subject: Re: [PATCH 15/22] firmware: arm_scmi: Add SCMIv3.1 SENSOR_AXIS_NAME_GET support
Date: Thu, 2 Jun 2022 16:25:45 +0200 [thread overview]
Message-ID: <d523569d-2470-3e01-c407-d6e723c7d0c1@opensynergy.com> (raw)
In-Reply-To: <20220330150551.2573938-16-cristian.marussi@arm.com>
On 30.03.22 17:05, Cristian Marussi wrote:
> Add support for SCMIv3.1 SENSOR_AXIS_NAME_GET multi-part command using the
> common iterator protocol helpers.
>
> Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> ---
> drivers/firmware/arm_scmi/sensors.c | 82 ++++++++++++++++++++++++++---
> 1 file changed, 76 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/firmware/arm_scmi/sensors.c b/drivers/firmware/arm_scmi/sensors.c
> index e1a94463d7d8..21e0ce89b153 100644
> --- a/drivers/firmware/arm_scmi/sensors.c
> +++ b/drivers/firmware/arm_scmi/sensors.c
> @@ -28,6 +28,7 @@ enum scmi_sensor_protocol_cmd {
> SENSOR_CONFIG_SET = 0xA,
> SENSOR_CONTINUOUS_UPDATE_NOTIFY = 0xB,
> SENSOR_NAME_GET = 0xC,
> + SENSOR_AXIS_NAME_GET = 0xD,
> };
>
> struct scmi_msg_resp_sensor_attributes {
> @@ -117,13 +118,22 @@ struct scmi_msg_resp_sensor_axis_description {
> struct scmi_axis_descriptor {
> __le32 id;
> __le32 attributes_low;
> +#define SUPPORTS_EXTENDED_AXIS_NAMES(x) FIELD_GET(BIT(9), (x))
Hi Cristian,
I saw this patch is probably going into v5.19 already, so I'm a bit late, but I
wanted to point out a compatibility issue, and a small error handling issue.
Please see below.
Best regards,
Peter
> __le32 attributes_high;
> - u8 name[SCMI_MAX_STR_SIZE];
> + u8 name[SCMI_SHORT_NAME_MAX_SIZE];
> __le32 resolution;
> struct scmi_msg_resp_attrs attrs;
> } desc[];
> };
>
> +struct scmi_msg_resp_sensor_axis_names_description {
> + __le32 num_axis_flags;
> + struct scmi_sensor_axis_name_descriptor {
> + __le32 axis_id;
> + u8 name[SCMI_MAX_STR_SIZE];
> + } desc[];
> +};
> +
> /* Base scmi_axis_descriptor size excluding extended attrs after name */
> #define SCMI_MSG_RESP_AXIS_DESCR_BASE_SZ 28
>
> @@ -393,7 +403,6 @@ iter_axes_desc_process_response(const struct scmi_protocol_handle *ph,
> a->extended_attrs = SUPPORTS_EXTEND_ATTRS(attrl);
>
> attrh = le32_to_cpu(adesc->attributes_high);
> -
> a->scale = S32_EXT(SENSOR_SCALE(attrh));
> a->type = SENSOR_TYPE(attrh);
> strscpy(a->name, adesc->name, SCMI_MAX_STR_SIZE);
The strscpy() call should probably change the size parameter to
SCMI_SHORT_NAME_MAX_SIZE.
> @@ -408,15 +417,69 @@ iter_axes_desc_process_response(const struct scmi_protocol_handle *ph,
> scmi_parse_range_attrs(&a->attrs, &adesc->attrs);
> dsize += sizeof(adesc->attrs);
> }
> -
> st->priv = ((u8 *)adesc + dsize);
>
> return 0;
> }
>
> +static int
> +iter_axes_extended_name_update_state(struct scmi_iterator_state *st,
> + const void *response, void *priv)
> +{
> + u32 flags;
> + const struct scmi_msg_resp_sensor_axis_names_description *r = response;
> +
> + flags = le32_to_cpu(r->num_axis_flags);
> + st->num_returned = NUM_AXIS_RETURNED(flags);
> + st->num_remaining = NUM_AXIS_REMAINING(flags);
> + st->priv = (void *)&r->desc[0];
> +
> + return 0;
> +}
> +
> +static int
> +iter_axes_extended_name_process_response(const struct scmi_protocol_handle *ph,
> + const void *response,
> + struct scmi_iterator_state *st,
> + void *priv)
> +{
> + struct scmi_sensor_axis_info *a;
> + const struct scmi_sensor_info *s = priv;
> + struct scmi_sensor_axis_name_descriptor *adesc = st->priv;
> +
> + a = &s->axis[st->desc_index + st->loop_idx];
> + strscpy(a->name, adesc->name, SCMI_MAX_STR_SIZE);
> + st->priv = ++adesc;
> +
> + return 0;
> +}
> +
> +static int
> +scmi_sensor_axis_extended_names_get(const struct scmi_protocol_handle *ph,
> + struct scmi_sensor_info *s)
> +{
> + void *iter;
> + struct scmi_msg_sensor_axis_description_get *msg;
> + struct scmi_iterator_ops ops = {
> + .prepare_message = iter_axes_desc_prepare_message,
> + .update_state = iter_axes_extended_name_update_state,
> + .process_response = iter_axes_extended_name_process_response,
> + };
> +
> + iter = ph->hops->iter_response_init(ph, &ops, s->num_axis,
> + SENSOR_AXIS_NAME_GET,
> + sizeof(*msg), s);
> + if (IS_ERR(iter))
> + return PTR_ERR(iter);
> +
> + return ph->hops->iter_response_run(iter);
> +}
> +
> static int scmi_sensor_axis_description(const struct scmi_protocol_handle *ph,
> - struct scmi_sensor_info *s)
> + struct scmi_sensor_info *s,
> + u32 version)
> {
> + int ret;
> void *iter;
> struct scmi_msg_sensor_axis_description_get *msg;
> struct scmi_iterator_ops ops = {
> @@ -436,7 +499,14 @@ static int scmi_sensor_axis_description(const struct scmi_protocol_handle *ph,
> if (IS_ERR(iter))
> return PTR_ERR(iter);
>
> - return ph->hops->iter_response_run(iter);
> + ret = ph->hops->iter_response_run(iter);
> + if (ret)
> + return ret;
> +
> + if (PROTOCOL_REV_MAJOR(version) >= 0x3)
> + ret = scmi_sensor_axis_extended_names_get(ph, s);
From the SCMI v3.1 spec, I understood that the reading of the extended axis
name should be conditional on the bit checked by SUPPORTS_EXTENDED_AXIS_NAMES()
(the `Extended axis name' bit). Yet, the implementation doesn't use the macro,
and instead decides whether to issue SENSOR_AXIS_NAME_GET depending on the
(sensor management) protocol version being at least v3.0. But, per the spec, it
would be permissible for a v3.0 protocol to not support SENSOR_AXIS_NAME_GET at
all. Is my understanding correct?
> +
> + return ret;
> }
>
> static void iter_sens_descr_prepare_message(void *message,
> @@ -559,7 +629,7 @@ iter_sens_descr_process_response(const struct scmi_protocol_handle *ph,
> }
>
> if (s->num_axis > 0)
> - ret = scmi_sensor_axis_description(ph, s);
> + ret = scmi_sensor_axis_description(ph, s, si->version);
>
> st->priv = ((u8 *)sdesc + dsize);
>
next prev parent reply other threads:[~2022-06-02 14:30 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 15:05 [PATCH 00/22] SCMIv3.1 Miscellaneous changes Cristian Marussi
2022-03-30 15:05 ` [PATCH 01/22] firmware: arm_scmi: Fix sorting of retrieved clock rates Cristian Marussi
2022-03-30 15:05 ` [PATCH 02/22] firmware: arm_scmi: Make protocols init fail on basic errors Cristian Marussi
2022-04-26 15:35 ` Sudeep Holla
2022-04-26 16:25 ` Cristian Marussi
2022-04-28 10:25 ` Sudeep Holla
2022-04-28 12:07 ` Cristian Marussi
2022-03-30 15:05 ` [PATCH 03/22] firmware: arm_scmi: Fix Base list protocols enumeration Cristian Marussi
2022-03-30 15:05 ` [PATCH 04/22] firmware: arm_scmi: Validate BASE_DISCOVER_LIST_PROTOCOLS reply Cristian Marussi
2022-04-28 10:07 ` Sudeep Holla
2022-04-28 13:45 ` Cristian Marussi
2022-04-28 13:55 ` Sudeep Holla
2022-04-28 14:03 ` Cristian Marussi
2022-03-30 15:05 ` [PATCH 05/22] firmware: arm_scmi: Dynamically allocate protocols array Cristian Marussi
2022-04-28 10:27 ` Sudeep Holla
2022-03-30 15:05 ` [PATCH 06/22] firmware: arm_scmi: Make name_get operations return a const Cristian Marussi
2022-03-30 15:05 ` [PATCH 07/22] firmware: arm_scmi: Check CLOCK_RATE_SET_COMPLETE async reply Cristian Marussi
2022-03-30 15:05 ` [PATCH 08/22] firmware: arm_scmi: Remove unneeded NULL termination of clk name Cristian Marussi
2022-03-30 15:05 ` [PATCH 09/22] firmware: arm_scmi: Split protocol specific definitions in a dedicated header Cristian Marussi
2022-03-30 15:05 ` [PATCH 10/22] firmware: arm_scmi: Introduce a common SCMIv3.1 .extended_name_get helper Cristian Marussi
2022-03-30 15:05 ` [PATCH 11/22] firmware: arm_scmi: Add SCMIv3.1 extended names protocols support Cristian Marussi
2022-06-15 3:45 ` Florian Fainelli
2022-06-15 8:17 ` Cristian Marussi
2022-06-15 9:40 ` Cristian Marussi
2022-06-15 16:10 ` Florian Fainelli
2022-06-15 16:29 ` Cristian Marussi
2022-06-15 17:19 ` Florian Fainelli
2022-06-15 17:32 ` Cristian Marussi
2022-06-15 22:58 ` Florian Fainelli
2022-03-30 15:05 ` [PATCH 12/22] firmware: arm_scmi: Parse clock_enable_latency conditionally Cristian Marussi
2022-03-30 15:05 ` [PATCH 13/22] firmware: arm_scmi: Add iterators for multi-part commands Cristian Marussi
2022-03-30 15:05 ` [PATCH 14/22] firmware: arm_scmi: Use common iterators in Sensor protocol Cristian Marussi
2022-03-30 15:05 ` [PATCH 15/22] firmware: arm_scmi: Add SCMIv3.1 SENSOR_AXIS_NAME_GET support Cristian Marussi
2022-06-02 14:25 ` Peter Hilber [this message]
2022-06-06 8:18 ` Cristian Marussi
2022-06-08 8:40 ` Peter Hilber
2022-06-08 8:49 ` Cristian Marussi
2022-03-30 15:05 ` [PATCH 16/22] firmware: arm_scmi: Use common iterators in Clock protocol Cristian Marussi
2022-03-30 15:05 ` [PATCH 17/22] firmware: arm_scmi: Use common iterators in Voltage protocol Cristian Marussi
2022-03-30 15:05 ` [PATCH 18/22] firmware: arm_scmi: Use common iterators in Perf protocol Cristian Marussi
2022-03-30 15:05 ` [PATCH 19/22] firmware: arm_scmi: Add SCMIv3.1 Clock notifications Cristian Marussi
2022-03-30 15:05 ` [PATCH 20/22] firmware: arm_scmi: Add SCMIv3.1 VOLTAGE_LEVEL_SET_COMPLETE Cristian Marussi
2022-03-30 15:05 ` [PATCH 21/22] firmware: arm_scmi: Add SCMI v3.1 Perf power-cost in microwatts Cristian Marussi
2022-03-30 16:46 ` Lukasz Luba
2022-03-30 15:05 ` [PATCH 22/22] firmware: arm_scmi: Add SCMIv3.1 PERFORMANCE_LIMITS_SET checks Cristian Marussi
2022-04-28 13:13 ` Sudeep Holla
2022-04-28 13:49 ` Cristian Marussi
2022-04-28 13:52 ` Sudeep Holla
2022-04-28 13:46 ` [PATCH 00/22] SCMIv3.1 Miscellaneous changes Sudeep Holla
2022-05-03 8:03 ` 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=d523569d-2470-3e01-c407-d6e723c7d0c1@opensynergy.com \
--to=peter.hilber@opensynergy.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=cristian.marussi@arm.com \
--cc=etienne.carriere@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=souvik.chakravarty@arm.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
/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®