Hello MyungJoo!
On 2015-02-24 02:22, MyungJoo Ham wrote:
Unless you are willing to wait for 2 minutes after the kernal hangs,
you may want to adjust DEFAULT_HUNG_TASK_TIMEOUT to shorter value
(120 -- 5 for 5 seconds). It seems that you've cut it off in the
middle
of that 120 sec wait.
Thanks
Hello Chanwoo!
Chanwoo Choi wrote:
As you thought, when maintaining lower clock of memory bus frequency,
some issue related to multimedia feature will happen.
Separately, We have to check the miminum lower clock for working of
multimedia feature.
and then multimedia or other IP have to
Hello Chanwoo!
Chanwoo Choi wrote:
As you thought, when maintaining lower clock of memory bus frequency,
some issue related to multimedia feature will happen.
Separately, We have to check the miminum lower clock for working of
multimedia feature.
and then multimedia or other IP
Hi Tobias,
On 02/24/2015 04:57 AM, Tobias Jakobi wrote:
Hello Chanwoo!
Chanwoo Choi wrote:
As you thought, when maintaining lower clock of memory bus frequency,
some issue related to multimedia feature will happen.
Separately, We have to check the miminum lower clock for working of
Hi Tobias,
First of all, thanks for your test.
On 02/19/2015 05:59 AM, Tobias Jakobi wrote:
Hello again,
Tobias Jakobi wrote
I've tested the series on my Odroid-X2 (by adapting the TRATS2 changes),
and so far I haven't seen any issues. With the system being idle one can
see that the
Hello again,
Tobias Jakobi wrote
I've tested the series on my Odroid-X2 (by adapting the TRATS2 changes),
and so far I haven't seen any issues. With the system being idle one can
see that the 'simple_ondemand' devfreq governor clocks down both memory
busses to the lowest state.
looks I was
Hello,
I've tested the series on my Odroid-X2 (by adapting the TRATS2 changes),
and so far I haven't seen any issues. With the system being idle one can
see that the 'simple_ondemand' devfreq governor clocks down both memory
busses to the lowest state.
With best wishes,
Tobias
--
To unsubscribe
