Messages in this thread |  | | Date | Mon, 11 May 2026 09:10:28 +0200 | | Subject | Re: [PATCH v13 3/4] gpio: rpmsg: add generic rpmsg GPIO driver | | From | Arnaud POULIQUEN <> |
| |
Hello Mathieu,
[...] >> >> A third option would be a combination of both approaches: instantiate the >> device using the same name service from the remote side, as done in >> rpmsg-tty. In that case, a get_config message, or a similar mechanism, would >> also be needed to retrieve the port information from the remote side. >> > > I'm not overly fond of a get_config message because it is one more thing we > have to define and maintain. > > Arnaud: is there a get_config message already defined for rpmsg_tty?
No there isn't.
Regards, Arnaud
> > Beleswar: Can you provide a link to a virtio device that would use a get_config > message? > >> Tanmaya also proposed another alternative based on reserved addresses. >> >> At this point, I suggest letting Mathieu review the discussion and recommend >> the most suitable approach. >> >> Thanks, >> Arnaud >> >>>> >>>> At the end, whatever solution is implemented, my main concern is that the >>>> Linux driver design should, if possible, avoid adding unnecessary complexity >>>> or limitations on the remote side (for instance in openAMP project). >>> >>> >>> Yes definitely, I want the same. Feel free to let me know if this does >>> not suit with the OpenAMP project. >>> >>> Thanks, >>> Beleswar >>> >>>> >>>> Thanks, >>>> Arnaud >>>> >>>> >>>>> So Linux does not need to send the port idx everytime while sending a >>>>> gpio message anymore. >>>>> >>>>> Thanks, >>>>> Beleswar >>>>> >>>>> [...] >>>>> >>>> >>
|  |