linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: noman pouigt <variksla@gmail.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Re: Re: devfreq relation with pm qos
Date: Thu, 12 Jul 2018 11:34:44 +0900	[thread overview]
Message-ID: <20180712023444epcms1p8cb202bb977fcb2b365bc334f87244d04@epcms1p8> (raw)
In-Reply-To: <CAES_P+-=iictJKgHFGN2Mypp_+GMyTOVmZVQw=bSfHbyZMY4QA@mail.gmail.com>

>MyungJo, I am trying to understand the relationship of PM QOS with
>devfreq drivers. I don't see any relation of PM QOS api's with devfreq drivers
>directly as there are no QOS apis used in the devfreq framework.
>
>The only explanation I have is that PM QOS has direct relationship
>with CPUFREQ driver and as CPUFREQ driver works with CPU
>frequency and that CPU frequency directly affects DEVFREQ drivers
>as devfreq driver maps CPU frequency to device frequency and
>that is why PM QOS doesn’t have direct relation with PM QOS.
>
>Is my understanding right?

Your understanding on the fact that there is no relation between
PM QOS and Devfreq framework of today's code is correct.

The reason on why so is not.
In general, you don't make a peripheral device be directly throttled
by CPUFreq values. There exist such cases, but they are not
"general" or inherit characteristics of peripheral devices.

Cheers,
MyungJoo.


      parent reply	other threads:[~2018-07-12  2:35 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 ` devfreq relation with pm qos noman pouigt
     [not found] ` <CGME20180709213456epcas4p17e5753d1b59856a0df3790d7faef8d73@epcms1p2>
2018-07-10  5:58   ` MyungJoo Ham
2018-07-11 17:02     ` noman pouigt
     [not found]     ` <CGME20180709213456epcas4p17e5753d1b59856a0df3790d7faef8d73@epcms1p8>
2018-07-12  2:34       ` MyungJoo Ham [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=20180712023444epcms1p8cb202bb977fcb2b365bc334f87244d04@epcms1p8 \
    --to=myungjoo.ham@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=variksla@gmail.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).