From: Thierry Reding <thierry.reding@gmail.com>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, jonathanh@nvidia.com,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: Add INA3221 channel info for Jetson TX2
Date: Tue, 18 Jun 2019 12:57:56 +0200 [thread overview]
Message-ID: <20190618105756.GC28892@ulmo> (raw)
In-Reply-To: <20190617221659.25366-1-nicoleotsuka@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Mon, Jun 17, 2019 at 03:16:59PM -0700, Nicolin Chen wrote:
> There are four INA3221 chips on the Jetson TX2 (p3310 + p2771).
> And each INA3221 chip has three input channels to monitor power.
>
> So this patch adds these 12 channels to the DT of Jetson TX2, by
> following the DT binding of INA3221 and official documents from
> https://developer.nvidia.com/embedded/downloads
>
> tegra186-p3310:
> https://developer.nvidia.com/embedded/dlc/jetson-tx2-series-modules-oem-product-design-guide
>
> tegra186-p2771-0000:
> http://developer.nvidia.com/embedded/dlc/jetson-tx1-tx2-developer-kit-carrier-board-spec-20180618
>
> Signed-off-by: Nicolin Chen <nicoleotsuka@gmail.com>
> ---
> .../boot/dts/nvidia/tegra186-p2771-0000.dts | 40 +++++++++++++++++++
> .../arm64/boot/dts/nvidia/tegra186-p3310.dtsi | 40 +++++++++++++++++++
> 2 files changed, 80 insertions(+)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-06-18 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 22:16 [PATCH] arm64: tegra: Add INA3221 channel info for Jetson TX2 Nicolin Chen
2019-06-18 10:57 ` Thierry Reding [this message]
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=20190618105756.GC28892@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicoleotsuka@gmail.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).