From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Troy Lee" <troy_lee@aspeedtech.com>,
openbmc@lists.ozlabs.org, "Joel Stanley" <joel@jms.id.au>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"open list" <linux-kernel@vger.kernel.org>,
"moderated list:ARM/ASPEED MACHINE SUPPORT"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/ASPEED MACHINE SUPPORT"
<linux-aspeed@lists.ozlabs.org>
Cc: "Ryan Chen" <ryan_chen@aspeedtech.com>,
"Chia-Wei, Wang" <chiawei_wang@aspeedtech.com>,
"Troy Lee" <leetroy@gmail.com>, "Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v3 1/4] dt-bindings: hwmon: Add Aspeed AST2600 PWM/Fan
Date: Fri, 22 Jan 2021 14:56:44 +1030 [thread overview]
Message-ID: <647428e4-49fb-4e2b-9291-895488c9c7f5@www.fastmail.com> (raw)
In-Reply-To: <20210118065059.2478078-2-troy_lee@aspeedtech.com>
On Mon, 18 Jan 2021, at 17:20, Troy Lee wrote:
> We add binding for supporting a new AST2600 PWM/Fan hwmon driver.
>
> Changes since v2:
> - Fixed yamllint warnings/errors
>
> Changes since v1:
> - dt binding with DT schema format
>
> Signed-off-by: Troy Lee <troy_lee@aspeedtech.com>
> Reported-by: Rob Herring <robh@kernel.org>
> ---
> .../hwmon/aspeed,ast2600-pwm-tachometer.yaml | 131 ++++++++++++++++++
> 1 file changed, 131 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/hwmon/aspeed,ast2600-pwm-tachometer.yaml
>
> diff --git
> a/Documentation/devicetree/bindings/hwmon/aspeed,ast2600-pwm-tachometer.yaml b/Documentation/devicetree/bindings/hwmon/aspeed,ast2600-pwm-tachometer.yaml
> new file mode 100644
> index 000000000000..fa5340f5a43f
> --- /dev/null
> +++
> b/Documentation/devicetree/bindings/hwmon/aspeed,ast2600-pwm-tachometer.yaml
> @@ -0,0 +1,131 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +
> +$id:
> http://devicetree.org/schemas/hwmon/aspeed,ast2600-pwm-tachometer.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ASPEED AST2600 PWM and Fan Tacho controller device driver
> +
> +maintainers:
> + - Ryan Chen <ryan_chen@aspeedtech.com>
> +
> +description: |
> + The ASPEED PWM controller can support upto 16 PWM outputs. The
> ASPEED Fan Tacho
> + controller can support upto 16 Fan tachometer inputs.
> + There can be upto 16 fans supported. Each fan can have one PWM
> output and
> + one Fan tach inputs.
> +
> +properties:
> + compatible:
> + const: aspeed,ast2600-pwm-tachometer
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 0
> +
> + "#cooling-cells":
> + const: 2
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + resets:
> + maxItems: 1
> +
> +patternProperties:
> + "^fan@[0-9a-f]$":
> + type: object
> + description:
> + Under fan subnode there can upto 16 child nodes, with each child
> node
> + representing a fan. There are 16 fans each fan can have one PWM
> port and one
> + Fan tach inputs.
> + For PWM port can be configured cooling-levels to create cooling
> device.
> + Cooling device could be bound to a thermal zone for the thermal
> control.
> +
> + properties:
> + reg:
> + minimum: 0
> + maximum: 15
> + description:
> + This property identify the PWM control channel of this fan.
> +
> + fan-tach-ch:
> + $ref: /schemas/types.yaml#/definitions/uint8
> + minimum: 0
> + maximum: 15
> + description:
> + This property identify the fan tach input channel.
> +
> + pulses-per-revolution:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + default: 2
> + minimum: 1
> + description:
> + Specify tacho pulse per revolution of the fan.
> +
> + cooling-levels:
> + description:
> + PWM duty cycle values in a range from 0 to 255
> + which correspond to thermal cooling states.
> +
> + aspeed,pwm-freq-hz:
> + default: 25000
> + minimum: 24
> + maximum: 780000
> + description:
> + Specify the frequency of PWM.
What about using 'bus-frequency' instead?
> +
> + aspeed,inverse-pin:
> + type: boolean
> + description:
> + Inverse PWM output signal.
What's the benefit? I know the hardware provides the function, but do we need to expose it?
> +
> + aspeed,falling-point:
> + $ref: /schemas/types.yaml#/definitions/uint8
> + default: 10
I feel like it probably shouldn't have a default value.
> + description:
> + Initialize the pulse width.
Then can we make the property name a bit more intuitive? 'pwm-duty'? Alternatively, [1] calls the duty "cooling-levels", can we use something in that vein instead?
[1] Documentation/devicetree/bindings/hwmon/pwm-fan.txt
Andrew
next prev parent reply other threads:[~2021-01-22 4:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 6:50 [PATCH v3 0/4] hwmon: aspeed2600-pwm-tacho: Add driver support Troy Lee
2021-01-18 6:50 ` [PATCH v3 1/4] dt-bindings: hwmon: Add Aspeed AST2600 PWM/Fan Troy Lee
2021-01-22 4:26 ` Andrew Jeffery [this message]
2021-01-18 6:50 ` [PATCH v3 2/4] hwmon: Add Aspeed AST2600 support Troy Lee
2021-01-18 6:50 ` [PATCH v3 3/4] ARM: dts: aspeed: Add Aspeed AST2600 PWM/Fan node in devicetree Troy Lee
2021-01-18 6:50 ` [PATCH v3 4/4] hwmon: Support Aspeed AST2600 PWM/Fan tachometer Troy Lee
2021-01-20 5:16 ` Andrew Jeffery
2021-01-20 5:23 ` Ryan Chen
2021-01-20 6:37 ` Andrew Jeffery
2021-01-22 4:38 ` Andrew Jeffery
2021-01-26 10:05 ` Troy Lee
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=647428e4-49fb-4e2b-9291-895488c9c7f5@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=chiawei_wang@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=leetroy@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=troy_lee@aspeedtech.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
all inboxes | Powered by JetHome®