From: Bart Van Assche <bvanassche@acm.org>
To: Huan Tang <tanghuan@vivo.com>,
alim.akhtar@samsung.com, avri.altman@wdc.com,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, peter.wang@mediatek.com,
manivannan.sadhasivam@linaro.org, quic_nguyenb@quicinc.com,
luhongfei@vivo.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: opensource.kernel@vivo.com, Wenxing Cheng <wenxing.cheng@vivo.com>
Subject: Re: [PATCH v2] ufs: core: Add HID support
Date: Wed, 14 May 2025 14:04:56 -0700 [thread overview]
Message-ID: <88718b2f-0583-4444-8bf0-7ecf9a45329c@acm.org> (raw)
In-Reply-To: <20250512131519.138-1-tanghuan@vivo.com>
On 5/12/25 6:15 AM, Huan Tang wrote:
> +What: /sys/bus/platform/drivers/ufshcd/*/ufs_hid/hid_analysis_trigger
> +What: /sys/bus/platform/devices/*.ufs/ufs_hid/hid_analysis_trigger
> +Date: April 2025
> +Contact: Huan Tang <tanghuan@vivo.com>
> +Description:
> + The host can enable or disable HID analysis operation.
> +
> + ======= =========================================
> + disable disable HID analysis operation
> + enable enable HID analysis operation
> + ======= =========================================
> +
> + The file is write only.
All HID sysfs attributes occur in the "ufs_hid" directory and have a
"hid_" prefix. That's two times "hid". Please remove the "hid_" prefix
from the sysfs attribute names since it is redundant.
> +static struct attribute *ufs_sysfs_ufs_hid[] = {
> + &dev_attr_hid_analysis_trigger.attr,
> + &dev_attr_hid_defrag_trigger.attr,
> + &dev_attr_hid_fragmented_size.attr,
> + &dev_attr_hid_defrag_size.attr,
> + &dev_attr_hid_progress_ratio.attr,
> + &dev_attr_hid_state.attr,
> + NULL,
> +};
> +
> +static const struct attribute_group ufs_sysfs_ufs_hid_group = {
> + .name = "ufs_hid",
> + .attrs = ufs_sysfs_ufs_hid,
> +};
Isn't the prefix "ufs_" in "ufs_hid" redundant since this sysfs group
occurs under a UFS host controller directory?
Regarding the name of this sysfs group, "ufs" occurs twice in that
name (ufs_sysfs_ufs_hid_group). Please make sure that "ufs" only occurs
once in that sysfs group name.
> #define UFS_LUN_DESC_PARAM(_pname, _puname, _duname, _size) \
> static ssize_t _pname##_show(struct device *dev, \
> struct device_attribute *attr, char *buf) \
> @@ -1898,6 +2079,7 @@ const struct attribute_group ufs_sysfs_lun_attributes_group = {
>
> void ufs_sysfs_add_nodes(struct device *dev)
> {
> + struct ufs_hba *hba = dev_get_drvdata(dev);
> int ret;
>
> ret = sysfs_create_groups(&dev->kobj, ufs_sysfs_groups);
> @@ -1905,9 +2087,22 @@ void ufs_sysfs_add_nodes(struct device *dev)
> dev_err(dev,
> "%s: sysfs groups creation failed (err = %d)\n",
> __func__, ret);
> +
> + if (hba->dev_info.hid_sup) {
> + ret = sysfs_create_group(&dev->kobj, &ufs_sysfs_ufs_hid_group);
> + if (ret)
> + dev_err(dev,
> + "%s: sysfs ufs_hid group creation failed (err = %d)\n",
> + __func__, ret);
> + }
> }
Please merge ufs_sysfs_ufs_hid_group into ufs_sysfs_groups, remove the
new sysfs_create_group() call and add a visibility callback in
ufs_sysfs_ufs_hid_group that only makes the attributes in this group
visible if hba->dev_info.hid_sup == true.
Otherwise this patch looks good to me.
Thanks,
Bart.
next prev parent reply other threads:[~2025-05-14 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 13:15 Huan Tang
2025-05-14 21:04 ` Bart Van Assche [this message]
2025-05-19 2:38 ` Huan Tang
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=88718b2f-0583-4444-8bf0-7ecf9a45329c@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luhongfei@vivo.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=opensource.kernel@vivo.com \
--cc=peter.wang@mediatek.com \
--cc=quic_nguyenb@quicinc.com \
--cc=tanghuan@vivo.com \
--cc=wenxing.cheng@vivo.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
all inboxes | Powered by JetHome®