From: Guenter Roeck <linux@roeck-us.net>
To: Wenliang <wenliang202407@163.com>
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
conor+dt@kernel.org, krzk+dt@kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: modified ina2xx to match SY24655
Date: Thu, 24 Oct 2024 09:55:04 -0700 [thread overview]
Message-ID: <e028943e-2acb-4b19-b2eb-dd603855b3a8@roeck-us.net> (raw)
In-Reply-To: <20241024083055.82047-2-wenliang202407@163.com>
On 10/24/24 01:30, Wenliang wrote:
> Adding Silergy's sy24655 as an adapter chip for Ina2xx drivers.
>
> Because it is similar to INA226, the supply voltage and pin definitions
> are the same. It also supports IIC communication, with only two
> additional registers added for configuring and calculating average power.
>
Again, please consult
Documentation/process/submitting-patches.rst
for both description and subject.
"dt-bindings: Add SY24655 to ina2xx devicetree bindings" or similar
would be a much better subject, and something like
"SY24655 is similar to INA226. Its supply voltage and pin definitions
are therefore the same. Compared to INA226, SY24655 has two additional
registers for configuring and calculating average power."
would be a much better patch description.
Also, as already requested by Conor, please copy the devicetree mailing list
on devicetree patches to enable automated testing.
Thanks,
Guenter
> Signed-off-by: Wenliang <wenliang202407@163.com>
> ---
> Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml b/Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml
> index 6ae961732e6b..05a9cb36cd82 100644
> --- a/Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/ti,ina2xx.yaml
> @@ -20,6 +20,7 @@ description: |
> properties:
> compatible:
> enum:
> + - silergy,sy24655
> - ti,ina209
> - ti,ina219
> - ti,ina220
next prev parent reply other threads:[~2024-10-24 16:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <80bfd968-8f12-46b1-9b72-837502ccdb2a@roeck-us.ne>
2024-10-24 8:30 ` [PATCH v3 1/2] hwmon: modified ina2xx to match SY24655 Wenliang
2024-10-24 8:30 ` [PATCH v3 2/2] dt-bindings: " Wenliang
2024-10-24 16:32 ` Conor Dooley
2024-10-24 16:33 ` Conor Dooley
2024-10-24 16:55 ` Guenter Roeck [this message]
2024-10-25 7:56 ` Krzysztof Kozlowski
2024-10-24 17:10 ` [PATCH v3 1/2] hwmon: " Guenter Roeck
2024-11-03 16:39 ` [PATCH linux dev-6.11 v3 1/2] hwmon: (ina226) Add support for SY24655 Wenliang
2024-11-03 16:39 ` [PATCH linux dev-6.11 v3 2/2] dt-bindings: Add SY24655 to ina2xx devicetree bindings Wenliang
2024-11-03 16:46 ` Krzysztof Kozlowski
2024-11-03 16:52 ` Krzysztof Kozlowski
2024-11-03 22:39 ` Conor Dooley
2024-11-03 17:37 ` [PATCH linux dev-6.11 v3 1/2] hwmon: (ina226) Add support for SY24655 Guenter Roeck
2024-11-06 15:05 ` [PATCH " wenliang
2024-11-06 15:05 ` [PATCH v3 2/2] dt-bindings: Add SY24655 to ina2xx devicetree bindings wenliang
2024-11-06 15:31 ` [PATCH v3 1/2] hwmon: (ina226) Add support for SY24655 Guenter Roeck
2024-11-06 15:39 ` 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=e028943e-2acb-4b19-b2eb-dd603855b3a8@roeck-us.net \
--to=linux@roeck-us.net \
--cc=conor+dt@kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wenliang202407@163.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