|
[PATCH 4.4.y-cip 16/23] cpufreq: dt: No need to allocate resources anymore
From: Viresh Kumar <viresh.kumar@...>
commit dd02a3d920083b6cb0ee4f0eaf2c599b740bf5fe upstream.
OPP layer manages it now and cpufreq-dt driver doesn't need it. But, we
still need to check for
From: Viresh Kumar <viresh.kumar@...>
commit dd02a3d920083b6cb0ee4f0eaf2c599b740bf5fe upstream.
OPP layer manages it now and cpufreq-dt driver doesn't need it. But, we
still need to check for
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4901
·
|
|
[PATCH 4.4.y-cip 08/23] cpufreq: dt: Convert few pr_debug/err() calls to dev_dbg/err()
From: Viresh Kumar <viresh.kumar@...>
commit 896d6a4c0f41a93809b83f9e58aad73874a89d99 upstream.
We have the device structure available now, lets use it for better
From: Viresh Kumar <viresh.kumar@...>
commit 896d6a4c0f41a93809b83f9e58aad73874a89d99 upstream.
We have the device structure available now, lets use it for better
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4900
·
|
|
[PATCH 4.4.y-cip 14/23] cpufreq: dt: Use dev_pm_opp_set_rate() to switch frequency
From: Viresh Kumar <viresh.kumar@...>
commit 78c3ba5df96c875b1668e1cd3ee0a69e62454f32 upstream.
OPP core supports frequency/voltage changes based on the target
frequency now, use that instead
From: Viresh Kumar <viresh.kumar@...>
commit 78c3ba5df96c875b1668e1cd3ee0a69e62454f32 upstream.
OPP core supports frequency/voltage changes based on the target
frequency now, use that instead
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4899
·
|
|
[PATCH 4.4.y-cip 09/23] cpufreq: dt: Rename 'need_update' to 'opp_v1'
From: Viresh Kumar <viresh.kumar@...>
commit 457e99e60a8f5a40b7da204c0bfc8a86ad2161b9 upstream.
That's the real purpose of this field, i.e. to take special care of old
OPP V1 bindings. Lets
From: Viresh Kumar <viresh.kumar@...>
commit 457e99e60a8f5a40b7da204c0bfc8a86ad2161b9 upstream.
That's the real purpose of this field, i.e. to take special care of old
OPP V1 bindings. Lets
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4898
·
|
|
[PATCH 4.4.y-cip 13/23] cpufreq: dt: Reuse dev_pm_opp_get_max_transition_latency()
From: Viresh Kumar <viresh.kumar@...>
commit 755b888ff098c9f762717a9fbda7e05b16619069 upstream.
OPP layer has all the information now to calculate transition latency
(clock_latency +
From: Viresh Kumar <viresh.kumar@...>
commit 755b888ff098c9f762717a9fbda7e05b16619069 upstream.
OPP layer has all the information now to calculate transition latency
(clock_latency +
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4897
·
|
|
[PATCH 4.4.y-cip 10/23] cpufreq: dt: OPP layers handles clock-latency for V1 bindings as well
From: Viresh Kumar <viresh.kumar@...>
commit 391d9aef8145204e0a5d67be3bd1fc45c5396dae upstream.
"clock-latency" is handled by OPP layer for all bindings and so there is
no need to make
From: Viresh Kumar <viresh.kumar@...>
commit 391d9aef8145204e0a5d67be3bd1fc45c5396dae upstream.
"clock-latency" is handled by OPP layer for all bindings and so there is
no need to make
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4896
·
|
|
[PATCH 4.4.y-cip 11/23] cpufreq: dt: Pass regulator name to the OPP core
From: Viresh Kumar <viresh.kumar@...>
commit 050794aaebbb9f2c2c50b340b6998273e7c64189 upstream.
OPP core can handle the regulators by itself, and but it needs to know
the name of the
From: Viresh Kumar <viresh.kumar@...>
commit 050794aaebbb9f2c2c50b340b6998273e7c64189 upstream.
OPP core can handle the regulators by itself, and but it needs to know
the name of the
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4895
·
|
|
[PATCH 4.4.y-cip 12/23] cpufreq: dt: Unsupported OPPs are already disabled
From: Viresh Kumar <viresh.kumar@...>
commit 6def6ea75e6dea45f01a16ae3cfb5b5ce48dd5e9 upstream.
The core already have a valid regulator set for the device opp and the
unsupported OPPs are
From: Viresh Kumar <viresh.kumar@...>
commit 6def6ea75e6dea45f01a16ae3cfb5b5ce48dd5e9 upstream.
The core already have a valid regulator set for the device opp and the
unsupported OPPs are
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4894
·
|
|
[PATCH 4.4.y-cip 06/23] PM / OPP: Manage device clk
From: Viresh Kumar <viresh.kumar@...>
commit d54974c2513f487e9e70fbdc79c5da51c53e23da upstream.
OPP core has got almost everything now to manage device's OPP
transitions, the only thing left
From: Viresh Kumar <viresh.kumar@...>
commit d54974c2513f487e9e70fbdc79c5da51c53e23da upstream.
OPP core has got almost everything now to manage device's OPP
transitions, the only thing left
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4893
·
|
|
[PATCH 4.4.y-cip 07/23] PM / OPP: Add dev_pm_opp_set_rate()
From: Viresh Kumar <viresh.kumar@...>
commit 6a0712f6f199e737aa5913d28ec4bd3a25de9660 upstream.
This adds a routine, dev_pm_opp_set_rate(), responsible for configuring
power-supply and clock
From: Viresh Kumar <viresh.kumar@...>
commit 6a0712f6f199e737aa5913d28ec4bd3a25de9660 upstream.
This adds a routine, dev_pm_opp_set_rate(), responsible for configuring
power-supply and clock
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4892
·
|
|
[PATCH 4.4.y-cip 05/23] PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings
From: Viresh Kumar <viresh.kumar@...>
commit 50f8cfbd5897ca182d43f4caf19937153f17a604 uptream.
V2 bindings have better support for clock-latency and voltage-tolerance
and doesn't need special
From: Viresh Kumar <viresh.kumar@...>
commit 50f8cfbd5897ca182d43f4caf19937153f17a604 uptream.
V2 bindings have better support for clock-latency and voltage-tolerance
and doesn't need special
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4891
·
|
|
[PATCH 4.4.y-cip 00/23] PM / OPP v2 & cpufreq backports part 2
Hi everyone,
This is part 2 of MOXA's PM / OPP / cpufreq backport series. The whole
series aims to backport patches related to PM / OPPv2 and cpufreq
which were included in the v4.4 kernel from TI's
Hi everyone,
This is part 2 of MOXA's PM / OPP / cpufreq backport series. The whole
series aims to backport patches related to PM / OPPv2 and cpufreq
which were included in the v4.4 kernel from TI's
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4890
·
|
|
[PATCH 4.4.y-cip 02/23] PM / OPP: Disable OPPs that aren't supported by the regulator
From: Viresh Kumar <viresh.kumar@...>
commit 7d34d56ef3349cd5f29cf7aab6650f3414fa81b9 upstream.
Disable any OPPs where the connected regulator isn't able to provide the
specified
From: Viresh Kumar <viresh.kumar@...>
commit 7d34d56ef3349cd5f29cf7aab6650f3414fa81b9 upstream.
Disable any OPPs where the connected regulator isn't able to provide the
specified
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4889
·
|
|
[PATCH 4.4.y-cip 04/23] PM / OPP: Introduce dev_pm_opp_get_max_transition_latency()
From: Viresh Kumar <viresh.kumar@...>
commit 2174344765f472895c076d703c9cdc58215e1393 upstream.
In few use cases (like: cpufreq), it is desired to get the maximum
latency for changing OPPs.
From: Viresh Kumar <viresh.kumar@...>
commit 2174344765f472895c076d703c9cdc58215e1393 upstream.
In few use cases (like: cpufreq), it is desired to get the maximum
latency for changing OPPs.
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4888
·
|
|
[PATCH 4.4.y-cip 01/23] PM / OPP: get/put regulators from OPP core
From: Viresh Kumar <viresh.kumar@...>
commit 9f8ea969d5cfdd4353d2adb004e8e2286b984369 upstream.
This allows the OPP core to request/free the regulator resource,
attached to a device OPP. The
From: Viresh Kumar <viresh.kumar@...>
commit 9f8ea969d5cfdd4353d2adb004e8e2286b984369 upstream.
This allows the OPP core to request/free the regulator resource,
attached to a device OPP. The
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4887
·
|
|
[PATCH 4.4.y-cip 03/23] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
From: Viresh Kumar <viresh.kumar@...>
commit 655c9df961751ce21466f6e97e8033932c27a675 upstream.
In few use cases (like: cpufreq), it is desired to get the maximum
voltage latency for changing
From: Viresh Kumar <viresh.kumar@...>
commit 655c9df961751ce21466f6e97e8033932c27a675 upstream.
In few use cases (like: cpufreq), it is desired to get the maximum
voltage latency for changing
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#4886
·
|
|
Vagrant 2.2.8, 2.2.9 issue
All,
Just wanted to document an issue as well as a/my workaround when using vagrant 2.2.8/2.2.9. After installing vagrant 2.0.2 using apt-get in Ubuntu 18.04, it complained that I had a too new
All,
Just wanted to document an issue as well as a/my workaround when using vagrant 2.2.8/2.2.9. After installing vagrant 2.0.2 using apt-get in Ubuntu 18.04, it complained that I had a too new
|
By
Mohammed Billoo <mab@...>
·
#4885
·
|
|
Re: Working on HTTPS connection
Hi Quirin,
Thank you for the information.
I've added the information to the following issue.
https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/8
Thanks,
Suzuki
Hi Quirin,
Thank you for the information.
I've added the information to the following issue.
https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/8
Thanks,
Suzuki
|
By
Akihiro Suzuki
·
#4884
·
|
|
v4.19-rt status
Hi!
Newest 4.19-rt kernel is currently v4.19.127-rt54. That's not good
match for us, as -cip kernels are v4.19.128-cip28 and v4.19.130-cip29.
I could do kernel based on v4.19.127-rt54 and
Hi!
Newest 4.19-rt kernel is currently v4.19.127-rt54. That's not good
match for us, as -cip kernels are v4.19.128-cip28 and v4.19.130-cip29.
I could do kernel based on v4.19.127-rt54 and
|
By
Pavel Machek
·
#4883
·
|
|
Re: CIP IRC weekly meeting today
Hi, Chris-san,
Sure, then see you at the CIP mini summit!
Best regards,
--
M. Kudo
Hi, Chris-san,
Sure, then see you at the CIP mini summit!
Best regards,
--
M. Kudo
|
By
masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
·
#4882
·
|