From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: jdelvare@suse.com, linux@roeck-us.net, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH 1/2] dt-bindings: hwmon: Document adt7475 PWM initial duty cycle
Date: Thu, 9 May 2024 05:05:42 +1200 [thread overview]
Message-ID: <20240508170544.263059-2-chris.packham@alliedtelesis.co.nz> (raw)
In-Reply-To: <20240508170544.263059-1-chris.packham@alliedtelesis.co.nz>
Add documentation for the pwm-initial-duty-cycle and
pwm-initial-frequency properties. These allow the starting state of the
PWM outputs to be set to cater for hardware designs where undesirable
amounts of noise is created by the default hardware state.
Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
---
.../devicetree/bindings/hwmon/adt7475.yaml | 26 ++++++++++++++++++-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/hwmon/adt7475.yaml b/Documentation/devicetree/bindings/hwmon/adt7475.yaml
index 051c976ab711..3de300c9da2a 100644
--- a/Documentation/devicetree/bindings/hwmon/adt7475.yaml
+++ b/Documentation/devicetree/bindings/hwmon/adt7475.yaml
@@ -51,6 +51,29 @@ properties:
enum: [0, 1]
default: 1
+ adi,pwm-initial-duty-cycle:
+ description: |
+ Configures the initial duty cycle for the PWM outputs. The hardware
+ default is 100% but this may cause unwanted fan noise at startup. Set
+ this to a value from 0 (0% duty cycle) to 255 (100% duty cycle).
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+ minItems: 3
+ maxItems: 3
+ items:
+ minimum: 0
+ maximum: 255
+ default: 255
+
+ adi,pwm-initial-frequency:
+ description: |
+ Configures the initial frequency for the PWM outputs.
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+ minItems: 3
+ maxItems: 3
+ items:
+ enum: [11, 14, 22, 29, 35, 44, 58, 88, 22500]
+ default: 35
+
patternProperties:
"^adi,bypass-attenuator-in[0-4]$":
description: |
@@ -80,7 +103,6 @@ patternProperties:
- therm#
- smbalert#
- gpio
-
required:
- compatible
- reg
@@ -99,6 +121,8 @@ examples:
adi,bypass-attenuator-in0 = <1>;
adi,bypass-attenuator-in1 = <0>;
adi,pwm-active-state = <1 0 1>;
+ adi,pwm-initial-duty-cycle = <128 0 128>;
+ adi,pwm-initial-frequency = <22500 0 22500>;
adi,pin10-function = "smbalert#";
adi,pin14-function = "tach4";
};
--
2.43.2
next prev parent reply other threads:[~2024-05-08 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 17:05 [PATCH 0/2] hwmon: (adt7475) duty cycle configuration Chris Packham
2024-05-08 17:05 ` Chris Packham [this message]
2024-05-08 19:00 ` [PATCH 1/2] dt-bindings: hwmon: Document adt7475 PWM initial duty cycle Rob Herring (Arm)
2024-05-08 17:05 ` [PATCH 2/2] hwmon: (adt7475) Add support for configuring initial PWM " Chris Packham
2024-05-08 17:49 ` Chris Packham
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=20240508170544.263059-2-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@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 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).