Re: [PATCH] arm64: dts: qcom: sm7225-fairphone-fp4: Name the regulators

From: Konrad Dybcio
Date: Sat Jun 29 2024 - 09:26:43 EST

Next message: kernel test robot: "Re: [Patch v5 04/12] ARM: dts: lpc32xx: Use simple-mfd for clock control block"
Previous message: syzbot: "Re: [syzbot] [bluetooth?] BUG: sleeping function called from invalid context in lock_sock_nested (3)"
In reply to: Dmitry Baryshkov: "Re: [PATCH] arm64: dts: qcom: sm7225-fairphone-fp4: Name the regulators"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 27.06.2024 3:15 PM, Luca Weiss wrote:
> Without explicitly specifying names for the regulators they are named
> based on the DeviceTree node name. This results in multiple regulators
> with the same name, making debug prints and regulator_summary impossible
> to reason about.
>
> Signed-off-by: Luca Weiss <luca.weiss@xxxxxxxxxxxxx>
> ---

Reviewed-by: Konrad Dybcio <konrad.dybcio@xxxxxxxxxx>

Konrad

Next message: kernel test robot: "Re: [Patch v5 04/12] ARM: dts: lpc32xx: Use simple-mfd for clock control block"
Previous message: syzbot: "Re: [syzbot] [bluetooth?] BUG: sleeping function called from invalid context in lock_sock_nested (3)"
In reply to: Dmitry Baryshkov: "Re: [PATCH] arm64: dts: qcom: sm7225-fairphone-fp4: Name the regulators"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]