From: Thomas Abraham <ta.omasab@gmail.com>
To: Sudeep Holla <Sudeep.Holla@arm.com>
Cc: Nishanth Menon <nm@ti.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"kgene.kim@samsung.com" <kgene.kim@samsung.com>,
"t.figa@samsung.com" <t.figa@samsung.com>,
"l.majewski@samsung.com" <l.majewski@samsung.com>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"thomas.ab@samsung.com" <thomas.ab@samsung.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v2 2/2] Documentation: devicetree: Add boost-frequency binding to list boost mode frequency
Date: Sat, 8 Feb 2014 12:17:09 +0530 [thread overview]
Message-ID: <CAJuA9agcpbKYocaQUBr2-VCXcXAo3r3urFF=+G_+ib2jCZqvwg@mail.gmail.com> (raw)
In-Reply-To: <52F51FCD.5000009@arm.com>
On Fri, Feb 7, 2014 at 11:32 PM, Sudeep Holla <Sudeep.Holla@arm.com> wrote:
> On 07/02/14 17:37, Nishanth Menon wrote:
>> On Fri, Feb 7, 2014 at 11:31 AM, Sudeep Holla <Sudeep.Holla@arm.com> wrote:
>
> [...]
>
>>> Yes I think its counter-intuitive as it's visible to the userspace(list of
>>> frequencies and the boost parameters are exposed through sysfs)
>>
>> That will be a different problem -> as currently every single
>> frequency in the cpufreq list has ability to be marked as boost
>> frequency - if userspace does not maintain that, then, IMHO, fix the
>> userspace :D
>>
>
> /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies gives
> the list of frequencies based on the state of the boost feature at anytime.
The list of frequencies in
/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies
does not change based in the state of the boost feature (enabled or
disabled). But the scaling_max_frequency and scaling_min_frequency are
updated based on the set of available + boost frequencies available.
>
> Intuitively the list without boost shouldn't have any frequency above the range
> when it's enabled :), that's what I was referring to. So I am not talking about
> any issue with user-space maintenance.
>
> Regards,
> Sudeep
>
WARNING: multiple messages have this Message-ID (diff)
From: ta.omasab@gmail.com (Thomas Abraham)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] Documentation: devicetree: Add boost-frequency binding to list boost mode frequency
Date: Sat, 8 Feb 2014 12:17:09 +0530 [thread overview]
Message-ID: <CAJuA9agcpbKYocaQUBr2-VCXcXAo3r3urFF=+G_+ib2jCZqvwg@mail.gmail.com> (raw)
In-Reply-To: <52F51FCD.5000009@arm.com>
On Fri, Feb 7, 2014 at 11:32 PM, Sudeep Holla <Sudeep.Holla@arm.com> wrote:
> On 07/02/14 17:37, Nishanth Menon wrote:
>> On Fri, Feb 7, 2014 at 11:31 AM, Sudeep Holla <Sudeep.Holla@arm.com> wrote:
>
> [...]
>
>>> Yes I think its counter-intuitive as it's visible to the userspace(list of
>>> frequencies and the boost parameters are exposed through sysfs)
>>
>> That will be a different problem -> as currently every single
>> frequency in the cpufreq list has ability to be marked as boost
>> frequency - if userspace does not maintain that, then, IMHO, fix the
>> userspace :D
>>
>
> /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies gives
> the list of frequencies based on the state of the boost feature at anytime.
The list of frequencies in
/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies
does not change based in the state of the boost feature (enabled or
disabled). But the scaling_max_frequency and scaling_min_frequency are
updated based on the set of available + boost frequencies available.
>
> Intuitively the list without boost shouldn't have any frequency above the range
> when it's enabled :), that's what I was referring to. So I am not talking about
> any issue with user-space maintenance.
>
> Regards,
> Sudeep
>
next prev parent reply other threads:[~2014-02-08 6:47 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 15:19 [PATCH v2 0/2] Add device tree based lookup of boost mode frequency Thomas Abraham
2014-02-07 15:19 ` Thomas Abraham
2014-02-07 15:19 ` [PATCH v2 1/2] PM / OPP: Allow boost frequency to be looked up from device tree Thomas Abraham
2014-02-07 15:19 ` Thomas Abraham
2014-02-07 15:29 ` Nishanth Menon
2014-02-07 15:29 ` Nishanth Menon
2014-02-07 15:38 ` Thomas Abraham
2014-02-07 15:38 ` Thomas Abraham
2014-02-07 15:52 ` Nishanth Menon
2014-02-07 15:52 ` Nishanth Menon
2014-02-07 16:01 ` Sudeep Holla
2014-02-07 16:01 ` Sudeep Holla
2014-02-08 5:10 ` Thomas Abraham
2014-02-08 5:10 ` Thomas Abraham
2014-02-10 7:10 ` Lukasz Majewski
2014-02-10 7:10 ` Lukasz Majewski
2014-02-10 10:40 ` Sudeep Holla
2014-02-10 10:40 ` Sudeep Holla
2014-02-07 15:19 ` [PATCH v2 2/2] Documentation: devicetree: Add boost-frequency binding to list boost mode frequency Thomas Abraham
2014-02-07 15:19 ` Thomas Abraham
2014-02-07 15:27 ` Nishanth Menon
2014-02-07 15:27 ` Nishanth Menon
2014-02-07 15:38 ` Thomas Abraham
2014-02-07 15:38 ` Thomas Abraham
2014-02-07 16:15 ` Sudeep Holla
2014-02-07 16:15 ` Sudeep Holla
2014-02-07 16:28 ` Sudeep Holla
2014-02-07 16:28 ` Sudeep Holla
2014-02-07 16:43 ` Nishanth Menon
2014-02-07 16:43 ` Nishanth Menon
2014-02-07 17:31 ` Sudeep Holla
2014-02-07 17:31 ` Sudeep Holla
2014-02-07 17:37 ` Nishanth Menon
2014-02-07 17:37 ` Nishanth Menon
2014-02-07 17:40 ` Nishanth Menon
2014-02-07 17:40 ` Nishanth Menon
2014-02-07 18:02 ` Sudeep Holla
2014-02-07 18:02 ` Sudeep Holla
2014-02-07 19:41 ` Nishanth Menon
2014-02-07 19:41 ` Nishanth Menon
2014-02-08 6:47 ` Thomas Abraham
2014-02-08 6:47 ` Thomas Abraham
2014-02-10 7:53 ` Lukasz Majewski
2014-02-10 7:53 ` Lukasz Majewski
2014-02-10 11:20 ` Sudeep Holla
2014-02-10 11:20 ` Sudeep Holla
2014-02-08 6:47 ` Thomas Abraham [this message]
2014-02-08 6:47 ` Thomas Abraham
2014-02-10 7:38 ` Lukasz Majewski
2014-02-10 7:38 ` Lukasz Majewski
2014-02-10 10:51 ` Sudeep Holla
2014-02-10 10:51 ` Sudeep Holla
2014-02-10 10:46 ` Sudeep Holla
2014-02-10 10:46 ` Sudeep Holla
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='CAJuA9agcpbKYocaQUBr2-VCXcXAo3r3urFF=+G_+ib2jCZqvwg@mail.gmail.com' \
--to=ta.omasab@gmail.com \
--cc=Mark.Rutland@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kgene.kim@samsung.com \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=t.figa@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=viresh.kumar@linaro.org \
/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.