From: Chuan Liu via B4 Relay <devnull+chuan.liu.amlogic.com@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Jerome Brunet <jbrunet@baylibre.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Chuan Liu <chuan.liu@amlogic.com>
Subject: [PATCH 0/6] clk: meson: Delete a meaningless spinlock from the MPLL
Date: Fri, 20 Sep 2024 16:16:10 +0800 [thread overview]
Message-ID: <20240920-mpll_spinlock-v1-0-5249a9a7e2b7@amlogic.com> (raw)
The existing locking mechanism of CCF can effectively avoid concurrent
register access. struct meson_clk_mpll_data has no meaning in defining
a spinlock repeatedly.
In addition, the register corresponding to MPLL does not share the same
register with other module drivers, so there is no concurrent access to
the register with other modules drivers.
Every driver file with mpll defines a spinlock with the same name (even
if defined as "static"), giving the illusion of repeated definitions?
Signed-off-by: Chuan Liu <chuan.liu@amlogic.com>
---
Chuan Liu (6):
clk: meson: mpll: Delete a meaningless spinlock from the MPLL
clk: meson: axg: Delete the spinlock from the MPLL
clk: meson: meson8b: Delete the spinlock from the MPLL
clk: meson: gxbb: Delete the spinlock from the MPLL
clk: meson: g12a: Delete the spinlock from the MPLL
clk: meson: s4: Delete the spinlock from the MPLL
drivers/clk/meson/axg.c | 6 ------
drivers/clk/meson/clk-mpll.c | 11 -----------
drivers/clk/meson/clk-mpll.h | 1 -
drivers/clk/meson/g12a.c | 6 ------
drivers/clk/meson/gxbb.c | 6 ------
drivers/clk/meson/meson8b.c | 3 ---
drivers/clk/meson/s4-pll.c | 6 ------
7 files changed, 39 deletions(-)
---
base-commit: 0ef513560b53d499c824b77220c537eafe1df90d
change-id: 20240918-mpll_spinlock-4b9b55c44fd5
Best regards,
--
Chuan Liu <chuan.liu@amlogic.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2024-09-20 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 8:16 Chuan Liu via B4 Relay [this message]
2024-09-20 8:16 ` [PATCH 1/6] clk: meson: mpll: " Chuan Liu via B4 Relay
2024-09-20 8:16 ` [PATCH 2/6] clk: meson: axg: Delete the " Chuan Liu via B4 Relay
2024-09-20 8:16 ` [PATCH 3/6] clk: meson: meson8b: " Chuan Liu via B4 Relay
2024-09-20 8:16 ` [PATCH 4/6] clk: meson: gxbb: " Chuan Liu via B4 Relay
2024-09-20 8:16 ` [PATCH 5/6] clk: meson: g12a: " Chuan Liu via B4 Relay
2024-09-20 8:16 ` [PATCH 6/6] clk: meson: s4: " Chuan Liu via B4 Relay
2024-09-24 8:35 ` [PATCH 0/6] clk: meson: Delete a meaningless " Jerome Brunet
2024-09-24 8:48 ` Chuan Liu
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=20240920-mpll_spinlock-v1-0-5249a9a7e2b7@amlogic.com \
--to=devnull+chuan.liu.amlogic.com@kernel.org \
--cc=chuan.liu@amlogic.com \
--cc=jbrunet@baylibre.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=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=sboyd@kernel.org \
/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
all inboxes | Powered by JetHome®