From: Mark Brown <broonie@kernel.org>
To: "zoie.lin" <zoie.lin@mediatek.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH 1/3] misc: eeprom: at24: add optional dovdd-supply
Date: Tue, 30 Apr 2024 11:53:17 +0900 [thread overview]
Message-ID: <ZjBdHdVUW9Q67nAC@finisterre.sirena.org.uk> (raw)
In-Reply-To: <20240426102949.23057-2-zoie.lin@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
On Fri, Apr 26, 2024 at 06:29:47PM +0800, zoie.lin wrote:
> From: Zoie Lin <zoie.lin@mediatek.com>
>
> Incorporate support for the dovdd regulator, which supplies an
> additional power source to the EEPROM.
It would be helpful if you could supply some additional information
about what this supply is, why we can't tell if it's supposed to be
there or not and so on.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-04-30 2:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 10:29 [PATCH 0/3] misc: eeprom: at24: add optional dovdd-supply zoie.lin
2024-04-26 10:29 ` [PATCH 1/3] " zoie.lin
2024-04-30 2:53 ` Mark Brown [this message]
2024-04-26 10:29 ` [PATCH 2/3] dt-bindings: eeprom: at24: Add support for at24c64 zoie.lin
2024-04-26 10:57 ` Krzysztof Kozlowski
2024-04-26 11:41 ` Rob Herring
2024-04-26 10:29 ` [PATCH 3/3] dt-bindings: eeprom: at24: Add property dovdd-supply zoie.lin
2024-04-26 10:59 ` Krzysztof Kozlowski
2024-04-26 19:10 ` Rob Herring
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=ZjBdHdVUW9Q67nAC@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=zoie.lin@mediatek.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 read-only IMAP folder(s) and NNTP newsgroup(s).