From: Peter Korsgaard <peter@korsgaard.com>
To: Rob Herring <robh@kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: ti,tmp102: document optional V+ supply property
Date: Tue, 22 Apr 2025 15:31:20 +0200 [thread overview]
Message-ID: <87a588b9w7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250422132602.GA1092156-robh@kernel.org> (Rob Herring's message of "Tue, 22 Apr 2025 08:26:02 -0500")
>>>>> "Rob" == Rob Herring <robh@kernel.org> writes:
> On Thu, Apr 17, 2025 at 08:04:25PM +0200, Peter Korsgaard wrote:
>> TMP102 is powered by its V+ supply, document it. The property is called
>> "vcc-supply" since the plus sign (+) is not a valid property character.
> Wouldn't "vplus-supply" or "vp-supply" work?
It could, but gcc-supply is what we use for the very similar tmp108
binding, so I think it makes sense to use that here for consistency as
well:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=699383466851e3fb8284e1eefeed78ec30989b3b
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2025-04-22 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 18:04 [PATCH 1/2] dt-bindings: hwmon: ti,tmp102: document optional V+ supply property Peter Korsgaard
2025-04-17 18:04 ` [PATCH 2/2] hwmon: (tmp102): add vcc regulator support Peter Korsgaard
2025-04-23 14:17 ` Guenter Roeck
2025-04-22 13:26 ` [PATCH 1/2] dt-bindings: hwmon: ti,tmp102: document optional V+ supply property Rob Herring
2025-04-22 13:31 ` Peter Korsgaard [this message]
2025-04-23 14:03 ` Rob Herring (Arm)
2025-04-23 14:17 ` Guenter Roeck
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=87a588b9w7.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.