Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753028AbbKQEbo (ORCPT ); Mon, 16 Nov 2015 23:31:44 -0500 Received: from mailout4.samsung.com ([203.254.224.34]:54869 "EHLO mailout4.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752913AbbKQEbl (ORCPT ); Mon, 16 Nov 2015 23:31:41 -0500 X-AuditID: cbfee68e-f791c6d000001498-1a-564aadab13de Subject: Re: [PATCH 1/2] clk: samsung: Don't build ARMv8 clock drivers on ARMv7 To: Krzysztof Kozlowski , Sylwester Nawrocki , Tomasz Figa , Michael Turquette , Stephen Boyd , linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, Catalin Marinas , Will Deacon , Kukjin Kim , Olof Johansson , Arnd Bergmann , linux-arm-kernel@lists.infradead.org, Kevin Hilman References: <1447637775-9887-1-git-send-email-k.kozlowski@samsung.com> <1447637775-9887-2-git-send-email-k.kozlowski@samsung.com> From: "pankaj.dubey" Message-id: <564AADB2.3030400@samsung.com> Date: Tue, 17 Nov 2015 10:01:46 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-version: 1.0 In-reply-to: <1447637775-9887-2-git-send-email-k.kozlowski@samsung.com> Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFIsWRmVeSWpSXmKPExsWyRsSkSnf1Wq8wg65XZhZ/Jx1jt3i/rIfR 4vULQ4v+x6+ZLb4eXsFosenxNVaLjz33WC0u75rDZjHj/D4mi4unXC1OXf/MZnH4TTurxY8z 3SwWq3b9YbR4+fEEiwO/x5p5axg9fv+axOjx/kYru8flvl4mj52z7rJ7bFrVyeZx59oeNo/N S+o9rpxoYvXo27KK0ePzJrkA7igum5TUnMyy1CJ9uwSujPYunoK9IhUnrq5namCcLNjFyMkh IWAisWnlIVYIW0ziwr31bF2MXBxCAisYJU7s2ckIUzSzbw5UYhajRNeCSSwQzndGiclzl7CA VAkL+Eu8+3gWrEpEYCeLxLrH/awQVc2MElcmL2AHqWIT0JeY/ngbG4jNK6AlsfpuD1g3i4Cq xJ6pp8H2iQpESEyc0MAKUSMo8WPyPbAaTgF3iaM3pzN3MXJwMAvoSdy/qAUSZhaQl9i85i0z yC4JgZUcEge6JjNBzBSQ+Db5EAtIvYSArMSmA8wQ70hKHFxxg2UCo+gsJBtmIUydhWTqAkbm VYyiqQXJBcVJ6UVGesWJucWleel6yfm5mxiBUX7637O+HYw3D1gfYhTgYFTi4W346xkmxJpY VlyZe4jRFOiIicxSosn5wFSSVxJvaGxmZGFqYmpsZG5ppiTOmyD1M1hIID2xJDU7NbUgtSi+ qDQntfgQIxMHp1QDY/yE6furV7K1bGjdrJLXOpNdpqbydvXVuPnezZmhSuLvts2/ZOi5gVt0 nXxZ/Oxdy6039RzctXh6rto7Wa1VomrLdk2YVZKcIOHf7R0TbRv0qpYxvjPq944j6vveC0ap z9k1N1jHOrglVHHahNd7pZ/tUk65l8AjEHtFbt0LgSvCOSdfM7PEKLEUZyQaajEXFScCABTi N4TtAgAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOKsWRmVeSWpSXmKPExsVy+t9jQd3Va73CDFrfa1j8nXSM3eL9sh5G i9cvDC36H79mtvh6eAWjxabH11gtPvbcY7W4vGsOm8WM8/uYLC6ecrU4df0zm8XhN+2sFj/O dLNYrNr1h9Hi5ccTLA78HmvmrWH0+P1rEqPH+xut7B6X+3qZPHbOusvusWlVJ5vHnWt72Dw2 L6n3uHKiidWjb8sqRo/Pm+QCuKMaGG0yUhNTUosUUvOS81My89JtlbyD453jTc0MDHUNLS3M lRTyEnNTbZVcfAJ03TJzgF5RUihLzCkFCgUkFhcr6dthmhAa4qZrAdMYoesbEgTXY2SABhLW MGa0d/EU7BWpOHF1PVMD42TBLkZODgkBE4mZfXPYIGwxiQv31gPZXBxCArMYJboWTGKBcL4z Skyeu4QFpEpYwF/i3cezYFUiAjtZJNY97meFqGpmlLgyeQE7SBWbgL7E9MfbwObyCmhJrL7b A9bNIqAqsWfqaUYQW1QgQmLihAZWiBpBiR+T74HVcAq4Sxy9OZ25i5GDg1lAT+L+RS2QMLOA vMTmNW+ZJzDyz0LSMQuhahaSqgWMzKsYJVILkguKk9JzDfNSy/WKE3OLS/PS9ZLzczcxghPJ M6kdjAd3uR9iFOBgVOLhbfjrGSbEmlhWXJl7iFGCg1lJhJdthVeYEG9KYmVValF+fFFpTmrx IUZToDcmMkuJJucDk1xeSbyhsYm5qbGppYmFiZmlkjivvqdRmJBAemJJanZqakFqEUwfEwen VAMj26MV8tKKzE/PxL1Xe6xwT3/BX9WEjlBOaTv73cvd+1P7H1k/2WxbzLU4pObkq78fVSaJ azjpy+ySyAjNnT/PO7sqcKlU1OV1N/vnnLnstGnT3yvFLzaY7964t+J+jFpw7lvH9dfOX4sW Lrp1Zt6btBVPG+4LbT73SY8/5ErVRn7WlxO0I17dV2Ipzkg01GIuKk4EANXxG6M6AwAA DLP-Filter: Pass X-MTR: 20000000000000000@CPGS X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2796 Lines: 79 On Monday 16 November 2015 07:06 AM, 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 build clock drivers only for respective SoC's architecture. > > Signed-off-by: Krzysztof Kozlowski > --- > drivers/clk/samsung/Kconfig | 13 +++++++++++++ > drivers/clk/samsung/Makefile | 4 ++-- > 2 files changed, 15 insertions(+), 2 deletions(-) > > diff --git a/drivers/clk/samsung/Kconfig b/drivers/clk/samsung/Kconfig > index 84196ecdaa12..5f138fc4d84d 100644 > --- a/drivers/clk/samsung/Kconfig > +++ b/drivers/clk/samsung/Kconfig > @@ -2,6 +2,7 @@ config COMMON_CLK_SAMSUNG > bool > select COMMON_CLK > > +# ARMv7 SoCs: > config S3C2410_COMMON_CLK > bool > select COMMON_CLK_SAMSUNG > @@ -24,3 +25,15 @@ config S3C2443_COMMON_CLK > bool > select COMMON_CLK_SAMSUNG > > +# ARMv8 SoCs: > +config EXYNOS5433_COMMON_CLK > + bool > + depends on ARM64 || COMPILE_TEST > + default ARCH_EXYNOS > + select COMMON_CLK_SAMSUNG > + > +config EXYNOS7_COMMON_CLK > + bool > + depends on ARM64 || COMPILE_TEST > + default ARCH_EXYNOS > + select COMMON_CLK_SAMSUNG > diff --git a/drivers/clk/samsung/Makefile b/drivers/clk/samsung/Makefile > index 5f6833ea355d..a31332a24ef4 100644 > --- a/drivers/clk/samsung/Makefile > +++ b/drivers/clk/samsung/Makefile > @@ -10,11 +10,11 @@ obj-$(CONFIG_SOC_EXYNOS5250) += clk-exynos5250.o > obj-$(CONFIG_SOC_EXYNOS5260) += clk-exynos5260.o > obj-$(CONFIG_SOC_EXYNOS5410) += clk-exynos5410.o > obj-$(CONFIG_SOC_EXYNOS5420) += clk-exynos5420.o > -obj-$(CONFIG_ARCH_EXYNOS) += clk-exynos5433.o > +obj-$(CONFIG_EXYNOS5433_COMMON_CLK) += clk-exynos5433.o > obj-$(CONFIG_SOC_EXYNOS5440) += clk-exynos5440.o > obj-$(CONFIG_ARCH_EXYNOS) += clk-exynos-audss.o > obj-$(CONFIG_ARCH_EXYNOS) += clk-exynos-clkout.o > -obj-$(CONFIG_ARCH_EXYNOS7) += clk-exynos7.o > +obj-$(CONFIG_EXYNOS7_COMMON_CLK) += clk-exynos7.o > obj-$(CONFIG_S3C2410_COMMON_CLK)+= clk-s3c2410.o > obj-$(CONFIG_S3C2410_COMMON_DCLK)+= clk-s3c2410-dclk.o > obj-$(CONFIG_S3C2412_COMMON_CLK)+= clk-s3c2412.o > So in this approach we need to add separate config for clock support of each ARM64 Exynos64 SoC. Is this fine? Can we club compilation of each ARM64 Exynos SoC clock file under EXYNOS7_COMMON_CLK? As for all ARM64 SoC there is single defconfig and binary. Thanks, Pankaj Dubey -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/