From: Frank Li <Frank.li@nxp.com>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com,
kernel@pengutronix.de, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] arm64: dts: imx93-evk/qsb: add m2-pcm-level-shifter-hog to enable BT HFP
Date: Thu, 22 Jan 2026 09:35:50 -0500 [thread overview]
Message-ID: <aXI1xgnkarGS0Min@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260121111346.2598783-1-sherry.sun@nxp.com>
On Wed, Jan 21, 2026 at 07:13:46PM +0800, Sherry Sun wrote:
> For i.MX93 11x11 EVK and 9x9 QSB boards, add the gpio-hog to enable the
> M.2 PCM pins level shifter connected between soc sai1 interface and M.2
> PCM pins so that HFP feature can be supported.
>
> Since the HFP is only used at a later stage — after the BT firmware has
> been downloaded and the BT connection with the remote device has been
> established — both the pcal6524 expander and sai1 interface are already
> fully initialized and available by that time. Therefore, using a
> gpio-hog here will not introduce any probe ordering or dependency issues
> for the HFP use case.
>
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> Changes in V2:
> 1. Improve the commit message to avoid confusion.
> ---
> arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts | 6 ++++++
> arch/arm64/boot/dts/freescale/imx93-9x9-qsb.dts | 6 ++++++
> 2 files changed, 12 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts b/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts
> index 8dd5340e8141..acb160d3186c 100644
> --- a/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts
> @@ -356,6 +356,12 @@ pcal6524: gpio@22 {
> #interrupt-cells = <2>;
> interrupt-parent = <&gpio3>;
> interrupts = <27 IRQ_TYPE_LEVEL_LOW>;
> +
> + m2-pcm-level-shifter-hog {
> + gpio-hog;
> + gpios = <19 GPIO_ACTIVE_HIGH>;
> + output-high;
> + };
> };
>
> pmic@25 {
> diff --git a/arch/arm64/boot/dts/freescale/imx93-9x9-qsb.dts b/arch/arm64/boot/dts/freescale/imx93-9x9-qsb.dts
> index 0852067eab2c..11e08673083b 100644
> --- a/arch/arm64/boot/dts/freescale/imx93-9x9-qsb.dts
> +++ b/arch/arm64/boot/dts/freescale/imx93-9x9-qsb.dts
> @@ -349,6 +349,12 @@ mic-can-sel-hog {
> gpios = <17 GPIO_ACTIVE_HIGH>;
> output-low;
> };
> +
> + m2-pcm-level-shifter-hog {
> + gpio-hog;
> + gpios = <19 GPIO_ACTIVE_HIGH>;
> + output-high;
> + };
> };
>
> pmic@25 {
> --
> 2.37.1
>
next prev parent reply other threads:[~2026-01-22 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 11:13 [PATCH V2] arm64: dts: imx93-evk/qsb: add m2-pcm-level-shifter-hog to enable BT HFP Sherry Sun
2026-01-22 8:53 ` Peng Fan
2026-01-22 14:35 ` Frank Li [this message]
2026-02-24 16:43 ` Frank Li
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=aXI1xgnkarGS0Min@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sherry.sun@nxp.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