linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	Ionela Voinescu <ionela.voinescu@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Vincent Guittot <vincent.guittot@linaro.org>
Subject: [PATCH V4 0/3] arm64: topology: improvements
Date: Fri,  8 Jan 2021 16:46:50 +0530	[thread overview]
Message-ID: <cover.1610104461.git.viresh.kumar@linaro.org> (raw)

Hi,

Here is the V4 with the general improvements for topology stuff. This
cleans up the code and makes it work with cpufreq modules.

V4:
- Added Rby from Ionela.
- In 3/3, Print cpus instead of amu_fie_cpus and make it pr_debug
  instead.

Viresh Kumar (3):
  arm64: topology: Avoid the have_policy check
  arm64: topology: Reorder init_amu_fie() a bit
  arm64: topology: Make AMUs work with modular cpufreq drivers

 arch/arm64/kernel/topology.c | 115 +++++++++++++++++------------------
 1 file changed, 56 insertions(+), 59 deletions(-)

-- 
2.25.0.rc1.19.g042ed3e048af


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-01-08 11:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 11:16 Viresh Kumar [this message]
2021-01-08 11:16 ` [PATCH V4 1/3] arm64: topology: Avoid the have_policy check Viresh Kumar
2021-01-08 11:16 ` [PATCH V4 2/3] arm64: topology: Reorder init_amu_fie() a bit Viresh Kumar
2021-01-08 11:16 ` [PATCH V4 3/3] arm64: topology: Make AMUs work with modular cpufreq drivers Viresh Kumar
2021-01-08 15:51   ` Ionela Voinescu
2021-01-08 15:53 ` [PATCH V4 0/3] arm64: topology: improvements Ionela Voinescu
2021-01-11  4:46   ` Viresh Kumar
2021-01-19  9:12 ` Viresh Kumar
2021-01-20 13:01 ` Will Deacon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1610104461.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=ionela.voinescu@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).