From: Rikard Falkeborn <rikard.falkeborn@gmail.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, Vinod Koul <vkoul@kernel.org>
Cc: linux-kernel@vger.kernel.org, Roger Quadros <rogerq@ti.com>,
Rikard Falkeborn <rikard.falkeborn@gmail.com>,
Stephen Boyd <sboyd@kernel.org>, Wen Yang <wen.yang99@zte.com.cn>,
YueHaibing <yuehaibing@huawei.com>
Subject: [PATCH 1/2] phy: ti: am654-serdes: Constify regmap_config
Date: Sun, 24 May 2020 11:55:15 +0200 [thread overview]
Message-ID: <20200524095516.25227-2-rikard.falkeborn@gmail.com> (raw)
In-Reply-To: <20200524095516.25227-1-rikard.falkeborn@gmail.com>
regmap_config is not modified and can be made static to allow the compiler
to put it in read-only memory.
Before:
text data bss dec hex filename
12328 3644 64 16036 3ea4 drivers/phy/ti/phy-am654-serdes.o
After:
text data bss dec hex filename
12648 3324 64 16036 3ea4 drivers/phy/ti/phy-am654-serdes.o
Signed-off-by: Rikard Falkeborn <rikard.falkeborn@gmail.com>
---
drivers/phy/ti/phy-am654-serdes.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/phy/ti/phy-am654-serdes.c b/drivers/phy/ti/phy-am654-serdes.c
index 0a166d5a6414..a174b3c3f010 100644
--- a/drivers/phy/ti/phy-am654-serdes.c
+++ b/drivers/phy/ti/phy-am654-serdes.c
@@ -72,7 +72,7 @@ struct serdes_am654_clk_mux {
#define to_serdes_am654_clk_mux(_hw) \
container_of(_hw, struct serdes_am654_clk_mux, hw)
-static struct regmap_config serdes_am654_regmap_config = {
+static const struct regmap_config serdes_am654_regmap_config = {
.reg_bits = 32,
.val_bits = 32,
.reg_stride = 4,
--
2.26.2
next prev parent reply other threads:[~2020-05-24 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 9:55 [PATCH 0/2] drivers/phy/ti: Constify structs Rikard Falkeborn
2020-05-24 9:55 ` Rikard Falkeborn [this message]
2020-05-24 9:55 ` [PATCH 2/2] phy: ti: j721e-wiz: " Rikard Falkeborn
2020-06-24 12:57 ` [PATCH 0/2] drivers/phy/ti: " Vinod Koul
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=20200524095516.25227-2-rikard.falkeborn@gmail.com \
--to=rikard.falkeborn@gmail.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=sboyd@kernel.org \
--cc=vkoul@kernel.org \
--cc=wen.yang99@zte.com.cn \
--cc=yuehaibing@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.