public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Marek Behun <marek.behun@nic.cz>
To: arm@kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: [GIT PULL] Turris Mox Moxtet bus
Date: Thu, 28 Mar 2019 19:22:32 +0100	[thread overview]
Message-ID: <20190328192232.4b5c993a@nic.cz> (raw)

Hello arm-soc maintainers,

please pull the implementation of the Moxtet bus driver into arm-soc/for-next.
Moxtet is a small bus found on Turris Mox.
The patches are reviewed by Linus Walleij and Rob Herring.

Thanks,
Marek

The following changes since commit 93958742192e7956d05989836ada9071f9ffe42e:

  arm64: tegra: Disable CQE Support for SDMMC4 on Tegra186 (2019-03-25 17:12:20 +0100)

are available in the Git repository at:

  https://gitlab.labs.nic.cz/turris/mox-kernel.git/ arm-soc-moxtet-bus

for you to fetch changes up to cea960603584ff05ae6dba647d1641508e5998b4:

  dt-bindings: gpio: Document GPIOs via Moxtet bus (2019-03-28 19:03:01 +0100)

----------------------------------------------------------------
Marek Behún (5):
      bus: Add support for Moxtet bus
      dt-bindings: bus: Document moxtet bus binding
      bus: moxtet: Add sysfs and debugfs documentation
      drivers: gpio: Add support for GPIOs over Moxtet bus
      dt-bindings: gpio: Document GPIOs via Moxtet bus

 Documentation/ABI/testing/debugfs-moxtet               |  23 ++
 Documentation/ABI/testing/sysfs-bus-moxtet-devices     |  17 ++
 Documentation/devicetree/bindings/bus/moxtet.txt       |  46 ++++
 Documentation/devicetree/bindings/gpio/gpio-moxtet.txt |  18 ++
 MAINTAINERS                                            |  12 ++
 drivers/bus/Kconfig                                    |  10 +
 drivers/bus/Makefile                                   |   1 +
 drivers/bus/moxtet.c                                   | 886 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 drivers/gpio/Kconfig                                   |   9 +
 drivers/gpio/Makefile                                  |   1 +
 drivers/gpio/gpio-moxtet.c                             | 179 ++++++++++++++++
 include/dt-bindings/bus/moxtet.h                       |  16 ++
 include/linux/moxtet.h                                 | 109 ++++++++++
 13 files changed, 1327 insertions(+)
 create mode 100644 Documentation/ABI/testing/debugfs-moxtet
 create mode 100644 Documentation/ABI/testing/sysfs-bus-moxtet-devices
 create mode 100644 Documentation/devicetree/bindings/bus/moxtet.txt
 create mode 100644 Documentation/devicetree/bindings/gpio/gpio-moxtet.txt
 create mode 100644 drivers/bus/moxtet.c
 create mode 100644 drivers/gpio/gpio-moxtet.c
 create mode 100644 include/dt-bindings/bus/moxtet.h
 create mode 100644 include/linux/moxtet.h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-03-28 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 18:22 Marek Behun [this message]
2019-04-28 19:06 ` [GIT PULL] Turris Mox Moxtet bus Olof Johansson
2019-04-28 21:40   ` Marek Behun

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=20190328192232.4b5c993a@nic.cz \
    --to=marek.behun@nic.cz \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@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