From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: am33xx: Map baseboard EEPROM on BeagleBone Black
Date: Mon, 27 Jun 2022 13:57:02 +0300 [thread overview]
Message-ID: <YrmM/nCKXwcqK6n1@atomide.com> (raw)
In-Reply-To: <20220620152150.708664-1-broonie@kernel.org>
* Mark Brown <broonie@kernel.org> [220620 18:17]:
> The identification EEPROM on the BeagleBone Black baseboard is supplied
> by VDD_3V3A which is supplied by LDO4 on the PMIC. Map this as per the DT
> binding for the EEPROM. Since this supply is always-on this has no
> practical impact but it does silence a warning at boot due to using a dummy
> regulator.
Thanks applying into omap-for-v5.20/dt. Sorry looks like I missed your
earlier patch somehow.
Regards,
Tony
prev parent reply other threads:[~2022-06-27 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 15:21 [PATCH] ARM: dts: am33xx: Map baseboard EEPROM on BeagleBone Black Mark Brown
2022-06-27 10:57 ` Tony Lindgren [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=YrmM/nCKXwcqK6n1@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@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).