ARM: tegra: fuse: add fuctions to read speedo id and process id
Subsystems (3)
PATCH 1/1 ARM: tegra: fuse: add fuctions to read speedo id and process id
Add functions to read the speedo and process id of both cpu and soc. There might be some drivers need the information as well.
--- arch/arm/mach-tegra/fuse.c | 24 ++++++++++++++++++++++++ include/linux/tegra-soc.h | 6 +++++- 2 files changed, 29 insertions(+), 1 deletion(-)
arch/arm/mach-tegra/fuse.c +24 -0
@@ -2,6 +2,7 @@* arch/arm/mach-tegra/fuse.c * * Copyright (C) 2010 Google, Inc. +* Copyright (c) 2013, NVIDIA CORPORATION. All rights reserved. * * Author: * Colin Cross <[email protected]>
@@ -161,3 +162,26 @@ unsigned long long tegra_chip_uid(void)return (hi <<32ull ) | lo; }EXPORT_SYMBOL (tegra_chip_uid); + +int tegra_get_cpu_process_id (void ) +{ +return tegra_cpu_process_id; +} + +int tegra_get_core_process_id (void ) +{ +return tegra_core_process_id; +} + +int tegra_get_cpu_speedo_id (void ) +{ +if (tegra_chip_id ==TEGRA20 ) +return -EINVAL ; + +return tegra_cpu_speedo_id; +} + +int tegra_get_soc_speedo_id (void ) +{ +return tegra_soc_speedo_id; +}
include/linux/tegra-soc.h +5 -1
@@ -1,5 +1,5 @@/* -* Copyright (c) 2012, NVIDIA CORPORATION. All rights reserved. +* Copyright (c) 2012,2013, NVIDIA CORPORATION. All rights reserved. * * This program is free software; you can redistribute it and/or modify it * under the terms and conditions of the GNU General Public License,
@@ -18,5 +18,9 @@#define __LINUX_TEGRA_SOC_H_u32 tegra_read_chipid (void ); +int tegra_get_cpu_process_id (void ); +int tegra_get_core_process_id (void ); +int tegra_get_cpu_speedo_id (void ); +int tegra_get_soc_speedo_id (void );#endif /* __LINUX_TEGRA_SOC_H_ */
Signature · 1 line
1.8.2
Quoted 2 lines · Danny Huang
Add functions to read the speedo and process id of both cpu and soc. There might be some drivers need the information as well.
What code wants to use these functions? It'd be best to submit this patch with that code, so that something actually uses the functions, and they don't look like dead code.
In the past, functions similar to this used to exist. However, they were removed and replaced by direct access to the underlying variables. Do we actually need functions for this, or can code simply read from the variables instead?
Quoted 7 lines · Stephen Warren
Quoted 2 lines · Danny Huang
Add functions to read the speedo and process id of both cpu and soc. There might be some drivers need the information as well.
What code wants to use these functions? It'd be best to submit this patch with that code, so that something actually uses the functions, and they don't look like dead code.
There are some developing drivers that are located in drivers folder needs those information. I think that they can't include a header file in mach-tegra folder. Hence I'd like to provide them such functions for their development.
Is there any better way to do this?
Quoted 5 lines
In the past, functions similar to this used to exist. However, they were removed and replaced by direct access to the underlying variables. Do we actually need functions for this, or can code simply read from the variables instead?
Quoted 11 lines · Danny Huang
Quoted 7 lines · Stephen Warren
Quoted 2 lines · Danny Huang
Add functions to read the speedo and process id of both cpu and soc. There might be some drivers need the information as well.
What code wants to use these functions? It'd be best to submit this patch with that code, so that something actually uses the functions, and they don't look like dead code.
There are some developing drivers that are located in drivers folder needs those information.
Which drivers?
Quoted 1 line
I think that they can't include a header file in mach-tegra folder
True.
Quoted 6 lines · Stephen Warren
Quoted 5 lines · Danny Huang
Quoted 4 lines · Stephen Warren
Quoted 2 lines · Danny Huang
Add functions to read the speedo and process id of both cpu and soc. There might be some drivers need the information as well.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
What code wants to use these functions? It'd be best to submit this patch with that code, so that something actually uses the functions, and they don't look like dead code.
There are some developing drivers that are located in drivers folder needs those information.
Which drivers?
Per my understanding, there is a dvfs development that is trying to use the devfreq framework.
Quoted 8 lines
Quoted 2 lines
I think that they can't include a header file in mach-tegra folder
True.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html