LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Miles Chen <miles.chen@mediatek.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Wendell Lin <wendell.lin@mediatek.com>,
Hanks Chen <hanks.chen@mediatek.com>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <wsd_upstream@mediatek.com>,
Miles Chen <miles.chen@mediatek.com>
Subject: [RESEND PATCH 0/4] clk: mediatek: modularize COMMON_CLK_MT6779
Date: Fri, 13 Aug 2021 11:24:25 +0800 [thread overview]
Message-ID: <20210813032429.14715-1-miles.chen@mediatek.com> (raw)
This patch set makes COMMON_CLK_MEDIATEK and COMMON_CLK_MT6779*
be able to built as kernel modules. Necessary symbols are exported
in this patch.
In previous discussion [1], Stephen commented that there must
be a user before exporting a symbol:
"
Is the mediatek driver compilable as a module? Last time I checked it
wasn't a module. I want an upstream modular driver that uses the symbol.
Otherwise we're exporting symbols when it doesn't need to be.
"
[1] https://lore.kernel.org/patchwork/patch/1278089/
Miles Chen (4):
clk: composite: export clk_register_composite
clk: mediatek: modularize COMMON_CLK_MEDIATEK
clk: mediatek: modularize COMMON_CLK_MT6779*
clk: mediatek: use tristate for COMMON_CLK_MEDAITEK and
COMMON_CLK_MT6779
drivers/clk/clk-composite.c | 1 +
drivers/clk/mediatek/Kconfig | 20 ++++++++++----------
drivers/clk/mediatek/clk-apmixed.c | 3 +++
drivers/clk/mediatek/clk-cpumux.c | 3 +++
drivers/clk/mediatek/clk-gate.c | 8 ++++++++
drivers/clk/mediatek/clk-mt6779-aud.c | 2 ++
drivers/clk/mediatek/clk-mt6779-cam.c | 2 ++
drivers/clk/mediatek/clk-mt6779-img.c | 2 ++
drivers/clk/mediatek/clk-mt6779-ipe.c | 2 ++
drivers/clk/mediatek/clk-mt6779-mfg.c | 2 ++
drivers/clk/mediatek/clk-mt6779-mm.c | 2 ++
drivers/clk/mediatek/clk-mt6779-vdec.c | 2 ++
drivers/clk/mediatek/clk-mt6779-venc.c | 2 ++
drivers/clk/mediatek/clk-mt6779.c | 2 ++
drivers/clk/mediatek/clk-mtk.c | 8 ++++++++
drivers/clk/mediatek/clk-mux.c | 4 ++++
drivers/clk/mediatek/clk-pll.c | 4 ++++
drivers/clk/mediatek/reset.c | 2 ++
18 files changed, 61 insertions(+), 10 deletions(-)
--
2.18.0
next reply other threads:[~2021-08-13 3:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 3:24 Miles Chen [this message]
2021-08-13 3:24 ` [RESEND PATCH 1/4] clk: composite: export clk_register_composite Miles Chen
2021-08-13 3:24 ` [RESEND PATCH 2/4] clk: mediatek: support COMMON_CLK_MEDIATEK module build Miles Chen
2021-08-13 3:24 ` [RESEND PATCH 3/4] clk: mediatek: support COMMON_CLK_MT6779 " Miles Chen
2021-08-29 4:14 ` Stephen Boyd
2021-08-30 18:43 ` Miles Chen
2021-09-01 5:32 ` Stephen Boyd
2021-09-01 22:04 ` Miles Chen
2021-08-13 3:24 ` [RESEND PATCH 4/4] clk: mediatek: use tristate for COMMON_CLK_MEDAITEK and COMMON_CLK_MT6779 Miles Chen
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=20210813032429.14715-1-miles.chen@mediatek.com \
--to=miles.chen@mediatek.com \
--cc=hanks.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=wendell.lin@mediatek.com \
--cc=wsd_upstream@mediatek.com \
--subject='Re: [RESEND PATCH 0/4] clk: mediatek: modularize COMMON_CLK_MT6779' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).