From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
Chris Healy <cphealy@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Voltage monitor on ZII's VF610 boards
Date: Tue, 14 Jan 2020 07:19:01 -0800 [thread overview]
Message-ID: <20200114151906.25491-1-andrew.smirnov@gmail.com> (raw)
Everyone:
This series configures voltage supply rail monitoring on all
applicable ZII VF610 boards. Should be pretty straightforward, but let
me know if any changes are necessary.
Thanks,
Andrey Smirnov
Andrey Smirnov (5):
ARM: dts: vf610-zii-ssmb-spu3: Add voltage monitor DT node
ARM: dts: vf610-zii-ssmb-dtu: Add voltage monitor DT node
ARM: dts: vf610-zii-spb4: Add voltage monitor DT node
ARM: dts: vf610-zii-dev: Add voltage monitor DT node
ARM: dts: vf610-zii-cfu1: Add voltage monitor DT node
arch/arm/boot/dts/vf610-zii-cfu1.dts | 8 ++++++++
arch/arm/boot/dts/vf610-zii-dev.dtsi | 8 ++++++++
arch/arm/boot/dts/vf610-zii-spb4.dts | 8 ++++++++
arch/arm/boot/dts/vf610-zii-ssmb-dtu.dts | 8 ++++++++
arch/arm/boot/dts/vf610-zii-ssmb-spu3.dts | 8 ++++++++
5 files changed, 40 insertions(+)
--
2.21.0
next reply other threads:[~2020-01-14 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 15:19 Andrey Smirnov [this message]
2020-01-14 15:19 ` [PATCH 1/5] ARM: dts: vf610-zii-ssmb-spu3: Add voltage monitor DT node Andrey Smirnov
2020-01-14 15:19 ` [PATCH 2/5] ARM: dts: vf610-zii-ssmb-dtu: " Andrey Smirnov
2020-01-14 15:19 ` [PATCH 3/5] ARM: dts: vf610-zii-spb4: " Andrey Smirnov
2020-01-14 15:19 ` [PATCH 4/5] ARM: dts: vf610-zii-dev: " Andrey Smirnov
2020-01-14 15:19 ` [PATCH 5/5] ARM: dts: vf610-zii-cfu1: " Andrey Smirnov
2020-02-12 14:01 ` [PATCH 0/5] Voltage monitor on ZII's VF610 boards Shawn Guo
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=20200114151906.25491-1-andrew.smirnov@gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@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).