| 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
| ||
|
Message-Id: <1376991021-12160-1-git-send-email-Sudeep.KarkadaNagesha@arm.com> Date: Tue, 20 Aug 2013 10:30:02 +0100 From: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@....com> To: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, devicetree@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org Cc: Sudeep.KarkadaNagesha@....com, Viresh Kumar <viresh.kumar@...aro.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Jonas Bonn <jonas@...thpole.se>, Michal Simek <monstr@...str.eu>, "Rafael J. Wysocki" <rjw@...k.pl>, Grant Likely <grant.likely@...aro.org>, Rob Herring <rob.herring@...xeda.com>, Sudeep KarkadaNagesha <sudeep.karkadanagesha@....com> Subject: [PATCH v4 00/19] DT/core: 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. Changes v3->v4: 1. There was a conflict with the generic definition of of_get_cpu_node with the one defined in PPC with the same name but different arguments. This version refactored the PPC definition to support other architectures before moving the code to DT core. This part was separately posted and reviewed[1]. 2. Updated the users of of_get_cpu_node with second argument(i.e. thread id mostly NULL as its currently used only in PPC). Changes v2->v3: 1. Added new OF helper to get of_node from the cpu logical index. With the use of this help, removed lots of duplicated code from cpufreq drivers. 2. Fixed issue with property length calculation in of_get_cpu_node. (previously had assumed of_get_property returns number of cells) 3. Changed return type of arch_match_cpu_phys_id to bool(as suggested by Nico) 4. Re-ordered patch 2 and 3, and few typo fixes. 5. Rebased on v3.11-rc2(to avoid any conflicts with __cpuinit* deletion) Changes v1->v2: 1. Moved most of arch_of_get_cpu_node to OF/DT core as of_get_cpu_node adding a provision for architecture specific hooks for matching logical and physical ids. 2. Extended removal of DT cpu node parsing to PPC cpufreq drivers 3. Added Acks from Viresh and Shawn Regards, Sudeep v1: https://lkml.org/lkml/2013/7/15/128 v2: https://lkml.org/lkml/2013/7/17/341 v3: https://lkml.org/lkml/2013/7/22/219 [1] https://lkml.org/lkml/2013/8/15/319 (PPC refactoring) Sudeep KarkadaNagesha (19): microblaze: remove undefined of_get_cpu_node declaration openrisc: remove undefined of_get_cpu_node declaration powerpc: refactor of_get_cpu_node to support other architectures of: move of_get_cpu_node implementation to DT core library ARM: DT/kernel: define ARM specific arch_match_cpu_phys_id driver/core: cpu: initialize of_node in cpu's device struture of/device: add helper to get cpu device node from logical cpu index 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 cpufreq: maple-cpufreq: remove device tree parsing for cpu nodes cpufreq: pmac64-cpufreq: remove device tree parsing for cpu nodes cpufreq: pmac32-cpufreq: remove device tree parsing for cpu nodes arch/arm/kernel/devtree.c | 5 ++ arch/arm/kernel/topology.c | 61 ++++++++---------------- arch/arm/mach-imx/mach-imx6q.c | 3 +- arch/arm/mach-mvebu/platsmp.c | 51 +++++++++----------- arch/microblaze/include/asm/prom.h | 3 -- arch/openrisc/include/asm/prom.h | 3 -- arch/powerpc/include/asm/prom.h | 3 -- arch/powerpc/kernel/prom.c | 43 +---------------- drivers/base/cpu.c | 2 + drivers/bus/arm-cci.c | 28 +++-------- drivers/cpufreq/arm_big_little_dt.c | 40 ++++++---------- drivers/cpufreq/cpufreq-cpu0.c | 23 ++------- drivers/cpufreq/highbank-cpufreq.c | 18 +++---- drivers/cpufreq/imx6q-cpufreq.c | 4 +- drivers/cpufreq/kirkwood-cpufreq.c | 8 ++-- drivers/cpufreq/maple-cpufreq.c | 23 ++------- drivers/cpufreq/pmac32-cpufreq.c | 5 +- drivers/cpufreq/pmac64-cpufreq.c | 47 +++++------------- drivers/cpufreq/spear-cpufreq.c | 4 +- drivers/of/base.c | 95 +++++++++++++++++++++++++++++++++++++ include/linux/cpu.h | 1 + include/linux/of.h | 7 +++ include/linux/of_device.h | 15 ++++++ 23 files changed, 226 insertions(+), 266 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/
Powered by blists - more mailing lists