Re: [PATCH v35 1/7] Documentation/firmware: add imx/se to other_interfaces

[email protected]
Newsgroups dev.linux.lists.imx,org.kernel.vger.linux-devicetree
Message-ID <[email protected]>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The `kernel-doc` directive references a non-existent file `drivers/firmware/imx/se_ctrl.c`, which will cause Sphinx build warnings or errors during documentation generation.
- [Low] Grammatical issues and awkward phrasing in the newly added documentation.
--

--- Patch [1]: [PATCH v35 1/7] Documentation/firmware: add imx/se to other_interfaces ---
commit 5b71a12dcba08cd85c4d04d9b33297065e03bb54
Author: Pankaj Gupta <[email protected]>

Documentation/firmware: add imx/se to other_interfaces
    
Documents i.MX SoC's Service layer and C_DEV driver for selected SoC(s)
that contains the NXP hardware IP(s) for Secure Enclaves(se).

> diff --git a/Documentation/driver-api/firmware/other_interfaces.rst b/Documentation/driver-api/firmware/other_interfaces.rst
> index 06ac89adaafba..6c6fa9a0ba1df 100644
> --- a/Documentation/driver-api/firmware/other_interfaces.rst
> +++ b/Documentation/driver-api/firmware/other_interfaces.rst
[ ... ]
> +Each of the above features is enabled through dedicated NXP H/W IP on the SoC.
> +On a single SoC, multiple hardware IP (or can say more than one secure enclave)
> +can exist.
> +
> +NXP SoCs enabled with the such secure enclaves(SEs) IPs are:
> +i.MX93, i.MX8ULP

[Severity: Low]
This isn't a bug, but the phrasing "with the such secure enclaves(SEs) IPs"
reads a bit awkwardly. Should this perhaps be "with such secure enclave (SE)
IPs" instead? 

There are a couple of other similar grammatical structures in this section 
(like "The NXP's i.MX HW IP" and "multiple hardware IP") that might also
benefit from being smoothed out.

[ ... ]
> +When a user sends a command to the firmware, it registers its device_ctx
> +as waiter of a response from firmware.
> +
> +Enclave's Firmware owns the storage management over a Linux filesystem.
> +For this c_dev provisions a dedicated slave device called "receiver".
> +
> +.. kernel-doc:: drivers/firmware/imx/se_ctrl.c
> +   :export:

[Severity: Low]
Will this kernel-doc directive trigger Sphinx build warnings during make
htmldocs?

It looks like drivers/firmware/imx/se_ctrl.c is not included in this patch.
Does the file exist in the current tree, or should this documentation patch
be combined with the patch that actually introduces se_ctrl.c to prevent
documentation build errors?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.