|
[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
·
|
|
Re: CIP IRC weekly meeting today
Hello Kudo-san,
Please accept my apologies; I can't babe the meeting this week.
Kind regards, Chris
Hello Kudo-san,
Please accept my apologies; I can't babe the meeting this week.
Kind regards, Chris
|
By
Chris Paterson
·
#4881
·
|
|
Re: Working on HTTPS connection
Hi,
if you add the following elements to the swupdate build config. HTTPS works more or less. I did not test it in all configurations, only for a short demo. And some of the options may not be
Hi,
if you add the following elements to the swupdate build config. HTTPS works more or less. I did not test it in all configurations, only for a short demo. And some of the options may not be
|
By
Quirin Gylstorff
·
#4880
·
|
|
Re: Setting up SWUpdate
Hi Mohammed,
If you work on this issue, you will be able to learn about our software update mechanism well, I think.
Can I assign you to work on this issue?
Thanks,
Suzuki
Hi Mohammed,
If you work on this issue, you will be able to learn about our software update mechanism well, I think.
Can I assign you to work on this issue?
Thanks,
Suzuki
|
By
Akihiro Suzuki
·
#4879
·
|
|
CIP IRC weekly meeting today
Hi all,
Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting
Hi all,
Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.
*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting
|
By
masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
·
#4878
·
|
|
Building generic initramfs for the various testing
Hello list,
Long time no see... ;-)
Just for the sake of Reality: the generic initramfs building from the:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipsystembuildhowto
Does not
Hello list,
Long time no see... ;-)
Just for the sake of Reality: the generic initramfs building from the:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipsystembuildhowto
Does not
|
By
Zoran
·
#4877
·
|
|
Re: Setting up SWUpdate
Suzuki,
I can look into this issue as well (when my BBB comes in). It's focused enough that I can learn enough about SWUpdate and how it fits into CIP.
Let me know what you think.
Mohammed
--
Suzuki,
I can look into this issue as well (when my BBB comes in). It's focused enough that I can learn enough about SWUpdate and how it fits into CIP.
Let me know what you think.
Mohammed
--
|
By
Mohammed Billoo <mab@...>
·
#4876
·
|
|
Re: Setting up SWUpdate
Hi Mohammed,
> NOTE: Now I have a problem with the demo. I’ll make the issue about it in cip-sw-updates-tasks repository later.
I’ve made the issue about
Hi Mohammed,
> NOTE: Now I have a problem with the demo. I’ll make the issue about it in cip-sw-updates-tasks repository later.
I’ve made the issue about
|
By
Akihiro Suzuki
·
#4875
·
|