From: Tomer Maimon <tmaimon77@gmail.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, avifishman70@gmail.com,
tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
benjaminfair@google.com, joel@jms.id.au
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org, tmaimon77@gmail.com
Subject: [PATCH v8 0/5] arm: dts: add and modify device node in NPCM7xx device tree
Date: Tue, 29 Sep 2020 16:18:02 +0300 [thread overview]
Message-ID: <20200929131807.15378-1-tmaimon77@gmail.com> (raw)
This patch set adds and modify device tree nodes in the NPCM7xx
Baseboard Management Controller (BMC) device tree.
The following device node add:
- NPCM7xx Pin controller and GPIO
- NPCM7xx PWM and FAN.
- NPCM7xx EHCI USB.
- NPCM7xx KCS.
- NPCM Reset.
- NPCM Peripheral SPI.
- NPCM FIU SPI.
- NPCM HWRNG.
- NPCM I2C.
- STMicro STMMAC.
The following device node modified:
- NPCM7xx timer.
- NPCM7xx clock constants parameters.
NPCM7xx device tree tested on NPCM750 evaluation board.
Changes since version 7:
Address comments from Joel Stanely: https://www.spinics.net/lists/devicetree/msg380191.html
Changes since version 6:
Split commits.
Changes since version 5:
Address comments from Joel Stanely: https://lkml.org/lkml/2020/9/16/994
Changes since version 4:
- Tested patches in Linux kernel 5.9.
Changes since version 3:
- Tested patches in Linux kernel 5.6.
Changes since version 2:
- Remove unnecessary output-enable flags.
Changes since version 1:
- Add NPCM reset device node.
- Add reset parameters to NPCM driver device nodes.
Tomer Maimon (5):
arm: dts: modify NPCM7xx device tree clock parameter
arm: dts: modify NPCM7xx device tree timer register size
arm: dts: add pinctrl and GPIO node to NPCM7XX device tree
arm: dts: add new device nodes to NPCM7XX device tree
arm: dts: add new device nodes to NPCM750 device tree EVB
arch/arm/boot/dts/nuvoton-common-npcm7xx.dtsi | 967 +++++++++++++++++-
arch/arm/boot/dts/nuvoton-npcm750-evb.dts | 367 ++++++-
.../boot/dts/nuvoton-npcm750-pincfg-evb.dtsi | 157 +++
arch/arm/boot/dts/nuvoton-npcm750.dtsi | 24 +-
4 files changed, 1495 insertions(+), 20 deletions(-)
create mode 100644 arch/arm/boot/dts/nuvoton-npcm750-pincfg-evb.dtsi
--
2.22.0
next reply other threads:[~2020-09-29 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 13:18 Tomer Maimon [this message]
2020-09-29 13:18 ` [PATCH v8 1/5] arm: dts: modify NPCM7xx device tree clock parameter Tomer Maimon
2020-09-29 13:18 ` [PATCH v8 2/5] arm: dts: modify NPCM7xx device tree timer register size Tomer Maimon
2020-09-29 13:18 ` [PATCH v8 3/5] arm: dts: add pinctrl and GPIO node to NPCM7XX device tree Tomer Maimon
2020-09-29 13:18 ` [PATCH v8 4/5] arm: dts: add new device nodes " Tomer Maimon
2020-09-29 13:18 ` [PATCH v8 5/5] arm: dts: add new device nodes to NPCM750 device tree EVB Tomer Maimon
2020-10-07 11:37 ` Joel Stanley
2020-10-07 11:41 ` [PATCH v8 0/5] arm: dts: add and modify device node in NPCM7xx device tree Joel Stanley
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=20200929131807.15378-1-tmaimon77@gmail.com \
--to=tmaimon77@gmail.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--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).