From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: k.kozlowski.k@gmail.com,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
linux-clk@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>, Kukjin Kim <kgene@kernel.org>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Kevin Hilman <khilman@linaro.org>,
Pankaj Dubey <pankaj.dubey@samsung.com>
Subject: Re: [PATCH 1/2] clk: samsung: Don't build ARMv8 clock drivers on ARMv7
Date: Thu, 19 Nov 2015 18:41:16 +0900 [thread overview]
Message-ID: <564D993C.4090104@samsung.com> (raw)
In-Reply-To: <CA+Ln22GTPFk6KpWZPDzLRBqO8B+iwwesQEzBwYikXnf0gr3Csg@mail.gmail.com>
W dniu 19.11.2015 o 18:16, Tomasz Figa pisze:
> 2015-11-19 13:51 GMT+09:00 Krzysztof Kozlowski <k.kozlowski@samsung.com>:
>> On 19.11.2015 13:18, Tomasz Figa wrote:
>>> However, I don't think we can disable compilation of particular 64-bit
>>> SoCs, so maybe there isn't much sense in splitting their clock drivers
>>> into separate symbols?
>>
>> To me it does not really matter. Indeed as you said one cannot disable
>> building of one particular Exynos SoCs.
>>
>> However we could still want not build some parts of such SoCs (like
>> clock, pinctrl etc). I don't see much benefit for such case except when
>> someone would like to drastically reduce the size of kernel image (for
>> whatever reasons he has.).
>
> Can we really build a kernel that support selected Exynos SoC without
> its clock driver? Actually I don't think we even allow deselecting
> clock drivers currently, because they are not visible in menuconfig.
> Unless there is a clear goal to separate ARCH level Kconfig symbol for
> particular ARM64-based Exynos SoCs, I don't think it makes any sense
> to keep the clock-related symbols separate.
That is reasonable and very convincing. I'll wait for Sylwester reply
before re-spinning.
BR,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: samsung: Don't build ARMv8 clock drivers on ARMv7
Date: Thu, 19 Nov 2015 18:41:16 +0900 [thread overview]
Message-ID: <564D993C.4090104@samsung.com> (raw)
In-Reply-To: <CA+Ln22GTPFk6KpWZPDzLRBqO8B+iwwesQEzBwYikXnf0gr3Csg@mail.gmail.com>
W dniu 19.11.2015 o 18:16, Tomasz Figa pisze:
> 2015-11-19 13:51 GMT+09:00 Krzysztof Kozlowski <k.kozlowski@samsung.com>:
>> On 19.11.2015 13:18, Tomasz Figa wrote:
>>> However, I don't think we can disable compilation of particular 64-bit
>>> SoCs, so maybe there isn't much sense in splitting their clock drivers
>>> into separate symbols?
>>
>> To me it does not really matter. Indeed as you said one cannot disable
>> building of one particular Exynos SoCs.
>>
>> However we could still want not build some parts of such SoCs (like
>> clock, pinctrl etc). I don't see much benefit for such case except when
>> someone would like to drastically reduce the size of kernel image (for
>> whatever reasons he has.).
>
> Can we really build a kernel that support selected Exynos SoC without
> its clock driver? Actually I don't think we even allow deselecting
> clock drivers currently, because they are not visible in menuconfig.
> Unless there is a clear goal to separate ARCH level Kconfig symbol for
> particular ARM64-based Exynos SoCs, I don't think it makes any sense
> to keep the clock-related symbols separate.
That is reasonable and very convincing. I'll wait for Sylwester reply
before re-spinning.
BR,
Krzysztof
next prev parent reply other threads:[~2015-11-19 9:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 1:36 [PATCH 0/2] arm64: EXYNOS: Consolidate Exynos7 symbol Krzysztof Kozlowski
2015-11-16 1:36 ` Krzysztof Kozlowski
2015-11-16 1:36 ` [PATCH 1/2] clk: samsung: Don't build ARMv8 clock drivers on ARMv7 Krzysztof Kozlowski
2015-11-16 1:36 ` Krzysztof Kozlowski
2015-11-16 3:05 ` Chanwoo Choi
2015-11-16 3:05 ` Chanwoo Choi
2015-11-16 3:05 ` Chanwoo Choi
2015-11-17 4:31 ` pankaj.dubey
2015-11-17 4:31 ` pankaj.dubey
2015-11-17 4:39 ` Krzysztof Kozlowski
2015-11-17 4:39 ` Krzysztof Kozlowski
2015-11-17 14:01 ` Sylwester Nawrocki
2015-11-17 14:01 ` Sylwester Nawrocki
2015-11-19 4:10 ` [1/2] " Alim Akhtar
2015-11-19 4:10 ` Alim Akhtar
2015-11-19 4:18 ` [PATCH 1/2] " Tomasz Figa
2015-11-19 4:18 ` Tomasz Figa
2015-11-19 4:18 ` Tomasz Figa
2015-11-19 4:51 ` Krzysztof Kozlowski
2015-11-19 4:51 ` Krzysztof Kozlowski
2015-11-19 9:16 ` Tomasz Figa
2015-11-19 9:16 ` Tomasz Figa
2015-11-19 9:41 ` Krzysztof Kozlowski [this message]
2015-11-19 9:41 ` Krzysztof Kozlowski
2015-11-19 11:05 ` Sylwester Nawrocki
2015-11-19 11:05 ` Sylwester Nawrocki
2015-11-16 1:36 ` [PATCH 2/2] arm64: EXYNOS: Consolidate ARCH_EXYNOS7 symbol into ARCH_EXYNOS Krzysztof Kozlowski
2015-11-16 1:36 ` Krzysztof Kozlowski
2015-11-16 2:55 ` Chanwoo Choi
2015-11-16 2:55 ` Chanwoo Choi
2015-11-16 2:55 ` Chanwoo Choi
2015-11-16 2:55 ` Chanwoo Choi
2015-11-17 4:25 ` pankaj.dubey
2015-11-17 4:25 ` pankaj.dubey
2015-11-19 4:04 ` [2/2] " Alim Akhtar
2015-11-19 4:04 ` Alim Akhtar
2015-11-19 4:23 ` [PATCH 2/2] " Tomasz Figa
2015-11-19 4:23 ` Tomasz Figa
2015-11-19 4:36 ` Krzysztof Kozlowski
2015-11-19 4:36 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=564D993C.4090104@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=k.kozlowski.k@gmail.com \
--cc=kgene@kernel.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=pankaj.dubey@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@codeaurora.org \
--cc=tomasz.figa@gmail.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.