From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chancel Liu <chancel.liu@nxp.com>
Cc: "robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
Frank Li <frank.li@nxp.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"Chancel Liu (OSS)" <chancel.liu@oss.nxp.com>
Subject: Re: [PATCH 2/5] dt-bindings: connector: Add fsl,io-connector binding
Date: Tue, 19 May 2026 10:29:50 +0200 [thread overview]
Message-ID: <20260519-macho-degu-from-nibiru-960af2@quoll> (raw)
In-Reply-To: <AM9PR04MB83538C4A07A6835FF8A74793E3002@AM9PR04MB8353.eurprd04.prod.outlook.com>
On Tue, May 19, 2026 at 02:56:24AM +0000, Chancel Liu wrote:
> > >>> +description:
> > >>> + The NXP I/O connector 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, PWMs 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.
> > >>> +
> > >>> +properties:
> > >>> + compatible:
> > >>> + const: fsl,io-connector
> > >>
> > >> Everything is IO. Everything is connector, so your compatible does
> > >> not match requirements from writing bindings.
> > >>
> > >
> > > Yes, this compatible is too generic. I will rename the compatible to
> > > fsl,aud-io-connector.
> >
> > aud is not much better. Which boards have it? What's the pinout? What's
> > standard? Is it described anywhere? If so, provide reference to spec/docs.
> >
>
> This is not an industry standard electrical interface. This connector
Then if you do not have standard, then you have board specific layouts
thus you need board-specific compatibles. You can use fallbacks. Generic
fallback could work, but both io-connector and aud-io-connector are just
too generic. Every connector is "connector" and "io", thus absolutely
anything can be "io-connector". "aud" improves it only a bit, thus
honestly I would go with board specific fallback as well.
> is present on i.MX95-19x19-EVK and i.MX952-EVK. For example, the
> "i.MX 95 19mm x 19mm Evaluation Kit" homepage[1] publicly documents an
> audio board connection through which IMX-AUD-IO card is connected. The
> detailed user manual (UM12022) is listed as official documentation[2],
> but it is behind an NXP login, so it is not suitable as a public
> reference for upstream. Therefore I list it here to illustrate it's
> mechanism:
>
> +-----------------------------+
> | Base Board |
> | +-----+ +---------+ | +---------+
> | | SPI +------+ | | | |
> | +-----+ | | | GPIO MAP | |
> | | +--|-----------+ |
> | +-----+ | | | | |
> | | I2C +------+ | | | |
> | +-----+ | | | CLOCK MAP | AUD-IO |
> | |connector+--|-----------+ CARD |
> | +-----+ | | | | |
> | | I2S +------+ | | | |
> | +-----+ | | | | |
> | | | | INT MAP | |
> | +-----+ | +--|-----------+ |
> | | I/O +------+ | | | |
> | +-----+ +---------+ | +---------+
> +-----------------------------+
>
> [1]https://www.nxp.com/design/design-center/development-boards-and-designs/IMX95LPD5EVK-19
> [2]https://docs.nxp.com/bundle/UM12022/page/topics/pcie_interface1.html
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-19 8:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 2:48 [PATCH 0/5] arm64: dts: freescale: Add IMX-AUD-IO daughter board support Chancel Liu
2026-05-09 2:48 ` [PATCH 1/5] clk: Add support for clock nexus dt bindings Chancel Liu
2026-05-13 3:19 ` Chancel Liu
2026-05-09 2:48 ` [PATCH 2/5] dt-bindings: connector: Add fsl,io-connector binding Chancel Liu
2026-05-15 7:19 ` Krzysztof Kozlowski
2026-05-18 4:18 ` Chancel Liu
2026-05-18 7:07 ` Krzysztof Kozlowski
2026-05-19 2:56 ` Chancel Liu
2026-05-19 8:29 ` Krzysztof Kozlowski [this message]
2026-05-20 5:02 ` Chancel Liu (OSS)
2026-05-20 7:08 ` Krzysztof Kozlowski
2026-05-20 14:33 ` Frank Li
2026-05-24 18:20 ` Krzysztof Kozlowski
2026-05-25 6:26 ` Chancel Liu (OSS)
2026-05-25 12:28 ` Krzysztof Kozlowski
2026-06-02 22:18 ` Frank Li
2026-06-05 9:11 ` Krzysztof Kozlowski
2026-05-09 2:48 ` [PATCH 3/5] arm64: dts: freescale: imx95-19x19-evk: Add IMX-AUD-IO board support Chancel Liu
2026-05-09 2:48 ` [PATCH 4/5] arm64: dts: freescale: imx952-evk: " Chancel Liu
2026-05-11 8:20 ` Bough Chen
2026-05-13 5:50 ` Chancel Liu
2026-05-09 2:48 ` [PATCH 5/5] arm64: dts: freescale: Add common DTS overlay for IMX-AUD-IO daughter 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=20260519-macho-degu-from-nibiru-960af2@quoll \
--to=krzk@kernel.org \
--cc=chancel.liu@nxp.com \
--cc=chancel.liu@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@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