From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: tegra: Add supply for temperature sensor on P2888
Date: Wed, 3 Apr 2019 18:44:38 +0200 [thread overview]
Message-ID: <20190403164438.GB1837@ulmo> (raw)
In-Reply-To: <1551197275-8977-1-git-send-email-jonathanh@nvidia.com>
[-- Attachment #1.1: Type: text/plain, Size: 780 bytes --]
On Tue, Feb 26, 2019 at 04:07:55PM +0000, Jon Hunter wrote:
> The VCC supply property is not populated for the temperature sensor on
> the P2888 board and so the following warning is observed on boot ...
>
> lm90 0-004c: 0-004c supply vcc not found, using dummy regulator
>
> On the P2888 board, the VCC supply for the temperature sensor is
> connected to the 'vdd_1v8ls' rail. Add the 'vcc-supply' property for
> the temperature sensor to prevent this warning message from occurring.
>
> Fixes: 8b457812f54b ('arm64: tegra: Add temperature sensor on P2888')
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 1 +
> 1 file changed, 1 insertion(+)
Applied to for-5.2/arm64/dt, thanks.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-04-03 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 16:07 [PATCH] arm64: tegra: Add supply for temperature sensor on P2888 Jon Hunter
2019-04-03 16:44 ` 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=20190403164438.GB1837@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.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).