From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
patches@lists.linux.dev
Subject: [PATCH 0/4] clk: Move debugfs to a loadable kernel module
Date: Tue, 7 Jan 2025 16:58:45 -0800 [thread overview]
Message-ID: <20250108005854.2973184-1-sboyd@kernel.org> (raw)
This series moves as much of the debugfs code as possible from the core
clk framework file clk.c into a loadable kernel module. The goal is to
move the debugfs code out of the primary vmlinux and allow users to
decide if they want to load the debugging logic at all. To get there, we
make the debugfs code use struct clk_hw and then add a bunch of helpers
to interrogate the clk_hw enough to satisfy the use-cases we have in
debugfs today. Finally we move the code from clk.c to clk-debug.c almost
wholesale, except for some tree walking logic and functions to
interrogate a struct clk_hw or install a function pointer to call when a
clk is registered.
I'll probably wait to merge this until after we're able to limit the
exporting of kernel symbols to particular modules, because I'm not super
excited with exporting internal clk details to any module. For now, I've
put the symbols that are newly introduced for debugfs into the
"clk-debug" namespace.
Stephen Boyd (4):
clk: Prepare clk_debug_create_one() to be split off
clk: Use struct clk_hw instead of struct clk_core for debugfs
clk: Iterate instead of recurse for debugfs printing
clk: Make debugfs code into a loadable kernel module
drivers/clk/Kconfig | 8 +
drivers/clk/Makefile | 1 +
drivers/clk/clk-debug.c | 529 ++++++++++++++++++++++++++++++++
drivers/clk/clk-debug.h | 33 ++
drivers/clk/clk.c | 646 ++++++++++++----------------------------
5 files changed, 763 insertions(+), 454 deletions(-)
create mode 100644 drivers/clk/clk-debug.c
create mode 100644 drivers/clk/clk-debug.h
base-commit: fac04efc5c793dccbd07e2d59af9f90b7fc0dca4
--
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/
https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git
next reply other threads:[~2025-01-08 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 0:58 Stephen Boyd [this message]
2025-01-08 0:58 ` [PATCH 1/4] clk: Prepare clk_debug_create_one() to be split off Stephen Boyd
2025-01-08 0:58 ` [PATCH 2/4] clk: Use struct clk_hw instead of struct clk_core for debugfs Stephen Boyd
2025-01-08 0:58 ` [PATCH 3/4] clk: Iterate instead of recurse for debugfs printing Stephen Boyd
2025-01-08 0:58 ` [PATCH 4/4] clk: Make debugfs code into a loadable kernel module Stephen Boyd
2025-01-10 6:45 ` kernel test robot
2025-01-11 11:51 ` kernel test robot
2025-01-22 23:29 ` Jeff Johnson
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=20250108005854.2973184-1-sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=patches@lists.linux.dev \
/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