From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6F7D93DDDD9; Tue, 6 Oct 2026 18:02:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791309754; cv=none; b=aQowH6wbuTUyA4AAmAeAZm1hawGvSqOfWLgKeQrywUNfIiKkMGhpX0KjpzEKivAQe6YNf1IfLRaxfFhGYwcLEcyQL0KaN2BSnFOud76Ct4h+xUxp0ozRmFBOpS/mdgpi34PdAIgpKhGK1UFDE0WzYATH64KC5aQOSjE5fYf+vfo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791309754; c=relaxed/simple; bh=goVd4gDkeawuFXTB2jfoClWl7lU2fnOknBCv008N5b8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=gafSVUoWO7gyTR1kIxsSg0ZK9CHcy4k4jFLlpAWN8FOtRSmO47JmKrDuvIa5qfiHCwjn0uuB/qflxrBN2ivXqNvYolbFoJKQgklDFHKjUyPhw6VhQb3t2EIUXJOMjo1mwiyCm9lVztVL0lS4Z1MjGgRDbZSg/vn+HTUjmp79IQY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=BA52giKo; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="BA52giKo" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EE90D1F0089C; Tue, 6 Oct 2026 18:02:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791309753; bh=zn1cf/2G1XAfRKst7JuV3s2fqRbOiLvk8GIPBUJjUtg=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=BA52giKoyHfyhpCln4903eug87nhQVCKX/PDe97zkg8DEB4R5rpHLlYnmv0t2GvBO 14OnGPEbXZhitW8AiOs3NBNAXGkyrR3coRIEnc9SJ9CL52M1rpG/OexOUUbFfjTF7M 3z+i8ewsimtJ/aThbzYtD00P/7xe8Vb4qgOJNLjZjG/NomsjxRgUtG2D+OlJja2ZAx KGncZp8F7gyG/kHT3iRDTjhTlPGI0Y7sj6yUCdHMqc0llXONhqGoNJtO+GApmyFKKW 3uCKz6TB/SYBLBZj8q/8KQD+X9vdXVzmmO3fm0gq3BPnNKV7ssoeJBLfwlfUtDXc5K 5gxBj0lUizHKw== Date: Tue, 6 Oct 2026 13:02:32 -0500 From: Rob Herring To: Mathieu Poirier Cc: Shenwei Wang , Linus Walleij , Bartosz Golaszewski , Jonathan Corbet , Krzysztof Kozlowski , Conor Dooley , Bjorn Andersson , Frank Li , Sascha Hauer , Shuah Khan , linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Pengutronix Kernel Team , Fabio Estevam , Shenwei Wang , Peng Fan , devicetree@vger.kernel.org, linux-remoteproc@vger.kernel.org, imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com, Arnaud POULIQUEN , b-padhi@ti.com, Andrew Lunn Subject: Re: [PATCH v16 2/5] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support Message-ID: <20261006180047.GD2194299-robh@kernel.org> References: <20260923184255.299034-1-shenwei.wang@oss.nxp.com> <20260923184255.299034-3-shenwei.wang@oss.nxp.com> <20261006030739.GA3457522-robh@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Tue, Oct 06, 2026 at 09:18:23AM -0600, Mathieu Poirier wrote: > On Mon, 5 Oct 2026 at 21:07, Rob Herring wrote: > > > > On Wed, Sep 23, 2026 at 01:42:29PM -0500, Shenwei Wang wrote: > > > From: Shenwei Wang > > > > > > Remote processors may announce multiple GPIO controllers over an RPMSG > > > channel. These GPIO controllers may require corresponding device tree > > > nodes, especially when acting as providers, to supply phandles for their > > > consumers. > > > > > > Define an RPMSG node to work as a container for a group of RPMSG channels > > > under the imx_rproc node. Each subnode within "rpmsg" represents an > > > individual RPMSG channel. The name of each subnode corresponds to the > > > channel name as defined by the remote processor. > > > > Sorry, but DT defines the names of nodes. If it's a gpio-controller, > > then 'gpio'. > > > > I still don't understand where the unit address gets defined. 0 and 1 > > look a bit made up. I'm sure you explained it before, but *this patch* > > needs to explain it. When you define a second protocol, the 0 and 1 > > addresses are taken already, so you can't have 'clock-controller@0' for > > example. > > > > I had a conversation with Krzysztof about this here in Prague. We > have decided to adopt the bindings proposed by Francesco in this > thread [1]. Same question applies there. Where do the 0 and 1 addresses come from? Will reply on that thread. Rob > > [1]. https://lore.kernel.org/all/20260916-remoteproc_virtio_map-v1-8-dac8c5eb4aa9@valla.it/ > > > Rob