Hi Chanwoo Choi,
On 2016年07月25日 17:45, Chanwoo Choi wrote:
Hi Lin,
On 2016년 07월 25일 17:47, hl wrote:
Hi Chanwoo Choi,
On 2016年07月25日 14:01, Chanwoo Choi wrote:
Hi Lin,
I'm glad to support the for dmc ddr clock scaling with devfreq/devfreq-event.
But, I think that you have to use the
Hi Chanwoo Choi,
On 2016年07月25日 17:45, Chanwoo Choi wrote:
Hi Lin,
On 2016년 07월 25일 17:47, hl wrote:
Hi Chanwoo Choi,
On 2016年07月25日 14:01, Chanwoo Choi wrote:
Hi Lin,
I'm glad to support the for dmc ddr clock scaling with devfreq/devfreq-event.
But, I think that you have to use the
Hi Lin,
On 2016년 07월 25일 17:47, hl wrote:
> Hi Chanwoo Choi,
>
> On 2016年07月25日 14:01, Chanwoo Choi wrote:
>> Hi Lin,
>>
>> I'm glad to support the for dmc ddr clock scaling with devfreq/devfreq-event.
>>
>> But, I think that you have to use the standard interface.
>> As I already mentioned[1]
Hi Lin,
On 2016년 07월 25일 17:47, hl wrote:
> Hi Chanwoo Choi,
>
> On 2016年07月25日 14:01, Chanwoo Choi wrote:
>> Hi Lin,
>>
>> I'm glad to support the for dmc ddr clock scaling with devfreq/devfreq-event.
>>
>> But, I think that you have to use the standard interface.
>> As I already mentioned[1]
Hi Chanwoo Choi,
On 2016年07月25日 14:01, Chanwoo Choi wrote:
Hi Lin,
I'm glad to support the for dmc ddr clock scaling with devfreq/devfreq-event.
But, I think that you have to use the standard interface.
As I already mentioned[1] on previous mail, devfreq fwk support
the standard
Hi Chanwoo Choi,
On 2016年07月25日 14:01, Chanwoo Choi wrote:
Hi Lin,
I'm glad to support the for dmc ddr clock scaling with devfreq/devfreq-event.
But, I think that you have to use the standard interface.
As I already mentioned[1] on previous mail, devfreq fwk support
the standard
Hi Lin,
I'm glad to support the for dmc ddr clock scaling with devfreq/devfreq-event.
But, I think that you have to use the standard interface.
As I already mentioned[1] on previous mail, devfreq fwk support
the standard DEVFREQ_TRANSITION_NOTIFIER notifier which has the two
notifications.
-
Hi Lin,
I'm glad to support the for dmc ddr clock scaling with devfreq/devfreq-event.
But, I think that you have to use the standard interface.
As I already mentioned[1] on previous mail, devfreq fwk support
the standard DEVFREQ_TRANSITION_NOTIFIER notifier which has the two
notifications.
-
Hi Paul,
On 2016年07月23日 04:24, Paul Gortmaker wrote:
On Fri, Jul 22, 2016 at 5:07 AM, Lin Huang wrote:
base on dfi result, we do ddr frequency scaling, register
dmc driver to devfreq framework, and use simple-ondemand
policy.
Signed-off-by: Lin Huang
Hi Paul,
On 2016年07月23日 04:24, Paul Gortmaker wrote:
On Fri, Jul 22, 2016 at 5:07 AM, Lin Huang wrote:
base on dfi result, we do ddr frequency scaling, register
dmc driver to devfreq framework, and use simple-ondemand
policy.
Signed-off-by: Lin Huang
---
Changes in v3:
- operate dram
On Fri, Jul 22, 2016 at 5:07 AM, Lin Huang wrote:
> base on dfi result, we do ddr frequency scaling, register
> dmc driver to devfreq framework, and use simple-ondemand
> policy.
>
> Signed-off-by: Lin Huang
> ---
> Changes in v3:
> - operate dram
On Fri, Jul 22, 2016 at 5:07 AM, Lin Huang wrote:
> base on dfi result, we do ddr frequency scaling, register
> dmc driver to devfreq framework, and use simple-ondemand
> policy.
>
> Signed-off-by: Lin Huang
> ---
> Changes in v3:
> - operate dram setting through sip call
> - imporve set rate
base on dfi result, we do ddr frequency scaling, register
dmc driver to devfreq framework, and use simple-ondemand
policy.
Signed-off-by: Lin Huang
---
Changes in v3:
- operate dram setting through sip call
- imporve set rate flow
Changes in v2:
- None
Changes in v1:
-
base on dfi result, we do ddr frequency scaling, register
dmc driver to devfreq framework, and use simple-ondemand
policy.
Signed-off-by: Lin Huang
---
Changes in v3:
- operate dram setting through sip call
- imporve set rate flow
Changes in v2:
- None
Changes in v1:
- move dfi controller to
14 matches
Mail list logo