with
CONFIG_CPU_FREQ_STAT now in them, as users wanted stats to be enabled.
Signed-off-by: Viresh Kumar
---
arch/arm/configs/exynos_defconfig | 2 +-
arch/arm/configs/multi_v5_defconfig | 2 +-
arch/arm/configs/multi_v7_defconfig | 2 +-
arch/arm/configs/mvebu_v5_defconfig
The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform
device now, reuse that and remove similar code from platform code.
Cc: Simon Horman
Cc: Magnus Damm
Signed-off-by: Viresh Kumar
---
arch/arm/mach-shmobile/Makefile | 1 -
arch/arm/mach-shmobile/common.h | 7
On 21-04-16, 15:04, Geert Uytterhoeven wrote:
> Hi Viresh,
>
> On Thu, Apr 21, 2016 at 10:43 AM, Viresh Kumar
> wrote:
> > --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> > @@ -29,6 +29,18 @@ static cons
On 22-04-16, 08:41, Geert Uytterhoeven wrote:
> I was mainly thinking about kernel size.
Ahh, I see..
> If this is done once per boot, the array should be __initconst,
> (looking at the code
> in next) which is fine as cpufreq_dt_platdev_init() is already __init.
Sure, makes sense.. I will do th
The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform
device now, reuse that and remove similar code from platform code.
Cc: Simon Horman
Cc: Magnus Damm
Signed-off-by: Viresh Kumar
Acked-by: Arnd Bergmann
---
arch/arm/mach-shmobile/Makefile | 1 -
arch/arm/mach
sas,r8a7794", },
> { .compatible = "renesas,r8a7795", },
> + { .compatible = "renesas,r8a7796", },
> { .compatible = "renesas,sh73a0", },
>
> { .compatible = "rockchip,rk2928", },
Well, you could have done that in the same patch. But I don't mind two patches
now.
Acked-by: Viresh Kumar
--
viresh
gned-off-by: Khiem Nguyen
> ---
> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Viresh Kumar
--
viresh
On 10-05-16, 10:17, Geert Uytterhoeven wrote:
> Hi Viresh,
>
> On Tue, May 10, 2016 at 7:07 AM, Viresh Kumar wrote:
> > On 10-05-16, 11:57, Khiem Nguyen wrote:
> >> After the commit "a399dc9fc50 cpufreq: shmobile: Use generic platdev
> >> driver", w
"renesas,r8a7792", },
> { .compatible = "renesas,r8a7793", },
> { .compatible = "renesas,r8a7794", },
> { .compatible = "renesas,sh73a0", },
Acked-by: Viresh Kumar
--
viresh
n v4.10.
Acked-by: Viresh Kumar
--
viresh
drivers/dma/dw/platform.c | 6 ++
> 1 file changed, 2 insertions(+), 4 deletions(-)
Acked-by: Viresh Kumar
--
viresh
t; drivers/staging/greybus/arche-platform.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Acked-by: Viresh Kumar
--
viresh
Revert "cpufreq: rcar: Add support for R8A7795 SoC"
>
> drivers/cpufreq/cpufreq-dt-platdev.c | 2 --
> 1 file changed, 2 deletions(-)
Acked-by: Viresh Kumar
--
viresh
dt-platdev.c
> @@ -67,6 +67,7 @@ static const struct of_device_id machines[] __initconst = {
> { .compatible = "renesas,r8a7792", },
> { .compatible = "renesas,r8a7793", },
> { .compatible = "renesas,r8a7794", },
> + { .compatible = "renesas,r8a7795", },
> { .compatible = "renesas,sh73a0", },
>
> { .compatible = "rockchip,rk2928", },
Acked-by: Viresh Kumar
--
viresh
},
> + { .compatible = "renesas,r8a7796", },
> { .compatible = "renesas,sh73a0", },
>
> { .compatible = "rockchip,rk2928", },
Acked-by: Viresh Kumar
--
viresh
On 14-08-17, 15:36, Geert Uytterhoeven wrote:
> I'm still a bit confused about your original comment when introducing this
> file with the ever-growing table of SoCs:
>
> "And for new platforms we may do things differently as they are going
> to use opp-v2 bindings."
>
> Hence I was unde
ill happen because the operating system looks for such properties in
the CPU node it is trying to bring up, so that it can create an OPP
table.
Add such missing properties.
Fix other missing property (clock latency) as well to make it all
work.
Signed-off-by: Viresh Kumar
---
arch/arm/boot/dts/r8
Viresh Kumar (15):
arm: dts: armada: Fix "#cooling-cells" property's name
arm: dts: ls1021a: Add missing cooling device properties for CPUs
arm: dts: mediatek: Add missing cooling device properties for CPUs
arm: dts: rk322x: Add missing cooling device properties for CPUs
arm
On 28-05-18, 11:23, Simon Horman wrote:
> [Cc Biju Das]
>
> On Fri, May 25, 2018 at 04:01:59PM +0530, Viresh Kumar wrote:
> > The OPP properties, like "operating-points", should either be present
> > for all the CPUs of a cluster or none. If these are present onl
mpatible = "renesas,r8a7745", },
> { .compatible = "renesas,r8a7778", },
> { .compatible = "renesas,r8a7779", },
Acked-by: Viresh Kumar
--
viresh
ps to include all devices affected by individual trip
points.
Signed-off-by: Viresh Kumar
---
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 15 ---
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 6 +++---
2 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/arch/arm64/boot/dts/re
e cooling maps to include all devices affected by individual trip
points.
Individual maintainers can take the patches through their tree.
--
viresh
Viresh Kumar (10):
ARM64: dts: amlogic: Add all CPUs in cooling maps
ARM64: dts: exynos: Add all CPUs in cooling maps
ARM64: dts: fsl: Add all CPU
22 matches
Mail list logo
