On Mon, Nov 17, 2025 at 10:39:54AM +0100, [email protected] wrote:

> From: Yegor Yefremov <[email protected]>
> 
> The TI System Controller (TI_SYSC) driver utilizes clock management
> functions provided by the TI Clock Controller (CLK_TI_CTRL) driver.
> 
> Specifically, the TI_SYSC driver relies on the 'ti,syscon' support,
> which is used to access system registers for tasks like reset control
> and power management. These operations often involve manipulating
> clock-gating or reset signals managed by the underlying clock hardware.
> 
> Therefore, to ensure that the necessary register access and clock
> manipulation functions are available for the System Controller
> operations, CLK_TI_CTRL must be selected when TI_SYSC is enabled.
> 
> Signed-off-by: Yegor Yefremov <[email protected]>
> ---
>  drivers/bus/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/bus/Kconfig b/drivers/bus/Kconfig
> index a786fe430e4..05492c63bf0 100644
> --- a/drivers/bus/Kconfig
> +++ b/drivers/bus/Kconfig
> @@ -15,6 +15,7 @@ config TI_SYSC
>       bool "TI sysc interconnect target module driver"
>       depends on DM && ARCH_OMAP2PLUS
>       select CLK
> +     select CLK_TI_CTRL
>       help
>         Generic driver for Texas Instruments interconnect target module
>         found on many TI SoCs.

This leads to failure to build on:
igep00x0 sniper am3517_evm omap35_logic omap35_logic_somlv omap3_logic
omap3_logic_somlv omap3_evm devkit8000 am57xx_evm am57xx_hs_evm
am57xx_hs_evm_usb dra7xx_evm dra7xx_hs_evm dra7xx_hs_evm_usb

-- 
Tom

Attachment: signature.asc
Description: PGP signature

Reply via email to