From: Tomer Maimon <tmaimon77@gmail.com>
To: linus.walleij@linaro.org, robh+dt@kernel.org,
mark.rutland@arm.com, yuenn@google.com, venture@google.com,
brendanhiggins@google.com, avifishman70@gmail.com,
joel@jms.id.au
Cc: devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Tomer Maimon <tmaimon77@gmail.com>
Subject: [PATCH v4 0/2] pinctrl: nuvoton: add driver for NPCM7xx
Date: Mon, 30 Jul 2018 14:04:04 +0300 [thread overview]
Message-ID: <20180730110406.132729-1-tmaimon77@gmail.com> (raw)
This patch set adds pinmux and GPIO controller for the Nuvoton
NPCM750/730/715/705 Baseboard Management Controller (BMC).
The Nuvoton BMC NPCM750/730/715/705 Pinmux functions accessible
only for pin groups and pinconf parameters available only for
individual pins.
The Nuvoton BMC NPCM750/730/715/705 has eight identical GPIO
modules, each module has 32 GPIO ports.
Most of the GPIO ports are multiplexed with other system functions.
The NPCM7xx pinctrl and GPIO driver tested on NPCM750 evaluation board.
this patch set depend on
gpio: mmio: add inverted direction get_set io support approval.
https://lore.kernel.org/patchwork/patch/968891/
without adding BGPIOF_INVERTED_REG_DIR to include/linux/gpio/driver.h
the build will failed.
Addressed comments from:.
- kbuild test robot: https://www.spinics.net/lists/kernel/msg2868491.html
conversion about it with Linus Walleij:
- https://www.spinics.net/lists/devicetree/msg241973.html
Changes since version 3:
- Remove Kconfig MFD_SYSCON dependency.
- Add BGPIOF_INVERTED_REG_DIR flag.
- dt-binding documentation haven't changed.
Changes since version 2:
- Using GPIO_GENERIC (mmio).
- Add Kconfig MFD_SYSCON dependency.
- Remove unnecessary code from the direction output function.
- dt-binding documentation haven't changed.
Changes since version 1:
- Remove Kconfig MFD_SYSCON dependency.
- Modify setfunc function.
- Modify dt-binding documentation according Rob comments.
Tomer Maimon (2):
dt-binding: pinctrl: Add NPCM7xx pinctrl and GPIO documentation
pinctrl: nuvoton: add NPCM7xx pinctrl and GPIO driver
.../bindings/pinctrl/nuvoton,npcm7xx-pinctrl.txt | 216 ++
drivers/pinctrl/Kconfig | 1 +
drivers/pinctrl/Makefile | 1 +
drivers/pinctrl/nuvoton/Kconfig | 12 +
drivers/pinctrl/nuvoton/Makefile | 4 +
drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c | 2082 ++++++++++++++++++++
6 files changed, 2316 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/nuvoton,npcm7xx-pinctrl.txt
create mode 100644 drivers/pinctrl/nuvoton/Kconfig
create mode 100644 drivers/pinctrl/nuvoton/Makefile
create mode 100644 drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c
--
2.14.1
next reply other threads:[~2018-07-30 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 11:04 Tomer Maimon [this message]
2018-07-30 11:04 ` [PATCH v4 1/2] dt-binding: pinctrl: Add NPCM7xx pinctrl and GPIO documentation Tomer Maimon
2018-07-30 23:08 ` Rob Herring
2018-07-30 11:04 ` [PATCH v4 2/2] pinctrl: nuvoton: add NPCM7xx pinctrl and GPIO driver Tomer Maimon
2018-08-03 0:09 ` 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=20180730110406.132729-1-tmaimon77@gmail.com \
--to=tmaimon77@gmail.com \
--cc=avifishman70@gmail.com \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=venture@google.com \
--cc=yuenn@google.com \
/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).