From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: "jay.xu@rock-chips.com" <jay.xu@rock-chips.com>
Cc: "Tao Huang" <huangtao@rock-chips.com>,
杨凯 <kever.yang@rock-chips.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Heiko Stübner" <heiko@sntech.de>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND 0/7] gpio-rockchip driver
Date: Fri, 26 Mar 2021 14:07:16 +0100 [thread overview]
Message-ID: <CAMpxmJWmUu962YrcCQmxukV3hM9K8hGVuOzimZ5friX58oSDWw@mail.gmail.com> (raw)
In-Reply-To: <202103241450286417142@rock-chips.com>
On Wed, Mar 24, 2021 at 7:50 AM jay.xu@rock-chips.com
<jay.xu@rock-chips.com> wrote:
>
> I'm forget to send-to include Bartosz, I'll remember in next version
>
> --------------
> jay.xu@rock-chips.com
> >Separate gpio driver from pinctrl driver, and support v2 controller.
> >
> >Jianqun Xu (7):
> > 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
> > gpio/rockchip: use struct rockchip_gpio_regs for gpio controller
> > gpio/rockchip: support next version gpio controller
> > gpio/rockchip: always enable clock for gpio controller
> > gpio/rockchip: drop irq_gc_lock/irq_gc_unlock for irq set type
> >
> > drivers/gpio/Kconfig | 8 +
> > drivers/gpio/Makefile | 1 +
> > drivers/gpio/gpio-rockchip.c | 758 ++++++++++++++++++++++++
> > drivers/pinctrl/pinctrl-rockchip.c | 909 +----------------------------
> > drivers/pinctrl/pinctrl-rockchip.h | 286 +++++++++
> > 5 files changed, 1072 insertions(+), 890 deletions(-)
> > create mode 100644 drivers/gpio/gpio-rockchip.c
> > create mode 100644 drivers/pinctrl/pinctrl-rockchip.h
> >
> >--
> >2.25.1
> >
> >
> >
I don't even have this in my inbox so I can't review it.
Bartosz
next prev parent reply other threads:[~2021-03-26 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 6:45 [PATCH RESEND 0/7] gpio-rockchip driver Jianqun Xu
2021-03-24 6:45 ` [PATCH 1/7] pinctrl/rockchip: separate struct rockchip_pin_bank to a head file Jianqun Xu
2021-03-24 6:45 ` [PATCH 2/7] pinctrl/pinctrl-rockchip.h: add pinctrl device to gpio bank struct Jianqun Xu
2021-03-24 6:45 ` [PATCH 3/7] gpio: separate gpio driver from pinctrl-rockchip driver Jianqun Xu
2021-03-24 6:45 ` [PATCH 4/7] gpio/rockchip: use struct rockchip_gpio_regs for gpio controller Jianqun Xu
2021-03-24 6:47 ` [PATCH 5/7] gpio/rockchip: support next version " Jianqun Xu
2021-03-24 6:47 ` [PATCH 6/7] gpio/rockchip: always enable clock for " Jianqun Xu
2021-03-24 6:47 ` [PATCH 7/7] gpio/rockchip: drop irq_gc_lock/irq_gc_unlock for irq set type Jianqun Xu
2021-03-24 6:50 ` [PATCH RESEND 0/7] gpio-rockchip driver jay.xu
2021-03-26 13:07 ` Bartosz Golaszewski [this message]
2021-04-10 20:41 ` Ezequiel Garcia
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=CAMpxmJWmUu962YrcCQmxukV3hM9K8hGVuOzimZ5friX58oSDWw@mail.gmail.com \
--to=bgolaszewski@baylibre.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@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;
as well as URLs for NNTP newsgroup(s).