From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (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 364453191BB; Tue, 24 Feb 2026 22:23:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771971786; cv=none; b=bwan7pmyu5u3J6w5lx82XZD/v/5sLp1HqduHKlIJWBE9P6W0AUNCKrc1mt1BVmaPXQyx+K2GPwk7YIt97NfX5gZCrHvPR7sJtQ7eGaDFPfBzfjl9EBVuK+FRyA1+P7z1tA/fjQM+q8YiPm/dC3NQ0gYtRQ8k0dD3YMcu+E5KtCE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771971786; c=relaxed/simple; bh=NbftUWxLOoJuc6CIUc9hxeQD/F1gsoDCVxJAdI+M1cA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=mVPM87daSLJwsE12RCIkSM8nL+sGXJUIiIqGhxhaIBgAqK+91yGP1JYbf7v6Gat5c0Po3MW13njl2NNfoquSPsSNYjJaF1o+7V0ZjZVWhtBAzwpUwhZbmgpw4c9jJ3D4VLdowJIqTVa4YnlbFxzL+/UdKy4F1BkVb57CpK6sw0g= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=zJV5pPQJ; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="zJV5pPQJ" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=RnTV6ZJVnwYW7iQf2SMUCiEq1bhIKlJyAv74L2EwgcA=; b=zJV5pPQJYab26RK+hLVBEgtPFb o1LBgVzoWwWkzkb/ch8dISjG/5HK9ndMRfsYHtdsUs2pa0YtacE/eVhtv6WMwHq4vm9uO3Xixxdzw BqTDHJsFV96dJLrAWOdUaKM7quT0BMPhYZVwJF9+53wMMTzSM4G7OUCKbDl65EO2Xi0I=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1vv0nw-008f4x-K6; Tue, 24 Feb 2026 23:22:56 +0100 Date: Tue, 24 Feb 2026 23:22:56 +0100 From: Andrew Lunn To: Shenwei Wang Cc: Arnaud POULIQUEN , Linus Walleij , Bartosz Golaszewski , Jonathan Corbet , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Bjorn Andersson , Mathieu Poirier , 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 , Peng Fan , "devicetree@vger.kernel.org" , "linux-remoteproc@vger.kernel.org" , "imx@lists.linux.dev" , "linux-arm-kernel@lists.infradead.org" , dl-linux-imx , Bartosz Golaszewski Subject: Re: [EXT] Re: [PATCH v8 3/4] gpio: rpmsg: add generic rpmsg GPIO driver Message-ID: <8fbb4ded-8914-4e11-aad6-038c78f2d31d@lunn.ch> References: <64ef5dbf-6264-4758-a5d8-d8c52c359fcc@foss.st.com> <79eb8bb8-83cb-4b24-8e56-42a53c710055@lunn.ch> <91701822-df30-4feb-9e9a-4ee82e2a5d23@lunn.ch> <0b42e303-a2ed-4983-bee5-a4eafd6c7f36@lunn.ch> Precedence: bulk X-Mailing-List: imx@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: > > > + remote_cm33{ > > > + rpmsg { > > > + rpmsg-io-channel { > > > + #address-cells = <1>; > > > + #size-cells = <0>; > > > + > > > + gpio@0 { > > > + compatible = "rpmsg-gpio"; > > > + reg = <0>; > > > + gpio-controller; > > > + #gpio-cells = <2>; > > > + #interrupt-cells = <2>; > > > + interrupt-controller; > > > + }; > > > + gpio@1 { > > > + compatible = "rpmsg-gpio"; > > > + reg = <1>; > > > + gpio-controller; > > > + #gpio-cells = <2>; > > > + #interrupt-cells = <2>; > > > + interrupt-controller; > > > + }; > Then how would you distinguish gpio@0 from gpio@1 on the CM33 RPMSG bus in the example above? > They are running on the same transport. Doesn't reg indicate the channel number? gpio@0 is on rpmsg channel 0. gpio@1 is on channel 1? The reg value gets filled into struct rpmsg_channel_info when the endpoints are created? Andrew