> -----Original Message-----
> From: Andrew Lunn <[email protected]>
> Sent: Tuesday, February 24, 2026 3:01 PM
> To: Shenwei Wang <[email protected]>
> Cc: Arnaud POULIQUEN <[email protected]>; Linus Walleij
> <[email protected]>; Bartosz Golaszewski <[email protected]>; Jonathan Corbet
> <[email protected]>; Rob Herring <[email protected]>; Krzysztof Kozlowski
> <[email protected]>; Conor Dooley <[email protected]>; Bjorn Andersson
> <[email protected]>; Mathieu Poirier <[email protected]>; Frank Li
> <[email protected]>; Sascha Hauer <[email protected]>; Shuah Khan
> <[email protected]>; [email protected]; linux-
> [email protected]; [email protected]; Pengutronix Kernel Team
> <[email protected]>; Fabio Estevam <[email protected]>; Peng Fan
> <[email protected]>; [email protected]; linux-
> [email protected]; [email protected]; linux-arm-
> [email protected]; dl-linux-imx <[email protected]>; Bartosz
> Golaszewski <[email protected]>
> Subject: [EXT] Re: [PATCH v8 3/4] gpio: rpmsg: add generic rpmsg GPIO driver
> > > 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.
>
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.
Thanks,
Shenwei
> Andrew
