From: "Arnd Bergmann" <arnd@arndb.de>
To: "Judith Mendez" <jm@ti.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>
Cc: "Bjorn Andersson" <bjorn.andersson@oss.qualcomm.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Dmitry Baryshkov" <lumag@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Nishanth Menon" <nm@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>
Subject: Re: [PATCH] arm64: defconfig: Enable hwspinlock and eQEP for K3
Date: Tue, 22 Apr 2025 08:37:23 +0200 [thread overview]
Message-ID: <55d306d4-c9cd-4119-8798-b65a6956f4df@app.fastmail.com> (raw)
In-Reply-To: <20250421201055.3889680-1-jm@ti.com>
On Mon, Apr 21, 2025, at 22:10, Judith Mendez wrote:
> Enable CONFIG_HWSPINLOCK_OMAP to allow usage of these devices
> across K3 SoC's. Also enable CONFIG_TI_EQEP which is enabled by
> default on am64x SK board.
>
> Signed-off-by: Judith Mendez <jm@ti.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
The patch seems fine to me, but you should address it at the
TI K3 maintainers, so they know they should apply it and forward
it to the SoC tree. You have Nishanth and Vignesh in Cc already,
so I assume they will pick it up from here, just put them in
'To' instead next time and move Catalin and Will to 'Cc' or
leave them off entirely.
> ---
> arch/arm64/configs/defconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 9e16b494ab0e2..1f7b97ff46a7e 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -1415,6 +1415,7 @@ CONFIG_CLK_GFM_LPASS_SM8250=m
> CONFIG_CLK_RCAR_USB2_CLOCK_SEL=y
> CONFIG_CLK_RENESAS_VBATTB=m
> CONFIG_HWSPINLOCK=y
> +CONFIG_HWSPINLOCK_OMAP=m
> CONFIG_HWSPINLOCK_QCOM=y
> CONFIG_TEGRA186_TIMER=y
> CONFIG_RENESAS_OSTM=y
> @@ -1676,6 +1677,7 @@ CONFIG_INTERCONNECT_QCOM_SM8650=y
> CONFIG_INTERCONNECT_QCOM_SM8750=y
> CONFIG_INTERCONNECT_QCOM_X1E80100=y
> CONFIG_COUNTER=m
> +CONFIG_TI_EQEP=m
> CONFIG_RZ_MTU3_CNT=m
> CONFIG_HTE=y
> CONFIG_HTE_TEGRA194=y
> --
> 2.49.0
next prev parent reply other threads:[~2025-04-22 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 20:10 [PATCH] arm64: defconfig: Enable hwspinlock and eQEP for K3 Judith Mendez
2025-04-22 6:37 ` Arnd Bergmann [this message]
2025-04-22 14:15 ` Judith Mendez
2025-04-22 14:22 ` Nishanth Menon
2025-04-22 14:23 ` Judith Mendez
2025-04-25 21:13 ` 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=55d306d4-c9cd-4119-8798-b65a6956f4df@app.fastmail.com \
--to=arnd@arndb.de \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=jm@ti.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=nm@ti.com \
--cc=vigneshr@ti.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).