From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: linux-tegra@vger.kernel.org
Subject: [PATCH v1 0/6] Nexus 7 and A500 device-tree improvements
Date: Mon, 26 Oct 2020 01:38:45 +0300 [thread overview]
Message-ID: <20201025223851.6984-1-digetx@gmail.com> (raw)
This small series improves device-trees of Nexus 7 and A500 devices by
correcting old and adding new DT properties.
Dmitry Osipenko (6):
ARM: tegra: acer-a500: Correct thermal zone names
ARM: tegra: acer-a500: Add power-supply to lvds-encoder node
ARM: tegra: nexus7: Correct thermal zone names
ARM: tegra: nexus7: Improve CPU passive-cooling threshold
ARM: tegra: nexus7: Add power-supply to lvds-encoder node
ARM: tegra: nexus7: Rename gpio-hog nodes
arch/arm/boot/dts/tegra20-acer-a500-picasso.dts | 5 +++--
.../dts/tegra30-asus-nexus7-grouper-common.dtsi | 15 ++++++++-------
.../tegra30-asus-nexus7-grouper-maxim-pmic.dtsi | 2 +-
.../arm/boot/dts/tegra30-asus-nexus7-tilapia.dtsi | 2 +-
4 files changed, 13 insertions(+), 11 deletions(-)
--
2.27.0
next reply other threads:[~2020-10-25 22:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 22:38 Dmitry Osipenko [this message]
2020-10-25 22:38 ` [PATCH v1 1/6] ARM: tegra: acer-a500: Correct thermal zone names Dmitry Osipenko
2020-10-25 22:38 ` [PATCH v1 2/6] ARM: tegra: acer-a500: Add power-supply to lvds-encoder node Dmitry Osipenko
2020-10-25 22:38 ` [PATCH v1 3/6] ARM: tegra: nexus7: Correct thermal zone names Dmitry Osipenko
2020-10-25 22:38 ` [PATCH v1 4/6] ARM: tegra: nexus7: Improve CPU passive-cooling threshold Dmitry Osipenko
2020-10-25 22:38 ` [PATCH v1 5/6] ARM: tegra: nexus7: Add power-supply to lvds-encoder node Dmitry Osipenko
2020-10-25 22:38 ` [PATCH v1 6/6] ARM: tegra: nexus7: Rename gpio-hog nodes Dmitry Osipenko
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=20201025223851.6984-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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).