[PATCH v2 1/3] clk: microchip: drop POLARFIRE from ARCH_MICROCHIP_POLARFIRE

claudiu beznea claudiu.beznea at tuxon.dev
Thu Jan 8 23:22:25 PST 2026



On 12/8/25 20:02, Conor Dooley wrote:
> On Sat, Dec 06, 2025 at 01:18:30PM +0200, Claudiu Beznea wrote:
>>
>>
>> On 11/21/25 15:44, Conor Dooley wrote:
>>> From: Conor Dooley <conor.dooley at microchip.com>
>>>
>>> This driver is used by non-polarfire devices now, and the ARCH_MICROCHIP
>>> symbol has been defined for some time on RISCV so drop it without any
>>> functional change.
>>>
>>> Signed-off-by: Conor Dooley <conor.dooley at microchip.com>
>>> ---
>>>   drivers/clk/microchip/Kconfig | 4 ++--
>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/clk/microchip/Kconfig b/drivers/clk/microchip/Kconfig
>>> index cab9a909893b..a0ef14310417 100644
>>> --- a/drivers/clk/microchip/Kconfig
>>> +++ b/drivers/clk/microchip/Kconfig
>>> @@ -5,8 +5,8 @@ config COMMON_CLK_PIC32
>>>   
>>>   config MCHP_CLK_MPFS
>>>   	bool "Clk driver for PolarFire SoC"
>>> -	depends on ARCH_MICROCHIP_POLARFIRE || COMPILE_TEST
>>> -	default ARCH_MICROCHIP_POLARFIRE
>>> +	depends on ARCH_MICROCHIP || COMPILE_TEST
>>> +	default y
>>>   	depends on MFD_SYSCON
>>>   	select AUXILIARY_BUS
>>>   	select COMMON_CLK_DIVIDER_REGMAP
>>
>> OK, I found v2 in my inbox. Same symptom here. It doesn't apply on top of
>> the current at91-next either.
> 
> I think this should sort itself out after -rc1, but I'll resend if it
> doesn't.

Still doesn't apply. It conflicts at least with
commit c6f2dddfa7f9 ("clk: microchip: mpfs: use regmap for clocks")

Thank you,
Claudiu



More information about the linux-riscv mailing list