public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sean Anderson <seanga2@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH v1 0/8] riscv: Add FPIOA and GPIO support for Kendryte K210
Date: Thu,  5 Mar 2020 13:53:20 -0500	[thread overview]
Message-ID: <20200305185328.951011-1-seanga2@gmail.com> (raw)

This patch series adds support for pinmuxing, gpios, and leds on the Kendyte
K210.

This patch series was previously part of
https://patchwork.ozlabs.org/project/uboot/list/?series=161576

This patch series depends on
https://patchwork.ozlabs.org/project/uboot/list/?series=162643

Sean Anderson (8):
  pinctrl: Add support for Kendryte K210 FPIOA
  gpio: sifive: Use generic reg read function
  gpio: dw: Fix warnings about casting int to pointer
  gpio: dw: Add a trailing underscore to generated name
  gpio: dw: Return output value when direction is out
  led: gpio: Default to using node name if label is absent
  riscv: Add pinmux and gpio bindings for Kendryte K210
  riscv: Add FPIOA and GPIO support for Kendryte K210

 MAINTAINERS                                   |   2 +
 arch/riscv/dts/k210-maix-bit.dts              | 196 ++++++
 arch/riscv/dts/k210.dtsi                      |  43 +-
 board/sipeed/maix/Kconfig                     |  12 +
 doc/board/sipeed/maix.rst                     |  64 +-
 .../pinctrl/kendryte,k210-fpioa.txt           | 116 +++
 drivers/gpio/dwapb_gpio.c                     |  33 +-
 drivers/gpio/sifive-gpio.c                    |   2 +-
 drivers/led/led_gpio.c                        |   7 +-
 drivers/pinctrl/Kconfig                       |   1 +
 drivers/pinctrl/Makefile                      |   1 +
 drivers/pinctrl/kendryte/Kconfig              |   7 +
 drivers/pinctrl/kendryte/Makefile             |   1 +
 drivers/pinctrl/kendryte/pinctrl.c            | 666 ++++++++++++++++++
 drivers/pinctrl/kendryte/pinctrl.h            | 325 +++++++++
 include/dt-bindings/pinctrl/k210-pinctrl.h    |  12 +
 16 files changed, 1465 insertions(+), 23 deletions(-)
 create mode 100644 doc/device-tree-bindings/pinctrl/kendryte,k210-fpioa.txt
 create mode 100644 drivers/pinctrl/kendryte/Kconfig
 create mode 100644 drivers/pinctrl/kendryte/Makefile
 create mode 100644 drivers/pinctrl/kendryte/pinctrl.c
 create mode 100644 drivers/pinctrl/kendryte/pinctrl.h
 create mode 100644 include/dt-bindings/pinctrl/k210-pinctrl.h

-- 
2.25.0

             reply	other threads:[~2020-03-05 18:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 18:53 Sean Anderson [this message]
2020-03-05 18:53 ` [PATCH v1 1/8] pinctrl: Add support for Kendryte K210 FPIOA Sean Anderson
2020-03-05 18:53 ` [PATCH v1 2/8] gpio: sifive: Use generic reg read function Sean Anderson
2020-03-05 18:53 ` [PATCH v1 3/8] gpio: dw: Fix warnings about casting int to pointer Sean Anderson
2020-03-05 18:53 ` [PATCH v1 4/8] gpio: dw: Add a trailing underscore to generated name Sean Anderson
2020-03-05 18:53 ` [PATCH v1 5/8] gpio: dw: Return output value when direction is out Sean Anderson
2020-03-05 18:53 ` [PATCH v1 6/8] led: gpio: Default to using node name if label is absent Sean Anderson
2020-03-05 18:53 ` [PATCH v1 7/8] riscv: Add pinmux and gpio bindings for Kendryte K210 Sean Anderson
2020-03-05 18:53 ` [PATCH v1 8/8] riscv: Add FPIOA and GPIO support " Sean Anderson

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=20200305185328.951011-1-seanga2@gmail.com \
    --to=seanga2@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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