From 861e62e9a9ce827b4d1b74677be20913589938e5 Mon Sep 17 00:00:00 2001 From: Frank Binns Date: Fri, 23 Jan 2026 12:58:51 +0000 Subject: [PATCH] docs/pvr: fix some typos and wording Signed-off-by: Frank Binns Suggested-by: Michael Green Reviewed-by: Simon Perretta Part-of: --- docs/drivers/powervr.rst | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/drivers/powervr.rst b/docs/drivers/powervr.rst index 51fd642cfde..0b057798eec 100644 --- a/docs/drivers/powervr.rst +++ b/docs/drivers/powervr.rst @@ -69,13 +69,13 @@ support Vulkan and therefore cannot be supported by this driver. Multi-Architecture support -------------------------- -In order to support multiple distinct hardware generations without too much -spaghetti-code, ther PowerVR compiles a few files multiple times (once per -hardware architecture), and uses a system of macros and aliases to be able -to refer to the different versions. +To support multiple distinct hardware generations without too much +spaghetti-code, the PowerVR build compiles a few files multiple times (once +per hardware architecture) and uses a system of macros and aliases to be +able to refer to the different versions. -The files that gets compiled multiple times are those named -:file:`pvr_arch_*.c`. These files contains definitions of functions prefixed +The files that get compiled multiple times are those named +:file:`pvr_arch_*.c`. These files contain definitions of functions prefixed with ``pvr_arch_`` (instead of the normal ``pvr_``-prefix). The ``arch``-bit of that function is a placeholder, which gets replaced at compile-time, thanks to a system of defines in the corresponding header file, supported by a set @@ -83,16 +83,16 @@ of macros defined in :file:`pvr_macros.h`. The intention is that these functions are mostly called from architecture specific entrypoints, that are handled by the common vulkan dispatch-table -code. This means that a architecture specific function can easily call either +code. This means that an architecture specific function can easily call either architecture specific or architecture agnostic code. -The tricky bit comes when architecture agnostic calls architecture specific -code. In that case, we have the ``PVR_ARCH_DISPATCH`` and -``PVR_ARCH_DISPATCH_RET`` macros. These are a bit error-prone to use, because -they need to see definition for all architecture versions of each entrypoint, +The tricky bit comes when architecture agnostic code calls architecture +specific code. In that case, we have the ``PVR_ARCH_DISPATCH`` and +``PVR_ARCH_DISPATCH_RET`` macros. These are a bit error-prone to use because +they need to see definitions for all architecture versions of each entrypoint, which isn't something we have available. To work around this, we define a ``PER_ARCH_FUNCS(arch)`` macro in each source-file that needs to use these -dispatch macros, and make sure to instantiate it once per architecture. +dispatch macros and make sure to instantiate it once per architecture. To avoid confusion, please do not add functions that are prefixed with ``pvr_arch_`` if they are not part of the system described here.