From: sashiko-bot@kernel.org
To: "Joseph Telaak" <joseph@telaak.dev>, dri-devel@lists.freedesktop.org
Cc: media-ci@linuxtv.org
Subject: Re: [PATCH RFC 04/13] drm/powervr_sgx: Add the uAPI header and its documentation
Date: Thu, 12 Nov 2026 23:12:02 +0000 [thread overview]
Message-ID: <sashiko-outbox-211934@kernel.org> (raw)
In-Reply-To: <20261112-powervr-sgx-v1-4-c69b84bac011@telaak.dev>
Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [Low] drm/powervr_sgx: missing macro identifiers in uapi.rst
kernel-doc
- [Low] drm/powervr_sgx: broken ReST role after caret in
powervr_sgx_drm.h
--
commit f06a880dd06227c9b6234d3a185b5b25ba657094
Author: Joseph Telaak <joseph@telaak.dev>
drm/powervr_sgx: Add the uAPI header and its documentation
This commit adds the powervr_sgx DRM driver's uAPI header, Sphinx
documentation, and MAINTAINERS entry.
> diff --git a/Documentation/gpu/powervr_sgx/uapi.rst b/Documentation/gpu/powervr_sgx/uapi.rst
> new file mode 100644
> index 0000000000000..8dd7908970b92
> --- /dev/null
> +++ b/Documentation/gpu/powervr_sgx/uapi.rst
[ ... ]
> +DEV_QUERY
> +---------
> +.. kernel-doc:: include/uapi/drm/powervr_sgx_drm.h
> + :doc: PowerVR SGX IOCTL DEV_QUERY interface
> +
> +.. kernel-doc:: include/uapi/drm/powervr_sgx_drm.h
> + :identifiers: drm_powervr_sgx_dev_query
> + drm_powervr_sgx_ioctl_dev_query_args
> + drm_powervr_sgx_dev_query_gpu_info
> + drm_powervr_sgx_dev_query_limits
> + drm_powervr_sgx_dev_query_commands
> + drm_powervr_sgx_dev_query_quirks
> + drm_powervr_sgx_heap_id
> + drm_powervr_sgx_heap
> + drm_powervr_sgx_dev_query_heap_info
> +
> +CREATE_BO
> +---------
> +.. kernel-doc:: include/uapi/drm/powervr_sgx_drm.h
> + :doc: PowerVR SGX IOCTL CREATE_BO interface
> +
> +.. kernel-doc:: include/uapi/drm/powervr_sgx_drm.h
> + :identifiers: drm_powervr_sgx_ioctl_create_bo_args
> + drm_powervr_sgx_ioctl_get_bo_mmap_offset_args
[Severity: Low]
Should these :identifiers: lists also include
DRM_POWERVR_SGX_CAP_BACKWARD_BLITS under DEV_QUERY, and
DRM_POWERVR_SGX_BO_ALLOW_CPU_ACCESS and DRM_POWERVR_SGX_BO_CODE under
CREATE_BO?
Those three macros have standalone kernel-doc comments in
powervr_sgx_drm.h rather than being part of a DOC: section, and every
kernel-doc directive in uapi.rst filters by :doc: or :identifiers:, so
their documentation (including the rules on code objects and reserved flag
bits) is omitted from the rendered Sphinx output.
> diff --git a/include/uapi/drm/powervr_sgx_drm.h b/include/uapi/drm/powervr_sgx_drm.h
> new file mode 100644
> index 0000000000000..12381809503a1
> --- /dev/null
> +++ b/include/uapi/drm/powervr_sgx_drm.h
> @@ -0,0 +1,1175 @@
[ ... ]
> + * - User pointers and device-virtual addresses are __u64. A device-virtual
> + * address at or above 2^&drm_powervr_sgx_dev_query_limits.va_bits is
> + * rejected.
[Severity: Low]
Does 2^&drm_powervr_sgx_dev_query_limits.va_bits render raw :c:type:
markup in the generated documentation?
kernel-doc expands &drm_powervr_sgx_dev_query_limits.va_bits into a
:c:type: role right after the caret, and ReStructuredText only recognizes
an inline role when it is preceded by whitespace, a backslash-escaped
space, or punctuation such as ( or -. Escaping the space as 2\^&\ ... or
adding parentheses as 2^(&drm_powervr_sgx_dev_query_limits.va_bits) lets
Docutils parse the cross-reference.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112-powervr-sgx-v1-0-c69b84bac011@telaak.dev?part=4
next prev parent reply other threads:[~2026-11-12 23:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 22:58 [PATCH RFC 00/13] drm/powervr_sgx: Add a DRM driver for PowerVR SGX5xx GPUs Joseph Telaak
2026-11-12 22:58 ` [PATCH RFC 01/13] drm/gem-shmem: Map pages for the DMA device Joseph Telaak
2026-11-12 23:11 ` sashiko-bot
2026-11-12 22:58 ` [PATCH RFC 02/13] drm/gma500: Publish the Cedarview SGX as an auxiliary device Joseph Telaak
2026-11-12 22:58 ` [PATCH RFC 03/13] drm/gma500: Export GEM objects as dma-bufs Joseph Telaak
2026-11-12 23:16 ` sashiko-bot
2026-11-12 22:58 ` [PATCH RFC 04/13] drm/powervr_sgx: Add the uAPI header and its documentation Joseph Telaak
2026-11-12 23:12 ` sashiko-bot [this message]
2026-11-12 22:58 ` [PATCH RFC 05/13] drm/powervr_sgx: Add the core table, registers and device bring-up Joseph Telaak
2026-11-12 23:16 ` sashiko-bot
2026-11-12 22:58 ` [PATCH RFC 06/13] drm/powervr_sgx: Load and start the microkernel Joseph Telaak
2026-11-12 22:58 ` [PATCH RFC 07/13] drm/powervr_sgx: Add GEM objects, VMs and dma-buf sharing Joseph Telaak
2026-11-12 22:58 ` [PATCH RFC 08/13] drm/powervr_sgx: Add contexts, the scheduler and SUBMIT_JOBS Joseph Telaak
2026-11-12 22:58 ` [PATCH RFC 09/13] drm/powervr_sgx: Add the client command checks Joseph Telaak
2026-11-12 23:14 ` sashiko-bot
2026-11-12 22:59 ` [PATCH RFC 10/13] drm/powervr_sgx: Add render jobs Joseph Telaak
2026-11-12 22:59 ` [PATCH RFC 11/13] drm/powervr_sgx: Validate shader code in the kernel Joseph Telaak
2026-11-12 22:59 ` [PATCH RFC 12/13] drm/powervr_sgx: Add the DRM driver, power management and debugging Joseph Telaak
2026-11-12 22:59 ` [PATCH RFC 13/13] drm/powervr_sgx: Add KUnit tests Joseph Telaak
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=sashiko-outbox-211934@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=joseph@telaak.dev \
--cc=media-ci@linuxtv.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.