From: patchwork-bot+linux-riscv@kernel.org
To: Drew Fustini <dfustini@tenstorrent.com>
Cc: linux-riscv@lists.infradead.org, drew@pdp7.com,
guoren@kernel.org, wefu@redhat.com, mturquette@baylibre.com,
sboyd@kernel.org, jszhang@kernel.org, frank.li@vivo.com,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] clk: thead: Fix TH1520 boot dependency on clk_ignore_unused
Date: Mon, 03 Feb 2025 19:15:45 +0000 [thread overview]
Message-ID: <173861014596.3409359.5224078103636343294.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250113-th1520-clk_ignore_unused-v1-0-0b08fb813438@tenstorrent.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Stephen Boyd <sboyd@kernel.org>:
On Mon, 13 Jan 2025 12:31:23 -0800 you wrote:
> Add the CLK_IGNORE_UNUSED flag to apb_pclk, cpu2peri_x2h_clk,
> perisys_apb2_hclk and perisys_apb3_hclk. Without this flag, the boot
> hangs after "clk: Disabling unused clocks" unless clk_ignore_unused
> is in the kernel cmdline.
>
> In order to allow individual clk gates to specify their own flags,
> the call to devm_clk_hw_register_gate_parent_data() is changeed to
> actually pass the clk flags instead of just 0.
>
> [...]
Here is the summary with links:
- [RESEND,1/2] clk: thead: Fix clk gate registration to pass flags
https://git.kernel.org/riscv/c/a826e53fd78c
- [RESEND,2/2] clk: thead: Add CLK_IGNORE_UNUSED to fix TH1520 boot
https://git.kernel.org/riscv/c/037705e94bf6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-03 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 20:31 [PATCH RESEND 0/2] clk: thead: Fix TH1520 boot dependency on clk_ignore_unused Drew Fustini
2025-01-13 20:31 ` [PATCH RESEND 1/2] clk: thead: Fix clk gate registration to pass flags Drew Fustini
2025-01-13 21:38 ` Stephen Boyd
2025-01-13 20:31 ` [PATCH RESEND 2/2] clk: thead: Add CLK_IGNORE_UNUSED to fix TH1520 boot Drew Fustini
2025-01-13 21:38 ` Stephen Boyd
2025-02-03 19:15 ` patchwork-bot+linux-riscv [this message]
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=173861014596.3409359.5224078103636343294.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=dfustini@tenstorrent.com \
--cc=drew@pdp7.com \
--cc=frank.li@vivo.com \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=wefu@redhat.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