From: Nishanth Menon <nm@ti.com>
To: Jai Luthra <j-luthra@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Esteban Blanc <eblanc@baylibre.com>, <jneanne@baylibre.com>,
<aseketeli@baylibre.com>, <jpanis@baylibre.com>,
<u-kumar1@ti.com>
Subject: Re: [PATCH v5 4/6] arm64: dts: ti: k3-j784s4-evm: Fix interrupt ranges for TPS6594 PMIC
Date: Wed, 9 Aug 2023 10:27:30 -0500 [thread overview]
Message-ID: <20230809152730.6pbb4fze6pv55gye@trapper> (raw)
In-Reply-To: <20230809-tps6594-v5-4-485fd3d63670@ti.com>
$subject is wrong.
On 20:17-20230809, Jai Luthra wrote:
> From: Apelete Seketeli <aseketeli@baylibre.com>
>
> This patch fixes the interrupt range for TPS6594 PMIC on MCU/WAKEUP
> domain for RTC peripheral.
>
This needs to be rephrased - interrupt map for gpio wakeup interrupt
controller is mapped in-correctly rather than indicating what caught the
bug in the SoC description.
Also missing:
Fixes: 4664ebd8346a ("arm64: dts: ti: Add initial support for J784S4 SoC")
> Signed-off-by: Apelete Seketeli <aseketeli@baylibre.com>
> Signed-off-by: Esteban Blanc <eblanc@baylibre.com>
> Signed-off-by: Jai Luthra <j-luthra@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi
> index 740ee794d7b9..77a45f97e28b 100644
> --- a/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi
> @@ -107,7 +107,7 @@ wkup_gpio_intr: interrupt-controller@42200000 {
> #interrupt-cells = <1>;
> ti,sci = <&sms>;
> ti,sci-dev-id = <177>;
> - ti,interrupt-ranges = <16 928 16>;
> + ti,interrupt-ranges = <16 960 16>;
> };
>
> /* MCU_TIMERIO pad input CTRLMMR_MCU_TIMER*_CTRL registers */
>
> --
> 2.41.0
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-08-09 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 14:47 [PATCH v5 0/6] Add TPS6594 PMIC support on several boards Jai Luthra
2023-08-09 14:47 ` [PATCH v5 1/6] arm64: dts: ti: k3-j7200-som-p0: Add TP6594 family PMICs Jai Luthra
2023-08-09 16:19 ` Nishanth Menon
2023-08-09 14:47 ` [PATCH v5 2/6] arm64: dts: ti: k3-j721s2-som-p0: " Jai Luthra
2023-08-09 14:47 ` [PATCH v5 3/6] arm64: dts: ti: k3-j721e-som-p0: " Jai Luthra
2023-08-09 14:47 ` [PATCH v5 4/6] arm64: dts: ti: k3-j784s4-evm: Fix interrupt ranges for TPS6594 PMIC Jai Luthra
2023-08-09 15:27 ` Nishanth Menon [this message]
2023-08-09 14:47 ` [PATCH v5 5/6] arm64: dts: ti: k3-j784s4-evm: Add support " Jai Luthra
2023-08-09 14:47 ` [PATCH v5 6/6] arm64: dts: ti: k3-am62a7-sk: Add support for TPS6593 PMIC Jai Luthra
2023-08-09 15:34 ` [PATCH v5 0/6] Add TPS6594 PMIC support on several boards Nishanth Menon
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=20230809152730.6pbb4fze6pv55gye@trapper \
--to=nm@ti.com \
--cc=aseketeli@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eblanc@baylibre.com \
--cc=j-luthra@ti.com \
--cc=jneanne@baylibre.com \
--cc=jpanis@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).