mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Thomas Gleixner <tglx@kernel.org>, Radu Rendec <radu@rendec.net>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/3] irqchip/qcom: Enable compile testing for QCOM_PDC and QCOM_MPM
Date: Mon, 27 Jul 2026 14:00:16 +0200	[thread overview]
Message-ID: <bc71b5d4-7ea4-4c84-9cf4-b26827a3f4d9@oss.qualcomm.com> (raw)
In-Reply-To: <20260727-irqchip-qcom-defaults-v1-1-ed80ad83ca53@oss.qualcomm.com>

On 7/27/26 1:44 PM, Krzysztof Kozlowski wrote:
> QCOM_PDC and QCOM_MPM do not reference any architecture code, thus
> should be compile-testable.  QCOM_MPM is used only on ARM64 SoCs, thus
> there is no point in proposing this option for 32-bit Qualcomm platforms
> making kernel configurators life easier.

This is only because no one wired it up, almost/all 32-bit SoCs
have one too

Konrad

  reply	other threads:[~2026-07-27 12:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 11:44 [PATCH 0/3] irqchip: qcom: Add sane defaults and drop defconfig Krzysztof Kozlowski
2026-07-27 11:44 ` [PATCH 1/3] irqchip/qcom: Enable compile testing for QCOM_PDC and QCOM_MPM Krzysztof Kozlowski
2026-07-27 12:00   ` Konrad Dybcio [this message]
2026-07-27 12:08     ` Krzysztof Kozlowski
2026-07-27 12:31   ` Mukesh Ojha
2026-07-27 12:41     ` Krzysztof Kozlowski
2026-07-27 11:44 ` [PATCH 2/3] irqchip/qcom: Add defaults for desired arm64 drivers Krzysztof Kozlowski
2026-07-27 11:44 ` [PATCH 3/3] arm64: defconfig: Drop redundant Qualcomm irqchip entries 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=bc71b5d4-7ea4-4c84-9cf4-b26827a3f4d9@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=radu@rendec.net \
    --cc=tglx@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®