> -----Original Message----- > From: Randy Dunlap <[email protected]> > Sent: Wednesday, November 12, 2025 3:18 PM > To: Daniel Baluta <[email protected]>; Rob Herring <[email protected]> > Cc: Shenwei Wang <[email protected]>; Bjorn Andersson > <[email protected]>; Mathieu Poirier <[email protected]>; > Krzysztof Kozlowski <[email protected]>; Conor Dooley > <[email protected]>; Shawn Guo <[email protected]>; Sascha Hauer > <[email protected]>; Jonathan Corbet <[email protected]>; Linus Walleij > <[email protected]>; Bartosz Golaszewski <[email protected]>; Pengutronix > Kernel Team <[email protected]>; Fabio Estevam <[email protected]>; > Peng Fan <[email protected]>; [email protected]; > [email protected]; [email protected]; linux-arm- > [email protected]; [email protected]; linux- > [email protected]; dl-linux-imx <[email protected]> > Subject: [EXT] Re: [PATCH v5 3/5] docs: staging: gpio-rpmsg: gpio over rpmsg > bus > On 11/12/25 5:35 AM, Daniel Baluta wrote: > > On Wed, Nov 12, 2025 at 2:59 PM Rob Herring <[email protected]> wrote: > >> > >> On Tue, Nov 04, 2025 at 02:33:13PM -0600, Shenwei Wang wrote: > >>> Describes the gpio rpmsg transport protocol over the rpmsg bus > >>> between the cores. > >>> > >>> Signed-off-by: Shenwei Wang <[email protected]> > >>> --- > >>> Documentation/staging/gpio-rpmsg.rst | 202 > +++++++++++++++++++++++++++ > >>> Documentation/staging/index.rst | 1 + > >> > >> Why is this in staging when none of the drivers are? > > > > I guess that's because remoteproc.rst and rpmsg.rst are in > > Documentation/staging and that's because when converting them from > > .txt to .rst the author didn't know a good place where to move them. > > > > Would Documentation/driver-api be a good place for these doc files? I > > can move them and then Shenwei place the gpio-rpmsg.rst in the > > Documentation/driver-api also > > Documentation/driver-api/gpio/ if its driver documentation. > Documentation/userspace-api/gpio/ if it user API docs There is also gpio > documentation in Documentation/admin-guide/gpio/ which could also be > appropriate depending on the nature of the document. >
Thanks Randy! Do we have a final decision on where to place this document? My thought is that Documentation/driver-api/gpio/ seems more appropriate. However, it’s worth noting that while this is a driver-related document, it doesn’t describe the driver API itself. Thanks, Shenwei > -- > ~Randy
