From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH 2/2] clk: qcom: restrict drivers per ARM/ARM64
Date: Wed, 25 Jan 2023 12:44:07 -0800 [thread overview]
Message-ID: <7ddf5c74de84c5dc291996423cb1eb46.sboyd@kernel.org> (raw)
In-Reply-To: <20230123094925.54824-2-krzysztof.kozlowski@linaro.org>
Quoting Krzysztof Kozlowski (2023-01-23 01:49:25)
> There is no point to allow selecting pin-controller drivers for Qualcomm
pin controllers?
> ARMv7 SoCs when building ARM64 kernel, and vice versa. This makes
> kernel configuration more difficult as many do not remember the Qualcomm
> SoCs model names/numbers. There won't be a single image for ARMv7 and
> ARMv8/9 SoCs, so no features/options are lost.
Are the drivers used in arm32 emulation mode on these SoCs? I recall
there are some SoCs they run with the arm architecture.
next prev parent reply other threads:[~2023-01-25 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 9:49 [PATCH 1/2] clk: qcom: add compile test to MSM8996 CPU clocks Krzysztof Kozlowski
2023-01-23 9:49 ` [PATCH 2/2] clk: qcom: restrict drivers per ARM/ARM64 Krzysztof Kozlowski
2023-01-23 12:31 ` Konrad Dybcio
2023-01-23 12:45 ` Krzysztof Kozlowski
2023-01-23 12:47 ` Konrad Dybcio
2023-01-25 20:44 ` Stephen Boyd [this message]
2023-01-26 9:31 ` Krzysztof Kozlowski
2023-01-30 23:30 ` Stephen Boyd
2023-02-01 7:12 ` Krzysztof Kozlowski
2023-02-10 22:32 ` Stephen Boyd
2023-02-11 11:19 ` Krzysztof Kozlowski
2023-01-23 12:32 ` [PATCH 1/2] clk: qcom: add compile test to MSM8996 CPU clocks Konrad Dybcio
2023-01-23 14:35 ` kernel test robot
2023-01-23 20:22 ` 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=7ddf5c74de84c5dc291996423cb1eb46.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.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.