From: Krzysztof Kozlowski <krzk@kernel.org>
To: Maulik Shah <maulik.shah@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Linus Walleij <linusw@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Sneh Mankad <sneh.mankad@oss.qualcomm.com>
Subject: Re: [PATCH 2/5] dt-bindings: interrupt-controller: qcom,pdc: Document reg and QMP
Date: Fri, 13 Mar 2026 14:55:14 +0100 [thread overview]
Message-ID: <20260313-hungry-mini-magpie-db50de@quoll> (raw)
In-Reply-To: <20260312-hamoa_pdc-v1-2-760c8593ce50@oss.qualcomm.com>
On Thu, Mar 12, 2026 at 09:26:36PM +0530, Maulik Shah wrote:
> Document PDC reg to configure pass through or secondary controller mode
> for GPIO IRQs.
> Document QMP handle for action concerning global resources.
Don't explain what you did. We can read the diff. Explain WHY you are
doing this.
>
> Signed-off-by: Maulik Shah <maulik.shah@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml b/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
> index 5ad68b2c6fc630fb4044c7224e6791d3bf4c2937..00eb9b28170c29c811c17b1f02f1f4f14779752f 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
> @@ -62,6 +62,7 @@ properties:
> items:
> - description: PDC base register region
> - description: Edge or Level config register for SPI interrupts
> + - description: PDC config for pass through or secondary IRQ mode for GPIOs
I do not understand why all devices have suddenly grown one more MMIO
region, including devices for few years in the market. Nothing in commit
msg helped me to understand that.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-13 13:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 15:56 [PATCH 0/5] x1e80100: Enable PDC wake GPIOs and deepest idle state Maulik Shah
2026-03-12 15:56 ` [PATCH 1/5] arm64: dts: qcom: x1e80100: Remove interconnect from SCM device Maulik Shah
2026-03-13 2:11 ` Dmitry Baryshkov
2026-03-13 10:12 ` Maulik Shah (mkshah)
2026-03-13 11:59 ` Konrad Dybcio
2026-03-13 14:48 ` Dmitry Baryshkov
2026-03-16 9:39 ` Konrad Dybcio
2026-03-16 14:25 ` Dmitry Baryshkov
2026-03-18 9:33 ` Konrad Dybcio
2026-03-18 10:38 ` Dmitry Baryshkov
2026-03-18 10:39 ` Konrad Dybcio
2026-03-18 14:23 ` Dmitry Baryshkov
2026-03-13 15:17 ` Maulik Shah (mkshah)
2026-03-13 14:47 ` Dmitry Baryshkov
2026-03-13 13:56 ` Krzysztof Kozlowski
2026-03-16 4:32 ` Maulik Shah (mkshah)
2026-03-12 15:56 ` [PATCH 2/5] dt-bindings: interrupt-controller: qcom,pdc: Document reg and QMP Maulik Shah
2026-03-13 13:55 ` Krzysztof Kozlowski [this message]
2026-03-12 15:56 ` [PATCH 3/5] irqchip/qcom-pdc: Configure PDC to pass through mode Maulik Shah
2026-03-13 2:22 ` Dmitry Baryshkov
2026-03-13 6:40 ` Maulik Shah (mkshah)
2026-03-13 11:49 ` Konrad Dybcio
2026-03-24 2:52 ` Bjorn Andersson
2026-03-12 15:56 ` [PATCH 4/5] arm64: dts: qcom: x1e80100: Add deepest idle state Maulik Shah
2026-03-13 2:30 ` Dmitry Baryshkov
2026-03-13 6:41 ` Maulik Shah (mkshah)
2026-03-13 13:57 ` Krzysztof Kozlowski
2026-03-16 4:36 ` Maulik Shah (mkshah)
2026-03-12 15:56 ` [PATCH 5/5] Revert "pinctrl: qcom: x1e80100: Bypass PDC wakeup parent for now" Maulik Shah
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=20260313-hungry-mini-magpie-db50de@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maulik.shah@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sneh.mankad@oss.qualcomm.com \
--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