linux-kernel - Re: [PATCH 2/2] clk: thead: th1520-ap: fix parent of padctrl0 clock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fbbd4f01234d63d1a083944a3c90fa554a6ac458.camel@icenowy.me>
Date: Thu, 14 Aug 2025 13:03:12 +0800
From: Icenowy Zheng <uwu@...nowy.me>
To: Guo Ren <guoren@...nel.org>
Cc: Drew Fustini <fustini@...nel.org>, Fu Wei <wefu@...hat.com>, Michael
 Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>,
 Michal Wilczynski <m.wilczynski@...sung.com>, Yao Zi <ziyao@...root.org>,
 Han Gao <rabenda.cn@...il.com>, linux-riscv@...ts.infradead.org, 
 linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] clk: thead: th1520-ap: fix parent of padctrl0 clock

在 2025-08-14星期四的 11:08 +0800，Guo Ren写道：
> On Thu, Aug 14, 2025 at 1:12 AM Icenowy Zheng <uwu@...nowy.me> wrote:
> > 
> > The padctrl0 clock seems to be a child of the perisys_apb4_hclk
> > clock,
> > gating the later makes padctrl0 registers stuck too.
> > 
> > Fix this relationship.
> Should it add a "Fixes:" tag?

Considering pulling this patch requires pulling PATCH 1/2 too, I doubt
whether this should be tagged a fix and trigger a backport operation.

> 
> Others, LGTM!
> 
> Reviewed-by: Guo Ren <guoren@...nel.org>
> 
> > 
> > Signed-off-by: Icenowy Zheng <uwu@...nowy.me>
> > ---
> >  drivers/clk/thead/clk-th1520-ap.c | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/clk/thead/clk-th1520-ap.c
> > b/drivers/clk/thead/clk-th1520-ap.c
> > index d08e7fb387e50..f6f3d63d53353 100644
> > --- a/drivers/clk/thead/clk-th1520-ap.c
> > +++ b/drivers/clk/thead/clk-th1520-ap.c
> > @@ -888,13 +888,16 @@ static CCU_GATE(CLK_PERISYS_APB3_HCLK,
> > perisys_apb3_hclk, "perisys-apb3-hclk", p
> >                 0x150, 11, CLK_IS_CRITICAL);
> >  static CCU_GATE(CLK_PERISYS_APB4_HCLK, perisys_apb4_hclk,
> > "perisys-apb4-hclk", perisys_ahb_hclk_pd,
> >                 0x150, 12, 0);
> > +static const struct clk_parent_data perisys_apb4_hclk_pd[] = {
> > +       { .hw = &perisys_apb4_hclk.gate.hw },
> > +};
> >  static CCU_GATE(CLK_NPU_AXI, npu_axi_clk, "npu-axi", axi_aclk_pd,
> > 0x1c8, 5, CLK_IS_CRITICAL);
> >  static CCU_GATE(CLK_CPU2VP, cpu2vp_clk, "cpu2vp", axi_aclk_pd,
> > 0x1e0, 13, CLK_IS_CRITICAL);
> >  static CCU_GATE(CLK_EMMC_SDIO, emmc_sdio_clk, "emmc-sdio",
> > emmc_sdio_ref_clk_pd, 0x204, 30, 0);
> >  static CCU_GATE(CLK_GMAC1, gmac1_clk, "gmac1", gmac_pll_clk_pd,
> > 0x204, 26, 0);
> >  static CCU_GATE(CLK_PADCTRL1, padctrl1_clk, "padctrl1",
> > perisys_apb_pclk_pd, 0x204, 24, 0);
> >  static CCU_GATE(CLK_DSMART, dsmart_clk, "dsmart",
> > perisys_apb_pclk_pd, 0x204, 23, 0);
> > -static CCU_GATE(CLK_PADCTRL0, padctrl0_clk, "padctrl0",
> > perisys_apb_pclk_pd, 0x204, 22, 0);
> > +static CCU_GATE(CLK_PADCTRL0, padctrl0_clk, "padctrl0",
> > perisys_apb4_hclk_pd, 0x204, 22, 0);
> >  static CCU_GATE(CLK_GMAC_AXI, gmac_axi_clk, "gmac-axi",
> > axi4_cpusys2_aclk_pd, 0x204, 21, 0);
> >  static CCU_GATE(CLK_GPIO3, gpio3_clk, "gpio3-clk",
> > peri2sys_apb_pclk_pd, 0x204, 20, 0);
> >  static CCU_GATE(CLK_GMAC0, gmac0_clk, "gmac0", gmac_pll_clk_pd,
> > 0x204, 19, 0);
> > --
> > 2.50.1
> > 
> 
>