From: Saravana Kannan <skannan@codeaurora.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PM / devfreq: Restart previous governor if new governor fails to start
Date: Wed, 26 Oct 2016 12:17:24 -0700 [thread overview]
Message-ID: <58110144.9020909@codeaurora.org> (raw)
In-Reply-To: <581059C8.3000408@samsung.com>
On 10/26/2016 12:22 AM, Chanwoo Choi wrote:
> Hi,
>
> On 2016년 10월 26일 10:25, Saravana Kannan wrote:
>> If the new governor fails to start, switch back to old governor so that the
>> devfreq state is not left in some weird limbo.
>>
>> Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
>> ---
>> * Fixed typo in commit text
>> * Fixed potential NULL deref
>>
>> drivers/devfreq/devfreq.c | 9 +++++++--
>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
>> index bf3ea76..243253e 100644
>> --- a/drivers/devfreq/devfreq.c
>> +++ b/drivers/devfreq/devfreq.c
>> @@ -919,7 +919,7 @@ static ssize_t governor_store(struct device *dev, struct device_attribute *attr,
>> struct devfreq *df = to_devfreq(dev);
>> int ret;
>> char str_governor[DEVFREQ_NAME_LEN + 1];
>> - struct devfreq_governor *governor;
>> + const struct devfreq_governor *governor, *prev_gov;
>>
>> ret = sscanf(buf, "%" __stringify(DEVFREQ_NAME_LEN) "s", str_governor);
>> if (ret != 1)
>> @@ -944,12 +944,17 @@ static ssize_t governor_store(struct device *dev, struct device_attribute *attr,
>> goto out;
>> }
>> }
>> + prev_gov = df->governor;
>> df->governor = governor;
>> strncpy(df->governor_name, governor->name, DEVFREQ_NAME_LEN);
>> ret = df->governor->event_handler(df, DEVFREQ_GOV_START, NULL);
>> - if (ret)
>> + if (ret) {
>> dev_warn(dev, "%s: Governor %s not started(%d)\n",
>> __func__, df->governor->name, ret);
>> + df->governor = prev_gov;
>> + strncpy(df->governor_name, prev_gov->name, DEVFREQ_NAME_LEN);
>> + df->governor->event_handler(df, DEVFREQ_GOV_START, NULL);
>> + }
Sigh... looks like I added the changes to the index but forgot to commit
it before I sent the patch. Will send v3.
>> out:
>> mutex_unlock(&devfreq_list_lock);
>>
>>
>
> Looks good to me.
> But, how about using the 'prev_governor' instead of 'prev_gov'?
> because the variable name of current governor is 'governor' instead of 'gov'.
I was trying to avoid wrapping lines too much. But this doesn't cause
any additional wraps. Done.
>
> Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
>
Can you please review v3?
Thanks,
Saravana
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-10-26 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161026012617epcas1p4c8f51ab0efde871ed15c217f62ff522e@epcas1p4.samsung.com>
2016-10-26 1:25 ` [PATCH v2] PM / devfreq: Restart previous governor if new governor fails to start Saravana Kannan
2016-10-26 7:22 ` Chanwoo Choi
2016-10-26 19:17 ` Saravana Kannan [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=58110144.9020909@codeaurora.org \
--to=skannan@codeaurora.org \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.