From: Jeffy Chen <jeffy.chen@rock-chips.com>
To: linux-kernel@vger.kernel.org, broonie@kernel.org,
alexandre.belloni@bootlin.com
Cc: Jeffy Chen <jeffy.chen@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Russell King <linux@armlinux.org.uk>,
Heiko Stuebner <heiko@sntech.de>
Subject: [PATCH v4 4/4] ARM: rockchip: Set name of regmap_config
Date: Fri, 9 Mar 2018 09:51:46 +0800 [thread overview]
Message-ID: <20180309015146.8297-5-jeffy.chen@rock-chips.com> (raw)
In-Reply-To: <20180309015146.8297-1-jeffy.chen@rock-chips.com>
We are now allowing to register debugfs without a valid device, and not
having a valid name will end up using "dummy*" to create debugfs dir.
Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
---
Changes in v4: None
Changes in v3: None
arch/arm/mach-rockchip/platsmp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-rockchip/platsmp.c b/arch/arm/mach-rockchip/platsmp.c
index ecec340ca345..51984a40b097 100644
--- a/arch/arm/mach-rockchip/platsmp.c
+++ b/arch/arm/mach-rockchip/platsmp.c
@@ -208,6 +208,7 @@ static int __init rockchip_smp_prepare_sram(struct device_node *node)
}
static const struct regmap_config rockchip_pmu_regmap_config = {
+ .name = "rockchip-pmu",
.reg_bits = 32,
.val_bits = 32,
.reg_stride = 4,
--
2.11.0
next prev parent reply other threads:[~2018-03-09 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 1:51 [PATCH v4 0/4] Set name of regmap_config Jeffy Chen
2018-03-09 1:51 ` [PATCH v4 1/4] mfd: syscon: " Jeffy Chen
2018-03-09 8:15 ` Lee Jones
2018-03-09 1:51 ` [PATCH v4 2/4] rtc: at91sam9: " Jeffy Chen
2018-03-09 1:51 ` [PATCH v4 3/4] clk: lpc32xx: " Jeffy Chen
2018-03-09 1:51 ` Jeffy Chen [this message]
2018-03-09 8:16 ` [PATCH v4 0/4] " Lee Jones
2018-03-09 8:45 ` JeffyChen
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=20180309015146.8297-5-jeffy.chen@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).