From: Viresh Kumar <viresh.kumar@...> commit dc4e7b1fa20a840d2317fcfdaa1064fc09d2afcb upstream. Few doc-style comments were missing, add them. Rearrange another one to match the sequence

From: Bartlomiej Zolnierkiewicz <b.zolnierkie@...> commit fd8d8e63467c922be9ae4452cca2980d473477d9 upstream. Commit 01fb4d3c39d3 ("PM / OPP: Parse 'opp-<prop>-<name>' bindings") broke

From: Viresh Kumar <viresh.kumar@...> commit 754dcf35f34698661801ae1d391efa02affe83a7 upstream. It would be better to name OPP nodes as opp@<opp-hz> as that will ensure that multiple DT nodes

Hi everyone, This is part 1 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

From: Viresh Kumar <viresh.kumar@...> commit af87a39a5f7cf6ef252b1aec3e2e6508a40e51f1 upstream. These aren't used until now by any DT files and wouldn't be used now as we have a better scheme

From: Viresh Kumar <viresh.kumar@...> commit 1c4d12de2719dfdf27c6dab31e7a5641ee293c94 upstream. We may want to enable only a subset of OPPs, from the bigger list of OPPs, based on what

From: Viresh Kumar <viresh.kumar@...> commit ffdb8cc7a27c89175e541e68e2a73f1f63ab8c6b upstream. Depending on the version of hardware or its properties, which are only known at runtime,

From: Viresh Kumar <viresh.kumar@...> commit deaa51465105a7eda19a627b10372f4f7c51a4df upstream. This patch adds debugfs support to OPP layer to export OPPs and their properties for all the

Testing git send-email ... please ignore.

Looks like this didn't hit the mailing list. I will resend again. Sorry for the noise. ChenYu

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

It sounds better to send a series with using these defines one time than separating it with defines and using codes with two times. I will send patch series later, thanks! Best regards, Johnson

For the TSN case I would say it is rather unlikely that this is already in use with any of our current CIP kernels. But I may miss earlier use cases besides TSN. For now, I would not invest

Hi! I did a bit of research on CVE-2020-10742. Unfortunately, RedHat is a bad player here, and bug reports are partly hidden from

Hi! I don't see anything wrong with the patch. OTOH I'd expect to see this in a series with the code actually using these defines. Is there a reason to merge it on its own? Best

Hi! Yes, IIRC. Ok, good to know. So... there are few reasons why it is important to know what is in use or not: 1) If we see patch in stable, how much effort should be spent reviewing it? 2) If

FYI Kind regards, Chris

From: Christina Quast <cquast@...> commit 7ebd1ea798a4932231b18499df136fb552f6f648 upstream. The values are extraced from the "AM335x SitaraTM Processors Technical Reference Manual",

Hi,

Hi! v4.4.225-cip45-rt29 should be available at kernel.org. Trees are available