[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <843824c0ef2e4cfc5307931c9a8aba2f.sboyd@kernel.org>
Date: Thu, 13 Mar 2025 17:54:45 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: heiko@...ech.de, mturquette@...libre.com
Cc: robh@...nel.org, p.zabel@...gutronix.de, krzk+dt@...nel.org, conor+dt@...nel.org, kever.yang@...k-chips.com, devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] dt-bindings: reset: fix double id on rk3562-cru reset ids
Quoting Heiko Stuebner (2025-03-12 14:59:23)
> Id 173 was accidentially used two times for SRST_P_DDR_HWLP and
> SRST_P_DDR_PHY. This makes both resets ambiguous and also causes build
> warnings like:
>
> drivers/clk/rockchip/rst-rk3562.c:21:57: error: initialized field overwritten [-Werror=override-init]
> 21 | #define RK3562_DDRCRU_RESET_OFFSET(id, reg, bit) [id] = (0x20000*4 + reg * 16 + bit)
> | ^
> drivers/clk/rockchip/rst-rk3562.c:266:9: note: in expansion of macro 'RK3562_DDRCRU_RESET_OFFSET'
> 266 | RK3562_DDRCRU_RESET_OFFSET(SRST_P_DDR_PHY, 0, 8),
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/clk/rockchip/rst-rk3562.c:21:57: note: (near initialization for 'rk3562_register_offset[173]')
> 21 | #define RK3562_DDRCRU_RESET_OFFSET(id, reg, bit) [id] = (0x20000*4 + reg * 16 + bit)
> | ^
> drivers/clk/rockchip/rst-rk3562.c:266:9: note: in expansion of macro 'RK3562_DDRCRU_RESET_OFFSET'
> 266 | RK3562_DDRCRU_RESET_OFFSET(SRST_P_DDR_PHY, 0, 8),
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
>
> To fix that issue give SRST_P_DDR_PHY a new and now unique id.
>
> Reported-by: Stephen Boyd <sboyd@...nel.org>
> Reported-by: kernel test robot <lkp@...el.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202503121743.0zcDf6nE-lkp@intel.com/
> Fixes: dd113c4fefc8 ("dt-bindings: clock: Add RK3562 cru")
> Signed-off-by: Heiko Stuebner <heiko@...ech.de>
> ---
Applied to clk-next
Powered by blists - more mailing lists