From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Phil Elwell <phil@raspberrypi.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
kernel-list@raspberrypi.com, linux-staging@lists.linux.dev
Subject: Re: [PATCH RFC 2/2] staging: vc04_services: Document VCHIQ character device
Date: Wed, 21 May 2025 13:20:54 +0200 [thread overview]
Message-ID: <2025052121-glisten-serpent-8ede@gregkh> (raw)
In-Reply-To: <20250509221152.13564-3-wahrenst@gmx.net>
On Sat, May 10, 2025 at 12:11:52AM +0200, Stefan Wahren wrote:
> From: Phil Elwell <phil@raspberrypi.com>
>
> Document the IOCTLs for the VCHIQ character device, which provide
> a userspace interface to access the VideoCore VPU of the
> Raspberry Pi. Several ARM side libraries make use of it like EGL,
> MMAL and OpenMAX.
>
> Link: https://github.com/raspberrypi/linux/pull/6801
> Signed-off-by: Phil Elwell <phil@raspberrypi.com>
> [wahrenst@gmx.net: Rewrite commit log]
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
> ---
> .../vc04_services/Documentation/vchiq-cdev | 87 +++++++++++++++++++
> 1 file changed, 87 insertions(+)
> create mode 100644 drivers/staging/vc04_services/Documentation/vchiq-cdev
>
> diff --git a/drivers/staging/vc04_services/Documentation/vchiq-cdev b/drivers/staging/vc04_services/Documentation/vchiq-cdev
> new file mode 100644
> index 000000000000..99ab2567643e
> --- /dev/null
> +++ b/drivers/staging/vc04_services/Documentation/vchiq-cdev
> @@ -0,0 +1,87 @@
> +What: /dev/vchiq
> +Date: October 2016
> +KernelVersion: 4.9
> +Contact: kernel-list@raspberrypi.com
> +Description:
> + The ioctl interface for the VCHIQ character device.
> + Following actions are supported:
> +
> + * VCHIQ_IOC_CONNECT:
> + Establish/confirm the link to the VPU peer.
I understand the need, but this does not document the parameters to the
ioctls, so it's not all that useful. How about just a normal
documentation file with this all written out?
thanks,
greg k-h
next prev parent reply other threads:[~2025-05-21 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 22:11 [PATCH RFC 0/2] staging: vchiq_arm: Improve documentation Stefan Wahren
2025-05-09 22:11 ` [PATCH RFC 1/2] staging: vchiq_arm: Improve inline documentation Stefan Wahren
2025-05-09 22:11 ` [PATCH RFC 2/2] staging: vc04_services: Document VCHIQ character device Stefan Wahren
2025-05-16 10:55 ` Stefan Wahren
2025-05-21 11:20 ` Greg Kroah-Hartman [this message]
2025-05-21 11:28 ` Laurent Pinchart
2025-05-21 11:39 ` Stefan Wahren
2025-05-21 11:52 ` Laurent Pinchart
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=2025052121-glisten-serpent-8ede@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@linaro.org \
--cc=florian.fainelli@broadcom.com \
--cc=kernel-list@raspberrypi.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@raspberrypi.com \
--cc=wahrenst@gmx.net \
/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