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 0/3] gpio-rockchip driver
Date: Mon, 22 Mar 2021 18:43:07 +0800 [thread overview]
Message-ID: <20210322104310.863029-1-jay.xu@rock-chips.com> (raw)
Separate gpio driver from pinctrl driver.
Jianqun Xu (3):
pinctrl/rockchip: separate struct rockchip_pin_bank to a head file
pinctrl/pinctrl-rockchip.h: add pinctrl device to gpio bank struct
gpio: separate gpio driver from pinctrl-rockchip driver
drivers/gpio/Kconfig | 8 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-rockchip.c | 650 +++++++++++++++++++++
drivers/pinctrl/pinctrl-rockchip.c | 909 +----------------------------
drivers/pinctrl/pinctrl-rockchip.h | 246 ++++++++
5 files changed, 924 insertions(+), 890 deletions(-)
create mode 100644 drivers/gpio/gpio-rockchip.c
create mode 100644 drivers/pinctrl/pinctrl-rockchip.h
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
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 0/3] gpio-rockchip driver
Date: Mon, 22 Mar 2021 18:43:07 +0800 [thread overview]
Message-ID: <20210322104310.863029-1-jay.xu@rock-chips.com> (raw)
Separate gpio driver from pinctrl driver.
Jianqun Xu (3):
pinctrl/rockchip: separate struct rockchip_pin_bank to a head file
pinctrl/pinctrl-rockchip.h: add pinctrl device to gpio bank struct
gpio: separate gpio driver from pinctrl-rockchip driver
drivers/gpio/Kconfig | 8 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-rockchip.c | 650 +++++++++++++++++++++
drivers/pinctrl/pinctrl-rockchip.c | 909 +----------------------------
drivers/pinctrl/pinctrl-rockchip.h | 246 ++++++++
5 files changed, 924 insertions(+), 890 deletions(-)
create mode 100644 drivers/gpio/gpio-rockchip.c
create mode 100644 drivers/pinctrl/pinctrl-rockchip.h
--
2.25.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2021-03-22 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 10:43 Jianqun Xu [this message]
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
2021-03-22 10:43 ` [PATCH 2/3] pinctrl/pinctrl-rockchip.h: add pinctrl device to gpio bank struct Jianqun Xu
2021-03-22 10:43 ` Jianqun Xu
2021-03-22 10:43 ` [PATCH 3/3] gpio: separate gpio driver from pinctrl-rockchip driver Jianqun Xu
2021-03-22 10:43 ` Jianqun Xu
2021-03-22 12:54 ` [PATCH 0/3] gpio-rockchip driver Linus Walleij
2021-03-22 12:54 ` Linus Walleij
2021-04-08 13:43 ` 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-1-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 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.