[PATCH v20 5/8] regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub

[sashiko-bot at kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] mfd: driver-specific header placed in global include directory
--

commit 51d204aed0d51828d1e68a0ac0a10f8c8cac311b
Author: Aman Kumar Pandey <aman.kumarpandey at nxp.com>

regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub

This commit adds a regulator driver for the on-die regulators in the NXP
P3H2x4x i3c hub device, registering them via the regulator subsystem using
the MFD framework.

> diff --git a/drivers/regulator/p3h2840_i3c_hub_regulator.c b/drivers/regulator/p3h2840_i3c_hub_regulator.c
> new file mode 100644
> index 0000000000000..244f2a4f70f38
> --- /dev/null
> +++ b/drivers/regulator/p3h2840_i3c_hub_regulator.c
> @@ -0,0 +1,289 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright 2025-2026 NXP
> + * NXP P3H2X4X regulator driver file contain functions for enable/disable regulator
> + * and voltage set/get.
> + */
> +#include <linux/bitfield.h>
> +#include <linux/cleanup.h>
> +#include <linux/mfd/p3h2840.h>

[Severity: Low]
Does this include violate the MFD subsystem guidelines for driver-specific
headers? 

The MFD guidelines state that driver-specific header files used only by the
parent and its immediate children should be kept local to drivers/mfd/
rather than being placed in the global include/linux/mfd/ directory. Since
this header appears to only be used by the p3h2840 parent and children,
could it be moved to the local subsystem directory to avoid polluting the
global include space?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260922103551.2754613-1-lakshay.piplani@nxp.com?part=5