From: noman pouigt <variksla@gmail.com>
To: linux-pm@vger.kernel.org, myungjoo.ham@samsung.com,
kyungmin.park@samsung.com, linux-kernel@vger.kernel.org
Subject: Re: devfreq relation with pm qos
Date: Mon, 9 Jul 2018 14:34:53 -0700 [thread overview]
Message-ID: <CAES_P+_GTRcFya=N20+b+U=HOpv9gcpYkfJW_gU_i_2pH2hmMA@mail.gmail.com> (raw)
In-Reply-To: <CAES_P+_k=fz3yMnVZni2hEnfSujctnT33zoN9-KsBLBeQaG_sA@mail.gmail.com>
+ dev freq maintainters.
On Mon, Jul 9, 2018 at 3:37 AM, noman pouigt <variksla@gmail.com> wrote:
> folks,
>
> I am trying to figure out the relationship between PM QOS
> with devfreq framework. I see this thread[1] where MyungJoo
> talks about QOS and devfreq but that control is through
> sysfs but I don't see any relation of pm qos (kernel/power/qos.c)
> with devfreq directly as devfreq is not calling any of the QOS
> api's. Is this intended?
>
> Isn't QOS value update using pm_qos_update_request has a
> direct relation with devfreq drivers i.e. setting the value to
> high or low selects the corresponding voltage and frequency
> setting in devfreq framework? I went through the devfreq
> drivers and couldn't find that relationship. Is this by design or
> I am missing something very obvious?
>
> [1] https://lwn.net/Articles/484161/
next parent reply other threads:[~2018-07-09 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAES_P+_k=fz3yMnVZni2hEnfSujctnT33zoN9-KsBLBeQaG_sA@mail.gmail.com>
2018-07-09 21:34 ` noman pouigt [this message]
[not found] ` <CGME20180709213456epcas4p17e5753d1b59856a0df3790d7faef8d73@epcms1p2>
2018-07-10 5:58 ` Re: devfreq relation with pm qos MyungJoo Ham
2018-07-11 17:02 ` noman pouigt
[not found] ` <CGME20180709213456epcas4p17e5753d1b59856a0df3790d7faef8d73@epcms1p8>
2018-07-12 2:34 ` MyungJoo Ham
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='CAES_P+_GTRcFya=N20+b+U=HOpv9gcpYkfJW_gU_i_2pH2hmMA@mail.gmail.com' \
--to=variksla@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.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;
as well as URLs for NNTP newsgroup(s).