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 EB6F81A0BD0; Tue, 24 Feb 2026 21:01:15 +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=1771966877; cv=none; b=TKHco6/8W163XeomFnU0USzRji+u0TkDVVgIj0FB2Cve5KN6gGKcfRs81+CeLRR5gpSxbEhPAw4XH1J1pheNno9f935pjr31Qc705M68f+wrnFrwPmNOjVFM5DtSEI/dZgw7/7NG8MPYIcbb/MF5nm44O0h1mmy+Ldq2L0MkZcQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771966877; c=relaxed/simple; bh=T5ECrRU2hnn88r4jWZvJ3KKDKv71stJ7hWxICCN95M0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=jxbLXIQ/dpMdeBQn9k0wfnyWscvC7DhoqN3LewM5H8jf3qfQobpyC39KILXbD5UCgzvNb8S3Im6UoGa/xZ1icsK1n52YO9L2D7sbecDw7aRwR3f64MUuW4Pzqu4+DWHlsFF/o7N9EVorCIAntRHvHqQmGyY71P8uAD1OMxNqSdU= 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=LwB7tktH; 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="LwB7tktH" 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=07uVd607MifiuSRzoOjjNoPh2Ox16VYF5/OT1HqLnBc=; b=LwB7tktHtq70OQC/BVl9MxJxmT dvbXMnuXnxUZyuhUWA9ltJTE2uDwVXbUUdceubfAiEk1GU3Uw7IXLblWb0j4PABZEDqxkAc3sOmef yLZhiPm442/b9x/LTJz+7WlI7N91R2J1XIMy6IbepjvW4Hut7MsXYAbQO7XlSPP1EsgU=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1vuzWh-008ejm-N1; Tue, 24 Feb 2026 22:01:03 +0100 Date: Tue, 24 Feb 2026 22:01:03 +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: [PATCH v8 3/4] gpio: rpmsg: add generic rpmsg GPIO driver Message-ID: <0b42e303-a2ed-4983-bee5-a4eafd6c7f36@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> 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: > > How does port_idx fit into this? > > I think you were assuming there is only one remoteproc in the system? > In practice, the setup can look more like this: > > + 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; > + }; > + ... > + }; > + }; > +}; > + > + remote_dsp { > + 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; > + }; > + ... > + }; > + }; > +}; And why would this require a port_idx? If they are different rpmsg instances, the channel numbers are in different address spaces. Andrew