Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Brunet <jbrunet@baylibre.com>
To: Jian Hu <jian.hu@amlogic.com>
Cc: Xianwei Zhao <xianwei.zhao@amlogic.com>,
	 Chuan Liu <chuan.liu@amlogic.com>,
	 Neil Armstrong <neil.armstrong@linaro.org>,
	Kevin Hilman <khilman@baylibre.com>,
	 Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	 Dmitry Rokosov <ddrokosov@sberdevices.ru>,
	 robh+dt <robh+dt@kernel.org>,  Rob Herring <robh@kernel.org>,
	 devicetree <devicetree@vger.kernel.org>,
	 linux-clk <linux-clk@vger.kernel.org>,
	 linux-amlogic <linux-amlogic@lists.infradead.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	 linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 4/6] clk: meson: t7: add support for the T7 SoC PLL clock
Date: Mon, 16 Jun 2025 18:27:53 +0200	[thread overview]
Message-ID: <1jh60fd52u.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <4dd25114-212d-44d6-938a-63871750c292@amlogic.com> (Jian Hu's message of "Thu, 12 Jun 2025 21:02:00 +0800")

On Thu 12 Jun 2025 at 21:02, Jian Hu <jian.hu@amlogic.com> wrote:

>>> +
>>> +static struct clk_regmap t7_pcie_pll_od = {
>>> +     .data = &(struct clk_regmap_div_data){
>>> +             .offset = ANACTRL_PCIEPLL_CTRL0,
>>> +             .shift = 16,
>>> +             .width = 5,
>>> +             .flags = CLK_DIVIDER_ONE_BASED |
>>> +                      CLK_DIVIDER_ALLOW_ZERO,
>> What's the behaviour of the divider on zero then ?
>
>
> If there is no CLK_DIVDER_ALLOW_ZERO, there is a warning when registering
> t7_pcie_pll_od.
>
> like this:
>
>   ------------[ cut here ]------------
>   WARNING: CPU: 1 PID: 1 at drivers/clk/clk-divider.c:140
> divider_recalc_rate+0xfc/0x100
>   pcie_pll_od: Zero divisor and CLK_DIVIDER_ALLOW_ZERO not set
>   Modules linked in:
>  CPU: 1 PID: 1 Comm: swapper/0 Not tainted
> 5.4.283-09976-ga803e94eed88-dirty #91
>   Hardware name: tm2_t962e2_ab311 (DT)
>  Call trace:
>   [ffffffc020003750+  64][<ffffffc0100e3e3c>] dump_backtrace+0x0/0x1e4
>   [ffffffc020003790+  32][<ffffffc0100e4044>] show_stack+0x24/0x34
>   [ffffffc0200037b0+  96][<ffffffc01130a2e8>] dump_stack+0xbc/0x108
>  [ffffffc020003810+ 144][<ffffffc01010c484>] __warn+0xf4/0x1b8
>   [ffffffc0200038a0+  64][<ffffffc01010c5f4>] warn_slowpath_fmt+0xac/0xc8
>  [ffffffc0200038e0+  64][<ffffffc01061d364>] divider_recalc_rate+0xfc/0x100
>  [ffffffc020003920+  80][<ffffffc010624e84>]
> clk_regmap_div_recalc_rate+0x74/0x88
>   [ffffffc020003970+  96][<ffffffc010616a54>] __clk_register+0x62c/0xb78
>
> so add it to avoid the warning.

That does not really answer my question


  reply	other threads:[~2025-06-16 18:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09  7:48 [PATCH v3 0/6] add support for T7 family clock controller Jian Hu
2025-05-09  7:48 ` [PATCH v3 1/6] dt-bindings: clock: add Amlogic T7 PLL " Jian Hu
2025-05-09 16:09   ` Conor Dooley
2025-05-09  7:48 ` [PATCH v3 2/6] dt-bindings: clock: add Amlogic T7 SCMI " Jian Hu
2025-05-09  7:48 ` [PATCH v3 3/6] dt-bindings: clock: add Amlogic T7 peripherals " Jian Hu
2025-05-09  7:48 ` [PATCH v3 4/6] clk: meson: t7: add support for the T7 SoC PLL clock Jian Hu
2025-05-14  7:52   ` Jerome Brunet
2025-06-12 13:02     ` Jian Hu
2025-06-16 16:27       ` Jerome Brunet [this message]
2025-06-25  2:52         ` Jian Hu
2025-06-25  7:46           ` Jerome Brunet
2025-07-03  3:42             ` Jian Hu
2025-05-09  7:48 ` [PATCH v3 5/6] clk: meson: add MESON_PCLK_V2 for sys gate clock Jian Hu
2025-05-14  7:39   ` Jerome Brunet
     [not found]     ` <ea83e375-7088-4047-92f1-31d0e7c2c331@amlogic.com>
2025-06-16 16:28       ` Jerome Brunet
2025-06-20  9:21     ` Jian Hu
2025-05-09  7:48 ` [PATCH v3 6/6] clk: meson: t7: add t7 clock peripherals controller driver Jian Hu
2025-05-14  8:00   ` Jerome Brunet
2025-06-13  9:39     ` Jian Hu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1jh60fd52u.fsf@starbuckisacylon.baylibre.com \
    --to=jbrunet@baylibre.com \
    --cc=chuan.liu@amlogic.com \
    --cc=ddrokosov@sberdevices.ru \
    --cc=devicetree@vger.kernel.org \
    --cc=jian.hu@amlogic.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=xianwei.zhao@amlogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox