From: Anand Moon <linux.amoon@gmail.com>
To: linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Anand Moon <linux.amoon@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
devicetree@vger.kernel.org
Subject: [PATCHv2 0/3] Fix the pwm regulator supply properties
Date: Mon, 5 Jul 2021 11:23:52 +0000 [thread overview]
Message-ID: <20210705112358.3554-1-linux.amoon@gmail.com> (raw)
Changes PWM supply properties help fix internal link of PWM to
main 5V supply as per the shematics.
PATCHv1 below
[0] https://lore.kernel.org/linux-amlogic/CANAwSgRD9_B7f5UjPrxeL+x-eMMc2MAG3tXLQw36x0ho+ba_Uw@mail.gmail.com/T/#t
Thanks
-Anand
Anand Moon (3):
ARM: dts: meson8b: odroidc1: Fix the pwm regulator supply properties
ARM: dts: meson8b: mxq: Fix the pwm regulator supply properties
ARM: dts: meson8b: ec100: Fix the pwm regulator supply properties
arch/arm/boot/dts/meson8b-ec100.dts | 4 ++--
arch/arm/boot/dts/meson8b-mxq.dts | 4 +++-
arch/arm/boot/dts/meson8b-odroidc1.dts | 4 ++--
3 files changed, 7 insertions(+), 5 deletions(-)
--
2.32.0
next reply other threads:[~2021-07-05 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 11:23 Anand Moon [this message]
2021-07-05 11:23 ` [PATCHv2 1/3] ARM: dts: meson8b: odroidc1: Fix the pwm regulator supply properties Anand Moon
2021-07-08 12:58 ` Martin Blumenstingl
2021-07-26 8:06 ` Neil Armstrong
2021-07-05 11:23 ` [PATCHv2 2/3] ARM: dts: meson8b: mxq: " Anand Moon
2021-07-08 12:58 ` Martin Blumenstingl
2021-07-05 11:23 ` [PATCHv2 3/3] ARM: dts: meson8b: ec100: " Anand Moon
2021-07-08 12:58 ` Martin Blumenstingl
2021-07-26 8:12 ` [PATCHv2 0/3] " Neil Armstrong
2021-09-19 20:29 Anand Moon
2021-09-20 8:28 ` Neil Armstrong
2021-09-20 20:13 ` Martin Blumenstingl
2021-09-21 7:21 ` Neil Armstrong
2021-09-21 7:23 ` Neil Armstrong
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=20210705112358.3554-1-linux.amoon@gmail.com \
--to=linux.amoon@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@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).