From: Jianqun Xu <jay.xu@rock-chips.com>
To: huangtao@rock-chips.com, kever.yang@rock-chips.com,
linus.walleij@linaro.org, heiko@sntech.de
Cc: linux-gpio@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, Jianqun Xu <jay.xu@rock-chips.com>
Subject: [PATCH 2/3] pinctrl/pinctrl-rockchip.h: add pinctrl device to gpio bank struct
Date: Mon, 22 Mar 2021 18:43:09 +0800 [thread overview]
Message-ID: <20210322104310.863029-3-jay.xu@rock-chips.com> (raw)
In-Reply-To: <20210322104310.863029-1-jay.xu@rock-chips.com>
Store a pointer from the pinctrl device for the gpio bank.
Signed-off-by: Jianqun Xu <jay.xu@rock-chips.com>
---
drivers/pinctrl/pinctrl-rockchip.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pinctrl/pinctrl-rockchip.h b/drivers/pinctrl/pinctrl-rockchip.h
index 69e4639214b5..0a816e256ae6 100644
--- a/drivers/pinctrl/pinctrl-rockchip.h
+++ b/drivers/pinctrl/pinctrl-rockchip.h
@@ -80,6 +80,7 @@ struct rockchip_drv {
/**
* struct rockchip_pin_bank
+ * @dev: the pinctrl device bind to the bank
* @reg_base: register base of the gpio bank
* @regmap_pull: optional separate register for additional pull settings
* @clk: clock of the gpio bank
@@ -104,6 +105,7 @@ struct rockchip_drv {
* @route_mask: bits describing the routing pins of per bank
*/
struct rockchip_pin_bank {
+ struct device *dev;
void __iomem *reg_base;
struct regmap *regmap_pull;
struct clk *clk;
--
2.25.1
next prev parent reply other threads:[~2021-03-22 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 10:43 [PATCH 0/3] gpio-rockchip driver Jianqun Xu
2021-03-22 10:43 ` [PATCH 1/3] pinctrl/rockchip: separate struct rockchip_pin_bank to a head file Jianqun Xu
2021-03-22 10:43 ` Jianqun Xu [this message]
2021-03-22 10:43 ` [PATCH 3/3] gpio: separate gpio driver from pinctrl-rockchip driver Jianqun Xu
2021-03-22 12:54 ` [PATCH 0/3] gpio-rockchip driver Linus Walleij
2021-04-08 13:43 ` Linus Walleij
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=20210322104310.863029-3-jay.xu@rock-chips.com \
--to=jay.xu@rock-chips.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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®