linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Shenwei Wang <shenwei.wang@nxp.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Jonathan Corbet <corbet@lwn.net>,
	Bjorn Andersson <andersson@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-remoteproc@vger.kernel.org"
	<linux-remoteproc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v4 3/5] docs: admin-guide: gpio: rpmsg: gpio over rpmsg bus
Date: Wed, 29 Oct 2025 14:02:54 -0700	[thread overview]
Message-ID: <e4b63a5e-c549-4c48-aa03-e81ad694b200@infradead.org> (raw)
In-Reply-To: <PAXPR04MB918593CC07C246CADA458E4689FAA@PAXPR04MB9185.eurprd04.prod.outlook.com>



On 10/29/25 1:52 PM, Shenwei Wang wrote:
> 
> 
>> -----Original Message-----
>> From: Randy Dunlap <rdunlap@infradead.org>
>> Sent: Wednesday, October 29, 2025 3:47 PM
>> To: Shenwei Wang <shenwei.wang@nxp.com>; Linus Walleij
>> <linus.walleij@linaro.org>; Bartosz Golaszewski <brgl@bgdev.pl>; Jonathan
>> Corbet <corbet@lwn.net>; Bjorn Andersson <andersson@kernel.org>; Mathieu
>> Poirier <mathieu.poirier@linaro.org>; Rob Herring <robh@kernel.org>; Krzysztof
>> Kozlowski <krzk+dt@kernel.org>; Conor Dooley <conor+dt@kernel.org>; Shawn
>> Guo <shawnguo@kernel.org>; Sascha Hauer <s.hauer@pengutronix.de>
>> Cc: Pengutronix Kernel Team <kernel@pengutronix.de>; Fabio Estevam
>> <festevam@gmail.com>; Peng Fan <peng.fan@nxp.com>; linux-
>> gpio@vger.kernel.org; linux-doc@vger.kernel.org; linux-kernel@vger.kernel.org;
>> linux-remoteproc@vger.kernel.org; devicetree@vger.kernel.org;
>> imx@lists.linux.dev; dl-linux-imx <linux-imx@nxp.com>
>> Subject: [EXT] Re: [PATCH v4 3/5] docs: admin-guide: gpio: rpmsg: gpio over
>> rpmsg bus
>>
>> Hi--
>>
>> On 10/29/25 12:56 PM, Shenwei Wang wrote:
>>> Describes the gpio rpmsg transport protocol over the rpmsg bus between
>>> the cores.
>>>
>>> Signed-off-by: Shenwei Wang <shenwei.wang@nxp.com>
>>> ---
>>>  Documentation/admin-guide/gpio/gpio-rpmsg.rst | 202 ++++++++++++++++++
>>>  Documentation/admin-guide/gpio/index.rst      |   1 +
>>>  2 files changed, 203 insertions(+)
>>>  create mode 100644 Documentation/admin-guide/gpio/gpio-rpmsg.rst
>>>
>>
>> I don't think this should be in admin-guide/gpio/.
>> How about in driver-api/gpio/?
>> That may not be perfect either, but transport protocols are not typically admin
>> material AFAIK.
>>
> 
> How about putting it in Documentation/staging directory?
> I saw both remoteproc.rst and rpmsg.rst are in the directory.
> 

Yeah, maybe. That's sort of a last resort location for things
that don't have a better place.

> 
>>> diff --git a/Documentation/admin-guide/gpio/index.rst
>>> b/Documentation/admin-guide/gpio/index.rst
>>> index 712f379731cb..9c8f4441038a 100644
>>> --- a/Documentation/admin-guide/gpio/index.rst
>>> +++ b/Documentation/admin-guide/gpio/index.rst
>>> @@ -9,6 +9,7 @@ GPIO
>>>
>>>      Character Device Userspace API <../../userspace-api/gpio/chardev>
>>>      gpio-aggregator
>>> +    gpio-rpmsg
>>>      gpio-sim
>>>      gpio-virtuser
>>>      Obsolete APIs <obsolete>
>> If someone thinks that it should be in admin-guide/,please explain why.
>>
>> Thanks.
>> --
>> ~Randy

-- 
~Randy


  reply	other threads:[~2025-10-29 21:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 19:56 [PATCH v4 0/5] Enable Remote GPIO over RPMSG on i.MX Platform Shenwei Wang
2025-10-29 19:56 ` [PATCH v4 1/5] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support Shenwei Wang
2025-10-29 19:56 ` [PATCH v4 2/5] remoteproc: imx_rproc: Populate devices under "rpmsg" subnode Shenwei Wang
2025-10-29 19:56 ` [PATCH v4 3/5] docs: admin-guide: gpio: rpmsg: gpio over rpmsg bus Shenwei Wang
2025-10-29 20:46   ` Randy Dunlap
2025-10-29 20:52     ` Shenwei Wang
2025-10-29 21:02       ` Randy Dunlap [this message]
2025-10-29 19:56 ` [PATCH v4 4/5] gpio: imx-rpmsg: add imx-rpmsg GPIO driver Shenwei Wang
2025-10-30 15:44   ` Bartosz Golaszewski
2025-10-29 19:56 ` [PATCH v4 5/5] arm64: dts: imx8ulp: Add rpmsg node under imx_rproc Shenwei Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e4b63a5e-c549-4c48-aa03-e81ad694b200@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=andersson@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=shenwei.wang@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).