linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jianqun Xu <jay.xu@rock-chips.com>
To: heiko@sntech.de, linus.walleij@linaro.org
Cc: linux-gpio@vger.kernel.org, linux-rockchip@lists.infradead.org,
	robh+dt@kernel.org, kever.yang@rock-chips.com,
	Jianqun Xu <jay.xu@rock-chips.com>
Subject: [PATCH v6 0/9] gpio-rockchip driver
Date: Fri, 18 Jun 2021 14:24:40 +0800	[thread overview]
Message-ID: <20210618062449.1067106-1-jay.xu@rock-chips.com> (raw)

Separate gpio driver from pinctrl driver, and support gpio v2 controller.

Jianqun Xu (8):
  pinctrl/rockchip: always enable clock for gpio controller
  pinctrl/rockchip: separate struct rockchip_pin_bank to a head file
  pinctrl/rockchip: add pinctrl device to gpio bank struct
  gpio/rockchip: add driver for rockchip gpio
  gpio/rockchip: use struct rockchip_gpio_regs for gpio controller
  gpio/rockchip: support next version gpio controller
  gpio/rockchip: drop irq_gc_lock/irq_gc_unlock for irq set type
  pinctrl/rockchip: drop the gpio related codes

Liang Chen (1):
  dt-bindings: gpio: change items restriction of clock for
    rockchip,gpio-bank

 .../bindings/gpio/rockchip,gpio-bank.yaml     |   5 +-
 drivers/gpio/Kconfig                          |   8 +
 drivers/gpio/Makefile                         |   1 +
 drivers/gpio/gpio-rockchip.c                  | 766 +++++++++++++++
 drivers/pinctrl/pinctrl-rockchip.c            | 911 +-----------------
 drivers/pinctrl/pinctrl-rockchip.h            | 287 ++++++
 6 files changed, 1085 insertions(+), 893 deletions(-)
 create mode 100644 drivers/gpio/gpio-rockchip.c
 create mode 100644 drivers/pinctrl/pinctrl-rockchip.h

-- 
v6:
 - new gpio-driver first and then drop gpio from pinctrl
 - reorder patches
 - cherry-pick gpio dt-binding from chenliang

v5:
 - change to devel branch

2.25.1




             reply	other threads:[~2021-06-18  6:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  6:24 Jianqun Xu [this message]
2021-06-18  6:24 ` [PATCH 1/9] pinctrl/rockchip: always enable clock for gpio controller Jianqun Xu
2021-06-18  6:24 ` [PATCH 2/9] pinctrl/rockchip: separate struct rockchip_pin_bank to a head file Jianqun Xu
2021-06-18  6:24 ` [PATCH 3/9] pinctrl/rockchip: add pinctrl device to gpio bank struct Jianqun Xu
2021-06-18  6:24 ` [PATCH 4/9] dt-bindings: gpio: change items restriction of clock for rockchip,gpio-bank Jianqun Xu
2021-06-22 13:02   ` Heiko Stübner
2021-06-23 17:24     ` Rob Herring
2021-06-18  6:27 ` Jianqun Xu
2021-06-18  6:27 ` [PATCH 5/9] gpio/rockchip: add driver for rockchip gpio Jianqun Xu
2021-06-18  6:28 ` [PATCH 6/9] gpio/rockchip: use struct rockchip_gpio_regs for gpio controller Jianqun Xu
2021-06-18  6:28 ` [PATCH 7/9] gpio/rockchip: support next version " Jianqun Xu
2021-06-18  6:29 ` [PATCH 8/9] gpio/rockchip: drop irq_gc_lock/irq_gc_unlock for irq set type Jianqun Xu
2021-06-18  6:29 ` [PATCH 9/9] pinctrl/rockchip: drop the gpio related codes Jianqun Xu
2021-07-23 10:12   ` Linus Walleij
2021-07-23 10:07 ` [PATCH v6 0/9] gpio-rockchip driver Linus Walleij
2021-07-23 10:14   ` Linus Walleij
2021-07-23 13:47     ` Peter Geis

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=20210618062449.1067106-1-jay.xu@rock-chips.com \
    --to=jay.xu@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=kever.yang@rock-chips.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.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).