linux-kernel - [RFC PATCH 00/11] ARM: DT: update cpu device of

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1373883732-26303-1-git-send-email-Sudeep.KarkadaNagesha@arm.com>
Date:	Mon, 15 Jul 2013 11:22:01 +0100
From:	Sudeep.KarkadaNagesha@....com
To:	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Cc:	cpufreq@...r.kernel.org, arnd@...db.de, olof@...om.net,
	lorenzo.pieralisi@....com, rob.herring@...xeda.com,
	grant.likely@...aro.org, rjw@...k.pl, viresh.kumar@...aro.org,
	gregkh@...uxfoundation.org, gregory.clement@...e-electrons.com,
	kernel@...gutronix.de, shawn.guo@...aro.org,
	linux@....linux.org.uk,
	Sudeep KarkadaNagesha <sudeep.karkadanagesha@....com>
Subject: [RFC PATCH 00/11] ARM: DT: update cpu device of_node

From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@....com>

As more and more information is getting added into the cpu node, the number
of drivers needing to parse the device tree for CPU nodes are increasing.
Most of the time, the information needed from the cpu node is preferred
in the logical CPU order. Hence many drivers first parse and search the
CPU node, match them to logical index if needed and then search for the
required property inside a particular cpu node. Some of them assume the
logical and physical CPU ordering to be same which is incorrect.

This patch series initialises the of_node in all the cpu devices when
registering the CPU device.
1. This avoids different drivers having to parse the cpu nodes to obtain
   different attributes like operating points, latency,...etc.
2. This handles different physical and logical cpu ordering which is not
   the case in current code.
3. Also all the cpu nodes will have their of_node initialised correctly.
   Currently different drivers assign them partially and incorrectly.
4. Removes all the reduntant parsing in various drivers.

Regards,
Sudeep

Sudeep KarkadaNagesha (11):
  driver/core: cpu: initialize of_node in cpu's device struture
  ARM: DT/kernel: define ARM specific arch_of_get_cpu_node
  ARM: topology: remove hwid(MPIDR dependency) from cpu_capacity
  ARM: mvebu: remove device tree parsing for cpu nodes
  drivers/bus: arm-cci: avoid parsing DT for cpu device nodes
  cpufreq: imx6q-cpufreq: remove device tree parsing for cpu nodes
  cpufreq: cpufreq-cpu0: remove device tree parsing for cpu nodes
  cpufreq: highbank-cpufreq: remove device tree parsing for cpu nodes
  cpufreq: spear-cpufreq: remove device tree parsing for cpu nodes
  cpufreq: kirkwood-cpufreq: remove device tree parsing for cpu nodes
  cpufreq: arm_big_little: remove device tree parsing for cpu nodes

 arch/arm/include/asm/prom.h         |  1 +
 arch/arm/kernel/devtree.c           | 29 ++++++++++++++++++
 arch/arm/kernel/topology.c          | 61 ++++++++++++-------------------------
 arch/arm/mach-imx/mach-imx6q.c      |  3 +-
 arch/arm/mach-mvebu/platsmp.c       | 52 +++++++++++++++----------------
 drivers/base/cpu.c                  | 19 ++++++++++++
 drivers/bus/arm-cci.c               | 28 +++++------------
 drivers/cpufreq/arm_big_little_dt.c | 39 +++++++++++-------------
 drivers/cpufreq/cpufreq-cpu0.c      | 23 +++-----------
 drivers/cpufreq/highbank-cpufreq.c  | 18 ++++-------
 drivers/cpufreq/imx6q-cpufreq.c     |  4 +--
 drivers/cpufreq/kirkwood-cpufreq.c  | 14 +++++++--
 drivers/cpufreq/spear-cpufreq.c     | 10 +++++-
 13 files changed, 149 insertions(+), 152 deletions(-)

-- 
1.8.1.2


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/