From: sachin.kamat@linaro.org (Sachin Kamat)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 0/4] Add basic support for ASV
Date: Mon, 18 Nov 2013 09:37:49 +0530 [thread overview]
Message-ID: <CAK9yfHzUAnBMB2Bp+eKzR3NH1iRguJn4K45gss5psWzG4Lc7tw@mail.gmail.com> (raw)
In-Reply-To: <CAJ0PZbS8FxRA_sPTOnWbZcNfUMp=k5Jf_tZHLg1fh6gsAGJ=Gw@mail.gmail.com>
Hi MyungJoo,
On 18 November 2013 08:07, MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>
> 2013. 11. 15. ?? 8:44? "Sachin Kamat" <sachin.kamat@linaro.org>?? ??:
>
>
>>
>> Original cover letter from Yadwinder:
>> This series is to add basic common infrastructure for ASV.
>> Basically ASV is a technique used on samsung SoCs, which provides the
>> recommended supply voltage for dvfs of arm, mif etc. For a given operating
>> frequency, the voltage is recommended based on SoC's ASV group.
>> ASV group gets fussed on SoCs during process of mass production.
>>
>> This series includes:
>> - basic common infrastructue for ASV. It provides common APIs for user
>> drivers
>> like cpufreq & devfreq and and an interface for SoC specific drivers to
>> register ASV members(instances)
>> - a common platform driver to register ASV members for exynos SoCs
>> - an example providing minimal support (only for ARM ASV) for exynos5250
>> chips
>>
>> Its just basic skelton which I wanted to get it reviewed or discussed in
>> early stage, before going ahead on further development based on it.
>> Presently example is based on static ASV table provided in SoC specific
>> file,
>> which I expects to go into DT. But exactly how and where needs to be
>> discussed,
>> may be in next revisions once we get through the basic skelton.
>> Also the location of driver in kernel may also seem odd to someone and
>> many more things :).
>>
>> Looking for your valuable reviews and suggestions.
>
> Hi,
>
> As I have commented on the previous thread of Yadwinder, please share the
> directory woth AVS, which is conceptually a superset of ASV.
>
> Ultimately, it would be best if you can supply an infra that can be shared
> with the current AVS, which does not have any currently.
>
Yadwinder has already replied to your suggestion about his concerns. Please
share your comments.
--
With warm regards,
Sachin
next prev parent reply other threads:[~2013-11-18 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 11:41 [RFC v2 0/4] Add basic support for ASV Sachin Kamat
[not found] ` <CAJ0PZbS8FxRA_sPTOnWbZcNfUMp=k5Jf_tZHLg1fh6gsAGJ=Gw@mail.gmail.com>
2013-11-18 4:07 ` Sachin Kamat [this message]
2013-12-03 14:46 ` Abhilash Kesavan
2013-12-04 6:00 ` Sachin Kamat
2015-01-13 16:19 ` Kevin Hilman
[not found] ` <1384515691-26299-3-git-send-email-sachin.kamat@linaro.org>
2013-12-03 14:46 ` [RFC v2 2/4] power: asv: Add a common ASV driver for Exynos SoCs Abhilash Kesavan
[not found] ` <1384515691-26299-2-git-send-email-sachin.kamat@linaro.org>
2013-12-03 14:46 ` [RFC v2 1/4] power: asv: Add common ASV support for Samsung SoCs Abhilash Kesavan
2013-12-15 13:38 ` Yadwinder Singh Brar
2013-12-09 18:45 ` Tomasz Figa
2013-12-15 13:30 ` Yadwinder Singh Brar
2013-12-15 13:51 ` Tomasz Figa
2013-12-26 16:28 ` Yadwinder Singh Brar
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=CAK9yfHzUAnBMB2Bp+eKzR3NH1iRguJn4K45gss5psWzG4Lc7tw@mail.gmail.com \
--to=sachin.kamat@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 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).