On Fri, Oct 10, 2025 at 6:31 PM Mathieu Poirier <[email protected]> wrote: > On Fri, Oct 10, 2025 at 12:58:38AM +0200, Andrew Lunn wrote: > > On Thu, Oct 09, 2025 at 05:27:15PM -0500, Shenwei Wang wrote: > > > On i.MX SoCs, the system may include two processors: > > > - An MCU running an RTOS > > > - An MPU running Linux > > > > > > These processors communicate via the RPMSG protocol. > > > The driver implements the standard GPIO interface, allowing > > > the Linux side to control GPIO controllers which reside in > > > the remote processor via RPMSG protocol. > > > > I've not seen the discussion on earlier versions of this patchset, so > > i might be asking something already asked and answered. Sorry if i am. > > > > Is there anything IMX specific in here? This appears to be the first > > RPMSG GPIO driver. Do we have the opportunity here to define a > > protocol for all future RPMSG GPIO drivers, which any/all vendors > > should follow, so we don't have lots of different implementations of > > basically they same thing? So this would become gpio-rpmsg.c and a > > Document somewhere describing the protocol? > > > > I haven't looked at this patchset yet but I think Andrew's proposal has merit.
Yeah this was my comment on v2 as well :D I even posted a bug to the AMP mailing list to elicit some attention from that camp. It worked because now Arnaud is on board reviewing the patch set from an ST PoV. Maybe it is possible to split the driver in one generic part and one i.MX part, so it is easy to reuse for other SoCs? Yours, Linus Walleij
