From: Chancel Liu <chancel.liu@oss.nxp.com>
To: Rob Herring <robh@kernel.org>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org, Frank.Li@nxp.com,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/4] dt-bindings: connector: Add fsl,aud-io-slot binding
Date: Mon, 16 Nov 2026 16:14:26 +0800 [thread overview]
Message-ID: <dd68ae61-9dfd-4138-acf5-b77c63ba0fa3@oss.nxp.com> (raw)
In-Reply-To: <20261112225328.GA1784283-robh@kernel.org>
On 11/13/2026 6:53 AM, Rob Herring wrote:
> On Thu, Nov 05, 2026 at 03:41:14PM +0900, Chancel Liu wrote:
>> From: Chancel Liu <chancel.liu@nxp.com>
>>
>> The NXP AUD-IO slot represents a physically present I/O connector on
>> the base board. It acts as a nexus that exposes a constrained set of
>> I/O resources, such as GPIOs, clocks and interrupts, through fixed
>> electrical wiring. All actual hardware providers reside on the base
>> board. The connector node only defines index-based mappings to those
>> providers.
>>
>> This connector type is present on i.MX95 19x19 EVK and i.MX952 EVK,
>> where it is used to attach the IMX-AUD-IO audio expansion card[1]. The
>> same add-on board can be reused across different base boards that carry
>> this connector.
>>
>> [1]https://www.nxp.com/part/IMX-AUD-IO
>
> That link is pretty much useless. Is there a pinout definition
> somewhere?
>
The detailed user manual (UM12022) is listed as official documentation:
https://docs.nxp.com/bundle/UM12022/page/topics/pcie_interface1.html
But it is behind an NXP login.
The brief pinout table looks like this:
Pin Signal Dir
---- ------------------ ---
A11 PCI_AUD_RST_B In (GPIO)
A12 AUD_CARD_DET Out (INT)
A21 AUD_SPI7_SCLK In
A22 AUD_SPI7_SS0 In
A25 AUD_SPI7_MOSI In
A26 AUD_SPI7_MISO Out
A29 AUD_SPI7_SCLK In
A30 AUD_SPI7_SS0 In
A32 AUD_SPI7_MISO Out
A33 AUD_SPI7_MOSI In
B5 I2C6_SCL_1V8 In
B6 I2C6_SDA_1V8 I/O
B10 AUD_SLOT_PWR_SYNC In (GPIO)
B11 AUD_SLOT_PWRDN In (GPIO)
B12 AUD_SLOT_MCLK In (CLK)
B14 AUD_SLOT_INT_B Out (INT)
B15 AUD_SLOT_INT_B Out
B17 AUD_SLOT_INT_B Out
B23 SAI2_RXFS Out
B24 SAI2_RXC Out
B27 SAI2_TXD1 In
B28 SAI2_TXD2 In
B30 SAI2_TXD3 In
B31 SAI2_RXD1 Out
A2, A3, B1, B2, B3 VCC_EXT_12V0
B8, A9, A10 VCC_EXT_3V3
> Looking at the overlay, this looks incomplete. It looks like there's I2C
> thru the connector for example. There's also power rails.
>
> The idea with connectors is that overlays apply to the connector node
> and nothing else.
For this patch set, I2C, I2S and regulators are
provided by the base boards using a common set of labels:
aud_io_i2c
aud_io_cpu
aud_io_reg_1v8
aud_io_reg_3v3
aud_io_reg_5v
The common add-on board overlay references these labels directly. This
allows the same overlay to be used with both base boards. But the
overlay still depends on nodes outside the connector.
> I2C we've kind of figured out with something like this:
>
> connector {
> i2c-parent = <&i2c>;
> i2c {
> ...
> };
> };
>
I will rework the I2C part using this model.
> Regulators is still open issue though.
>
> Rob
Good to know this is being discussed. Is there a mailing-list thread or
patch series I can follow?
Regards,
Chancel Liu
next prev parent reply other threads:[~2026-11-16 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 6:41 [PATCH v4 0/4] arm64: dts: freescale: Add IMX-AUD-IO add-on board support Chancel Liu
2026-11-05 6:41 ` [PATCH v4 1/4] dt-bindings: connector: Add fsl,aud-io-slot binding Chancel Liu
2026-11-05 6:59 ` sashiko-bot
2026-11-12 22:53 ` Rob Herring
2026-11-16 8:14 ` Chancel Liu [this message]
2026-11-05 6:41 ` [PATCH v4 2/4] arm64: dts: freescale: imx95-19x19-evk: Add IMX-AUD-IO board support Chancel Liu
2026-11-05 6:41 ` [PATCH v4 3/4] arm64: dts: freescale: imx952-evk: " Chancel Liu
2026-11-05 6:41 ` [PATCH v4 4/4] arm64: dts: freescale: Add common DTS overlay for IMX-AUD-IO add-on board Chancel Liu
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=dd68ae61-9dfd-4138-acf5-b77c63ba0fa3@oss.nxp.com \
--to=chancel.liu@oss.nxp.com \
--cc=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 \
/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