From: Chanh Nguyen <chanh@amperemail.onmicrosoft.com>
To: Chanh Nguyen <chanh@os.amperecomputing.com>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Justin Ledford <justinledford@google.com>,
devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Open Source Submission <patches@amperecomputing.com>
Cc: Phong Vo <phong@os.amperecomputing.com>,
Thang Nguyen <thang@os.amperecomputing.com>,
Quan Nguyen <quan@os.amperecomputing.com>
Subject: Re: [PATCH v3 0/1] Update the max31790 driver
Date: Tue, 13 Aug 2024 15:44:01 +0700 [thread overview]
Message-ID: <50014195-b7b7-4fa8-ae37-2c3e57826c1b@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <20240813084152.25002-1-chanh@os.amperecomputing.com>
Hi all,
I dropped the "Support config PWM output becomes TACH" patch. I'm
implementing and testing the "Support config PWM output become TACH"
support; I'll push this feature later. Now, I'm only adding the device
tree binding for the max31790 device; it is necessary for some device
tree upstreams that use the "maxim,max31790" compatible.
Best Regards,
Chanh
On 13/08/2024 15:41, Chanh Nguyen wrote:
> Add device tree binding for the max31790 device.
>
> Changes in v2:
> - Drop "driver" in the patch 1/3 commit title [Krzysztof]
> - Update filename of the maxim,max31790.yaml [Krzysztof]
> - Add the common fan schema to $ref [Krzysztof]
> - Update the node name to "fan-controller" in maxim,max31790.yaml [Krzysztof]
> - Update the vendor property name to "maxim,pwmout-pin-as-tach-input" [Rob]
> Changes in v3:
> - Drop redundant "bindings" in commit message [Krzysztof]
> - Add the clocks and resets property to example [Krzysztof]
> - Add child node refer to fan-common.yaml [Krzysztof, Conor]
> - Drop "Support config PWM output become TACH" patch [Chanh]
> - Drop "Add maxim,pwmout-pin-as-tach-input property" patch [Chanh]
>
> Chanh Nguyen (1):
> dt-bindings: hwmon: Add maxim max31790
>
> .../bindings/hwmon/maxim,max31790.yaml | 81 +++++++++++++++++++
> 1 file changed, 81 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwmon/maxim,max31790.yaml
>
prev parent reply other threads:[~2024-08-13 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 8:41 [PATCH v3 0/1] Update the max31790 driver Chanh Nguyen
2024-08-13 8:41 ` [PATCH v3 1/1] dt-bindings: hwmon: Add maxim max31790 Chanh Nguyen
2024-08-13 15:33 ` Conor Dooley
2024-08-13 15:52 ` Guenter Roeck
2024-08-13 16:16 ` Conor Dooley
2024-08-13 16:21 ` Krzysztof Kozlowski
2024-08-14 8:58 ` Chanh Nguyen
2024-08-14 7:31 ` Chanh Nguyen
2024-08-13 16:20 ` Krzysztof Kozlowski
2024-08-14 8:54 ` Chanh Nguyen
2024-08-13 8:44 ` Chanh Nguyen [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=50014195-b7b7-4fa8-ae37-2c3e57826c1b@amperemail.onmicrosoft.com \
--to=chanh@amperemail.onmicrosoft.com \
--cc=chanh@os.amperecomputing.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=justinledford@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=robh+dt@kernel.org \
--cc=thang@os.amperecomputing.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