Re: [PATCH v5 2/3] clk: samsung: Don't build ARMv8 clock drivers on ARMv7

2016-02-22 Thread Krzysztof Kozlowski
On 23.02.2016 03:26, Michael Turquette wrote: > Quoting Sylwester Nawrocki (2016-02-17 02:03:36) >> On 16/02/16 07:20, Krzysztof Kozlowski wrote: >>> Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS >>> so it is built also on ARMv7. This does not bring any kind of benefit. >

Re: [PATCH v5 2/3] clk: samsung: Don't build ARMv8 clock drivers on ARMv7

2016-02-22 Thread Michael Turquette
Quoting Sylwester Nawrocki (2016-02-17 02:03:36) > On 16/02/16 07:20, Krzysztof Kozlowski wrote: > > Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS > > so it is built also on ARMv7. This does not bring any kind of benefit. > > There won't be a single kernel image for ARMv7

Re: [PATCH v5 2/3] clk: samsung: Don't build ARMv8 clock drivers on ARMv7

2016-02-17 Thread Sylwester Nawrocki
On 16/02/16 07:20, Krzysztof Kozlowski wrote: > Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS > so it is built also on ARMv7. This does not bring any kind of benefit. > There won't be a single kernel image for ARMv7 and ARMv8 SoCs (like > multi_v7 for ARMv7). > > Instead

[PATCH v5 2/3] clk: samsung: Don't build ARMv8 clock drivers on ARMv7

2016-02-15 Thread Krzysztof Kozlowski
Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS so it is built also on ARMv7. This does not bring any kind of benefit. There won't be a single kernel image for ARMv7 and ARMv8 SoCs (like multi_v7 for ARMv7). Instead build clock drivers only for respective SoC's architectur