From: Chanwoo Choi <cw00.choi@samsung.com>
To: myungjoo.ham@samsung.com, ABHILASH KESAVAN <a.kesavan@samsung.com>
Cc: "kgene@kernel.org" <kgene@kernel.org>,
박경민 <kyungmin.park@samsung.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"tomasz.figa@gmail.com" <tomasz.figa@gmail.com>,
"Krzysztof Kozlowski" <k.kozlowski@samsung.com>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
대인기 <inki.dae@samsung.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCHv7 00/10] devfreq: Add devfreq-event class to provide raw data for devfreq device
Date: Mon, 12 Jan 2015 19:17:05 +0900 [thread overview]
Message-ID: <54B39F21.3070602@samsung.com> (raw)
In-Reply-To: <437622256.904751421056684753.JavaMail.weblogic@epmlwas01a>
On 01/12/2015 06:58 PM, MyungJoo Ham wrote:
>>
>> This patchset add new devfreq_event class to provide raw data to determine
>> current utilization of device which is used for devfreq governor.
>>
>> The following description explains the feature of two kind of devfreq class:
>> - devfreq class (existing)
>> : devfreq consumer device use raw data from devfreq_event device for
>> determining proper current system state and change voltage/frequency
>> dynamically using various governors.
>> - devfreq_event class (new)
>> : Provide measured raw data to devfreq device for governor
>>
>
> Question: Applying this patchset seems to imply that
> drivers/devfreq/exynos/exynos_ppmu.c becomes obsolete.
> How do you want to address it? Do you think it'd be ok to remove
> thse obsolete drivers after your successing patchset?
>
> If it is ok to remove old drivers after applying the new patchset,
> please inclde a patch that removes old drivers unless such a removal
> might result in compatibility issues with old (yet another obsolete)
> board files, which I don't think probable.
I agree to remove 'drviers/devfreq/exynos/exynos_ppmu.c.
But, existing exynos_ppmu.c was used for drivers/devfreq/exynos/exynos5_bus.c.
Before removing existing 'exynos_ppmu.c', might need to test the devfreq-event class
on Exynos5260 SoC. I will just remove old driver('drivers/devfreq/exynos/exynos4_bus.{c|h}')
on next patchset.
To Abhilash,
Could you test this patch-set on Exynos5260 SoC?
Best Regards,
Chanwoo Choi
WARNING: multiple messages have this Message-ID (diff)
From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv7 00/10] devfreq: Add devfreq-event class to provide raw data for devfreq device
Date: Mon, 12 Jan 2015 19:17:05 +0900 [thread overview]
Message-ID: <54B39F21.3070602@samsung.com> (raw)
In-Reply-To: <437622256.904751421056684753.JavaMail.weblogic@epmlwas01a>
On 01/12/2015 06:58 PM, MyungJoo Ham wrote:
>>
>> This patchset add new devfreq_event class to provide raw data to determine
>> current utilization of device which is used for devfreq governor.
>>
>> The following description explains the feature of two kind of devfreq class:
>> - devfreq class (existing)
>> : devfreq consumer device use raw data from devfreq_event device for
>> determining proper current system state and change voltage/frequency
>> dynamically using various governors.
>> - devfreq_event class (new)
>> : Provide measured raw data to devfreq device for governor
>>
>
> Question: Applying this patchset seems to imply that
> drivers/devfreq/exynos/exynos_ppmu.c becomes obsolete.
> How do you want to address it? Do you think it'd be ok to remove
> thse obsolete drivers after your successing patchset?
>
> If it is ok to remove old drivers after applying the new patchset,
> please inclde a patch that removes old drivers unless such a removal
> might result in compatibility issues with old (yet another obsolete)
> board files, which I don't think probable.
I agree to remove 'drviers/devfreq/exynos/exynos_ppmu.c.
But, existing exynos_ppmu.c was used for drivers/devfreq/exynos/exynos5_bus.c.
Before removing existing 'exynos_ppmu.c', might need to test the devfreq-event class
on Exynos5260 SoC. I will just remove old driver('drivers/devfreq/exynos/exynos4_bus.{c|h}')
on next patchset.
To Abhilash,
Could you test this patch-set on Exynos5260 SoC?
Best Regards,
Chanwoo Choi
next prev parent reply other threads:[~2015-01-12 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 9:58 [PATCHv7 00/10] devfreq: Add devfreq-event class to provide raw data for devfreq device MyungJoo Ham
2015-01-12 9:58 ` MyungJoo Ham
2015-01-12 10:17 ` Chanwoo Choi [this message]
2015-01-12 10:17 ` Chanwoo Choi
-- strict thread matches above, loose matches on Subject: below --
2015-01-07 23:51 Chanwoo Choi
2015-01-07 23:51 ` Chanwoo Choi
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=54B39F21.3070602@samsung.com \
--to=cw00.choi@samsung.com \
--cc=a.kesavan@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=inki.dae@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--cc=tomasz.figa@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 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.