Re: [PATCH v1 6/6] reset: starfive: Add StarFive JHB100 System-0 reset driver
From: Jerome Brunet
Date: Sun Nov 15 2026 - 09:18:47 EST
> Add the auxiliary reset driver for the StarFive JHB100 SoC. It binds to
> the auxiliary devices registered by the JHB100 clock generator drivers
> and uses the register base handed over as platform data.
>
> Start with the System-0 clock and reset generator (SYS0CRG). Its reset
> IDs do not map one-to-one to the hardware reset bits, so the controller
> is registered with a reset ID map.
>
> The other JHB100 reset controllers are added by follow-up patches, each
> right after the clock driver of the same CRG.
>
> Signed-off-by: Changhuang Liang <changhuang.liang@xxxxxxxxxxxxxxxx>
> ---
> MAINTAINERS | 6 ++
> drivers/reset/starfive/Kconfig | 9 +++
> drivers/reset/starfive/Makefile | 1 +
> .../reset/starfive/reset-starfive-jhb100.c | 75 +++++++++++++++++++
> 4 files changed, 91 insertions(+)
> create mode 100644 drivers/reset/starfive/reset-starfive-jhb100.c
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f66998e8eb64..c2ab9cbccf49 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -26858,6 +26858,12 @@ S: Maintained
> F: Documentation/devicetree/bindings/pinctrl/starfive,jhb1*.yaml
> F: drivers/pinctrl/starfive/pinctrl-starfive-jhb1*
>
> +STARFIVE JHB100 RESET CONTROLLER DRIVERS
> +M: Changhuang Liang <changhuang.liang@xxxxxxxxxxxxxxxx>
> +S: Supported
> +F: drivers/reset/starfive/reset-starfive-jhb1*
> +F: include/dt-bindings/reset/starfive,jhb1*.h
> +
> STATIC BRANCH/CALL
> M: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
> M: Josh Poimboeuf <jpoimboe@xxxxxxxxxx>
> diff --git a/drivers/reset/starfive/Kconfig b/drivers/reset/starfive/Kconfig
> index d832339f61bc..84baefbaee14 100644
> --- a/drivers/reset/starfive/Kconfig
> +++ b/drivers/reset/starfive/Kconfig
> @@ -19,3 +19,12 @@ config RESET_STARFIVE_JH7110
> default ARCH_STARFIVE
> help
> This enables the reset controller driver for the StarFive JH7110 SoC.
> +
> +config RESET_STARFIVE_JHB100
> + bool "StarFive JHB100 Reset Driver"
> + depends on CLK_STARFIVE_JH71X0 || COMPILE_TEST
This would mean it can't build without the starfive clock being compiled too.
There should just be a shared header, unless I'm missing something and the
clock already imply this driver, that should be enough ? no ?
If so, 'default ARCH_STARFIVE' can go too. and just
depends on ARCH_STARFIVE || COMPILE_TEST
--
Jerome