From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0286DCD4851 for ; Tue, 19 May 2026 08:30:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=BgPCaNIp6cXg7H8i3l88afg4FdmSZ+4Qva7L8NFIvcw=; b=oBp8XUupE5Cqt401EqAVM9h0zR UJtMuH7ZnMydQiXp+b1KkSYjUiSLMmEmosvN+DBmNqIjivfSOucY+F+39uYaoMZY9CIHMVzJzbBCJ Zhr+lAW4UwZIHSZ4JJKkFz0LPqwqNI2k/fg7rcIHE11hHOQrJZ16vo4qzA6Jrd3+SeBHOWRU7oM/x /8rbM6uMiNANYsBDI7yEFDTjC26lH9sfWOC1MR4Kr4eFLOec0tHbg2N+9AsaaGrhcONLlaBen1iMW TPysNNx9+huDjEfjis9n3ZdfX5+fSN0E9VG+od6cE7mZW7tcgcWUezJzs/lFTtc0J3B7xPCgY9sGT 0fsbHARA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wPFpr-00000000gCz-2OEm; Tue, 19 May 2026 08:29:55 +0000 Received: from tor.source.kernel.org ([172.105.4.254]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wPFpq-00000000gCd-2W5D for linux-arm-kernel@lists.infradead.org; Tue, 19 May 2026 08:29:54 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id B5223600AE; Tue, 19 May 2026 08:29:53 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DBF03C2BCB3; Tue, 19 May 2026 08:29:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1779179393; bh=sxi4Nd3428EAjrfiX0HNjbsVsdPmFrqLWCGIPz6abEI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=N0cgEBogM3z+HeA/OXJOJ2GxWoPy8vgw4rkhTieDJOdOOcdM6JqbMBZAhJxziSrrR ZiVCL98OhiOOQF714K+o0uEE3cwuOqTQc6jFtALsCuHLI3rHX9N+RjM7DPIucbLyIs TKTz8Yt21LLhJdLZ+aJ08Oe9LEQlKudXiKniDXktGDayEp9ef88qx4VWsJtD2Hd3K0 8TxhN5l9nFsCd4TplzqT9ZaMvIlwkrSnTzd4jbEwHtacuzSvI+m90o6HH6b7m2wTMq lQJFknLZNhTFDNYHkmqM/Tpd+Fr+xxdoIc/ofp9F8AE7daqpTM2aVcGfRApQG837fr 7cf/QlG7APnhQ== Date: Tue, 19 May 2026 10:29:50 +0200 From: Krzysztof Kozlowski To: Chancel Liu Cc: "robh@kernel.org" , "krzk+dt@kernel.org" , "conor+dt@kernel.org" , Frank Li , "s.hauer@pengutronix.de" , "festevam@gmail.com" , "mturquette@baylibre.com" , "sboyd@kernel.org" , "kernel@pengutronix.de" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "imx@lists.linux.dev" , "linux-arm-kernel@lists.infradead.org" , "linux-clk@vger.kernel.org" , "Chancel Liu (OSS)" Subject: Re: [PATCH 2/5] dt-bindings: connector: Add fsl,io-connector binding Message-ID: <20260519-macho-degu-from-nibiru-960af2@quoll> References: <20260509024846.2094049-1-chancel.liu@nxp.com> <20260509024846.2094049-3-chancel.liu@nxp.com> <20260515-resourceful-singing-roadrunner-ce25ec@quoll> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org 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