The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "zhangpengjie (A)" <zhangpengjie2@huawei.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: <myungjoo.ham@samsung.com>, <kyungmin.park@samsung.com>,
	<cw00.choi@samsung.com>, <linux-pm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <zhanjie9@hisilicon.com>,
	<zhenglifeng1@huawei.com>, <lihuisong@huawei.com>,
	<yubowen8@huawei.com>, <linhongye@h-partners.com>,
	<linuxarm@huawei.com>
Subject: Re: [PATCH v2] PM / devfreq: use _visible attribute to replace create/remove_sysfs_files()
Date: Mon, 3 Nov 2025 10:29:13 +0800	[thread overview]
Message-ID: <68936aeb-20d7-429c-af5a-590b765f7351@huawei.com> (raw)
In-Reply-To: <20251031144157.00000e51@huawei.com>

On 10/31/2025 10:41 PM, Jonathan Cameron wrote:
> On Tue, 28 Oct 2025 10:24:58 +0800
> Pengjie Zhang <zhangpengjie2@huawei.com> wrote:
>
>>   static ssize_t polling_interval_store(struct device *dev,
>> @@ -1828,15 +1831,22 @@ static ssize_t polling_interval_store(struct device *dev,
>>   	unsigned int value;
>>   	int ret;
>>   
>> -	if (!df->governor)
>> +	mutex_lock(&devfreq_list_lock);
> As below I'd use guard() to simplify this.  Applies in various other places in this
> patch.
>>   
>> -/* Remove the specific sysfs files which depend on each governor. */
>> -static void remove_sysfs_files(struct devfreq *devfreq,
>> -				const struct devfreq_governor *gov)
>> +static bool gov_group_visible(struct kobject *kobj)
>>   {
>> -	if (IS_SUPPORTED_ATTR(gov->attrs, POLLING_INTERVAL))
>> -		sysfs_remove_file(&devfreq->dev.kobj,
>> -				&dev_attr_polling_interval.attr);
>> -	if (IS_SUPPORTED_ATTR(gov->attrs, TIMER))
>> -		sysfs_remove_file(&devfreq->dev.kobj, &dev_attr_timer.attr);
>> +	struct device *dev = kobj_to_dev(kobj);
>> +	struct devfreq *df;
>> +
>> +	if (!dev)
>> +		return false;
>> +
>> +	df = to_devfreq(dev);
>> +	if (!df)
>> +		return false;
> Isn't to_devfreq() just a container_of() wrapper?
> If that's the case it will always be there if dev is not NULL.
>
> As such I not seeing how this group is likely to ever be
> invisible.
>
Thank you for your review and comments.  I will address all your feedback

in the necessary revisions and submit the third version shortly.

Best regards,

Pengjie Zhang


      reply	other threads:[~2025-11-03  2:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28  2:24 [PATCH v2] PM / devfreq: use _visible attribute to replace create/remove_sysfs_files() Pengjie Zhang
2025-10-31 14:41 ` Jonathan Cameron
2025-11-03  2:29   ` zhangpengjie (A) [this message]

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=68936aeb-20d7-429c-af5a-590b765f7351@huawei.com \
    --to=zhangpengjie2@huawei.com \
    --cc=cw00.choi@samsung.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=kyungmin.park@samsung.com \
    --cc=lihuisong@huawei.com \
    --cc=linhongye@h-partners.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=yubowen8@huawei.com \
    --cc=zhanjie9@hisilicon.com \
    --cc=zhenglifeng1@huawei.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