From: Jeffy Chen <jeffy.chen@rock-chips.com>
To: linux-kernel@vger.kernel.org, broonie@kernel.org,
alexandre.belloni@bootlin.com
Cc: Guenter Roeck <linux@roeck-us.net>, Arnd Bergmann <arnd@arndb.de>,
Joseph Lo <josephl@nvidia.com>, Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
lee.jones@linaro.org, Emil Renner Berthing <kernel@esmil.dk>,
Heiko Stuebner <heiko@sntech.de>,
Brian Norris <briannorris@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Philippe Ombredanne <pombredanne@nexb.com>,
linux-rockchip@lists.infradead.org,
Kate Stewart <kstewart@linuxfoundation.org>,
linux-input@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
Matthias Kaehlcke <mka@chromium.org>,
devicetree@vger.kernel.org, stephen lu <lumotuwe@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arvind Yadav <arvind.yadav.cs@gmail.com>
Subject: [PATCH v5 2/4] rtc: at91sam9: Set name of regmap_config
Date: Mon, 12 Mar 2018 17:51:40 +0800 [thread overview]
Message-ID: <20180312095142.30854-3-jeffy.chen@rock-chips.com> (raw)
In-Reply-To: <20180312095142.30854-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 v5: None
Changes in v4:
Not to use rtc dev to init regmap, the gpbr is not directly related to
the rtc.
Changes in v3: None
drivers/rtc/rtc-at91sam9.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/rtc/rtc-at91sam9.c b/drivers/rtc/rtc-at91sam9.c
index 7418a763ce52..ee71e647fd43 100644
--- a/drivers/rtc/rtc-at91sam9.c
+++ b/drivers/rtc/rtc-at91sam9.c
@@ -349,6 +349,7 @@ static const struct rtc_class_ops at91_rtc_ops = {
};
static const struct regmap_config gpbr_regmap_config = {
+ .name = "gpbr",
.reg_bits = 32,
.val_bits = 32,
.reg_stride = 4,
--
2.11.0
next prev parent reply other threads:[~2018-03-12 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 9:51 [PATCH v5 0/4] Set name of regmap_config Jeffy Chen
2018-03-12 9:51 ` [PATCH v5 1/4] mfd: syscon: " Jeffy Chen
2018-03-12 14:06 ` Lee Jones
2018-03-12 9:51 ` Jeffy Chen [this message]
2018-03-13 0:37 ` [PATCH v5 2/4] rtc: at91sam9: " Alexandre Belloni
2018-03-12 9:51 ` [PATCH v5 3/4] clk: lpc32xx: " Jeffy Chen
2018-03-18 21:57 ` Vladimir Zapolskiy
2018-03-19 3:59 ` JeffyChen
2018-03-12 9:51 ` [PATCH v5 4/4] ARM: rockchip: " Jeffy Chen
2018-03-12 10:11 ` Heiko Stuebner
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=20180312095142.30854-3-jeffy.chen@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=arvind.yadav.cs@gmail.com \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=josephl@nvidia.com \
--cc=kernel@esmil.dk \
--cc=kstewart@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=lumotuwe@gmail.com \
--cc=mka@chromium.org \
--cc=pombredanne@nexb.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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 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).