linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org,
	sudeep.holla@arm.com, james.quinlan@broadcom.com,
	f.fainelli@gmail.com, vincent.guittot@linaro.org,
	etienne.carriere@st.com, peng.fan@oss.nxp.com,
	michal.simek@amd.com, quic_sibis@quicinc.com, d-gole@ti.com,
	souvik.chakravarty@arm.com
Subject: Re: [RFC PATCH 4/7] firmware: arm_scmi: Add System Telemetry driver
Date: Wed, 25 Jun 2025 15:11:50 +0100	[thread overview]
Message-ID: <aFwDprdWI0mtglwe@pluto> (raw)
In-Reply-To: <f2c0a0d9-6a1b-42c7-a180-e04e357dbbb5@suswa.mountain>

On Sat, Jun 21, 2025 at 12:27:03AM +0300, Dan Carpenter wrote:
> On Fri, Jun 20, 2025 at 08:28:10PM +0100, Cristian Marussi wrote:
> > +//TODO Review available interval show
> > +#define BUF_SZ	1024
> > +static inline ssize_t
> > +__available_update_show(char *buf,
> > +			const struct scmi_telemetry_update_interval *intervals)
> > +{
> > +	int len = 0, num_intervals = intervals->num;
> > +	char available[BUF_SZ];
> > +
> > +	for (int i = 0; i < num_intervals; i++) {
> > +		len += scnprintf(available + len, BUF_SZ - len, "%u ",
> > +				 intervals->update_intervals[i]);
> > +	}
> > +
> > +	available[len - 1] = '\0';
> 
> No need.  scnprintf() will already have put a NUL terminator there.
> Unless num_intervals <= 0 in which case this will corrupt memory.
> 

Yes, all of this routine has to be really reworked to avoid on the stack
allocation too...

> > +
> > +	return sysfs_emit(buf, "%s\n", available);
> > +}
> 
> [ snip ]
> 
> > +static int scmi_telemetry_groups_initialize(struct device *dev,
> > +					    struct scmi_tlm_instance *ti)
> > +{
> > +	int ret;
> > +
> > +	if (ti->info->num_groups == 0)
> > +		return 0;
> > +
> > +	ret = scmi_telemetry_dev_register(&ti->groups_dev, &ti->dev, "groups");
> > +	if (ret)
> > +		return ret;
> > +
> > +	for (int i = 0; i < ti->info->num_groups; i++) {
> > +		const struct scmi_telemetry_group *grp = &ti->info->des_groups[i];
> > +		struct scmi_tlm_grp_dev *gdev;
> > +		char name[16];
> > +
> > +		gdev = devm_kzalloc(dev, sizeof(*gdev), GFP_KERNEL);
> > +		if (!gdev) {
> > +			ret = -ENOMEM;
> > +			goto err;
> > +		}
> > +
> > +		gdev->tsp = ti->tsp;
> > +		gdev->grp = grp;
> > +		gdev->dev.groups = scmi_grp_groups;
> > +
> > +		snprintf(name, 8, "%d", grp->id);
> 
> s/8/sizeof(name)/?

indeed...

> 
> > +		ret = scmi_telemetry_dev_register(&gdev->dev,
> > +						  &ti->groups_dev, name);
> > +		if (ret)
> > +			goto err;
> > +
> > +		if (ti->info->per_group_config_support) {
> > +			sysfs_add_file_to_group(&gdev->dev.kobj,
> > +						&dev_attr_grp_current_update.attr,
> > +						NULL);
> > +			sysfs_add_file_to_group(&gdev->dev.kobj,
> > +						&dev_attr_grp_intervals_discrete.attr,
> > +						NULL);
> > +			sysfs_add_file_to_group(&gdev->dev.kobj,
> > +						&dev_attr_grp_available_intervals.attr,
> > +						NULL);
> > +		}
> > +	}
> > +
> > +	dev_info(dev, "Found %d Telemetry GROUPS resources.\n",
> > +		 ti->info->num_groups);
> > +
> > +	return 0;
> > +
> > +err:
> > +	scmi_telemetry_dev_unregister(&ti->groups_dev);
> > +
> > +	return ret;
> > +}
> > +
> > +static int scmi_telemetry_des_initialize(struct device *dev,
> > +					 struct scmi_tlm_instance *ti)
> > +{
> > +	int ret;
> > +
> > +	ret = scmi_telemetry_dev_register(&ti->des_dev, &ti->dev, "des");
> > +	if (ret)
> > +		return ret;
> > +
> > +	for (int i = 0; i < ti->info->num_de; i++) {
> > +		const struct scmi_telemetry_de *de = ti->info->des[i];
> > +		struct scmi_tlm_de_dev *tdev;
> > +		char name[16];
> > +
> > +		tdev = devm_kzalloc(dev, sizeof(*tdev), GFP_KERNEL);
> > +		if (!tdev) {
> > +			ret = -ENOMEM;
> > +			goto err;
> > +		}
> > +
> > +		tdev->tsp = ti->tsp;
> > +		tdev->de = de;
> > +		tdev->dev.groups = scmi_des_groups;
> > +
> > +		/*XXX What about of ID/name digits-length used ? */
> > +		snprintf(name, 8, "0x%04X", de->id);
> 
> s/8/sizeof(name)/?
> 

yes.

> regards,
> dan carpenter
>

Thanks,
Cristian

  reply	other threads:[~2025-06-25 14:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 19:28 [RFC PATCH 0/7] Introduce SCMI Telemetry support Cristian Marussi
2025-06-20 19:28 ` [RFC PATCH 1/7] firmware: arm_scmi: Define a common SCMI_MAX_PROTOCOLS value Cristian Marussi
2025-06-24  3:13   ` Peng Fan
2025-06-25 13:59     ` Cristian Marussi
2025-06-20 19:28 ` [RFC PATCH 2/7] firmware: arm_scmi: Allow protocols to register for notifications Cristian Marussi
2025-06-20 19:28 ` [RFC PATCH 3/7] firmware: arm_scmi: Add Telemetry protocol support Cristian Marussi
2025-06-20 20:46   ` Dan Carpenter
2025-06-25 14:02     ` Cristian Marussi
2025-06-25 14:04     ` Cristian Marussi
2025-06-20 21:01   ` Dan Carpenter
2025-06-25 14:04     ` Cristian Marussi
2025-06-20 19:28 ` [RFC PATCH 4/7] firmware: arm_scmi: Add System Telemetry driver Cristian Marussi
2025-06-20 21:27   ` Dan Carpenter
2025-06-25 14:11     ` Cristian Marussi [this message]
2025-06-20 19:28 ` [RFC PATCH 5/7] firmware: arm_scmi: Add System Telemetry chardev/ioctls API Cristian Marussi
2025-06-20 21:51   ` Dan Carpenter
2025-06-25 14:14     ` Cristian Marussi
2025-06-20 19:28 ` [RFC PATCH 6/7] include: trace: Add Telemetry trace events Cristian Marussi
2025-06-20 19:28 ` [RFC PATCH 7/7] firmware: arm_scmi: Use new Telemetry traces Cristian Marussi
2025-06-24 10:22 ` [RFC PATCH 0/7] Introduce SCMI Telemetry support Dhruva Gole
2025-06-25 14:53   ` Cristian Marussi

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=aFwDprdWI0mtglwe@pluto \
    --to=cristian.marussi@arm.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=d-gole@ti.com \
    --cc=dan.carpenter@linaro.org \
    --cc=etienne.carriere@st.com \
    --cc=f.fainelli@gmail.com \
    --cc=james.quinlan@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=quic_sibis@quicinc.com \
    --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;
as well as URLs for NNTP newsgroup(s).