From: Stephen Boyd <sboyd@kernel.org>
To: Rohit Visavalia <rohit.visavalia@amd.com>,
michal.simek@amd.com, mturquette@baylibre.com,
vishal.sagar@amd.com
Cc: javier.carrasco.cruz@gmail.com, geert+renesas@glider.be,
u.kleine-koenig@baylibre.com, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Rohit Visavalia <rohit.visavalia@amd.com>
Subject: Re: [PATCH v3 1/2] clk: xilinx: vcu: unregister pll_post only if registered correctly
Date: Sat, 21 Jun 2025 14:52:44 -0700 [thread overview]
Message-ID: <175054276458.4372.13734001282575754373@lazor> (raw)
In-Reply-To: <20250210113614.4149050-2-rohit.visavalia@amd.com>
Quoting Rohit Visavalia (2025-02-10 03:36:13)
> If registration of pll_post is failed, it will be set to NULL or ERR,
> unregistering same will fail with following call trace:
>
> Unable to handle kernel NULL pointer dereference at virtual address 008
> pc : clk_hw_unregister+0xc/0x20
> lr : clk_hw_unregister_fixed_factor+0x18/0x30
> sp : ffff800011923850
> ...
> Call trace:
> clk_hw_unregister+0xc/0x20
> clk_hw_unregister_fixed_factor+0x18/0x30
> xvcu_unregister_clock_provider+0xcc/0xf4 [xlnx_vcu]
> xvcu_probe+0x2bc/0x53c [xlnx_vcu]
>
> Fixes: 4472e1849db7 ("soc: xilinx: vcu: make pll post divider explicit")
> Signed-off-by: Rohit Visavalia <rohit.visavalia@amd.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2025-06-21 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 11:36 [PATCH v3 0/2] clk: xilinx: vcu: Sequence update and call trace fix Rohit Visavalia
2025-02-10 11:36 ` [PATCH v3 1/2] clk: xilinx: vcu: unregister pll_post only if registered correctly Rohit Visavalia
2025-06-21 21:52 ` Stephen Boyd [this message]
2025-02-10 11:36 ` [PATCH v3 2/2] clk: xilinx: vcu: Update vcu init/reset sequence Rohit Visavalia
2025-06-21 21:52 ` Stephen Boyd
2025-03-13 6:36 ` [PATCH v3 0/2] clk: xilinx: vcu: Sequence update and call trace fix Visavalia, Rohit
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=175054276458.4372.13734001282575754373@lazor \
--to=sboyd@kernel.org \
--cc=geert+renesas@glider.be \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=mturquette@baylibre.com \
--cc=rohit.visavalia@amd.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vishal.sagar@amd.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