From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: nick.hawkins@hpe.com, jdelvare@suse.com, linux@roeck-us.net,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
verdun@hpe.com, corbet@lwn.net, linux@armlinux.org.uk,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 3/6] dt-bindings: hwmon: Add hpe,gxp-fan-ctrl
Date: Sun, 6 Nov 2022 11:38:27 +0100 [thread overview]
Message-ID: <1b90f86c-9c0f-225b-38b5-6f37a4eded69@linaro.org> (raw)
In-Reply-To: <20221104193657.105130-4-nick.hawkins@hpe.com>
On 04/11/2022 20:36, nick.hawkins@hpe.com wrote:
> From: Nick Hawkins <nick.hawkins@hpe.com>
>
> This provides the base registers address, programmable logic registers
> address, and the function 2 registers to allow control access of the HPE
> fans on the GXP SoC.
What is "This"? If "This patch", then drop it.
https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst#L95
If "This hardware" then please instead describe the hardware, not it
components. What are its features? If it controls the fan, then why
there are no PWM-related cells? How do you set the speed?
>
> Signed-off-by: Nick Hawkins <nick.hawkins@hpe.com>
> ---
> .../bindings/hwmon/hpe,gxp-fan-ctrl.yaml | 41 +++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwmon/hpe,gxp-fan-ctrl.yaml
>
> diff --git a/Documentation/devicetree/bindings/hwmon/hpe,gxp-fan-ctrl.yaml b/Documentation/devicetree/bindings/hwmon/hpe,gxp-fan-ctrl.yaml
> new file mode 100644
> index 000000000000..40a5d9cd0a30
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/hpe,gxp-fan-ctrl.yaml
> @@ -0,0 +1,41 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/hwmon/hpe,gxp-fan-ctrl.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: GXP Fan Controller
> +
> +maintainers:
> + - Nick Hawkins <nick.hawkins@hpe.com>
> +
> +properties:
> + compatible:
> + const: hpe,gxp-fan-ctrl
> +
> + reg:
> + items:
> + - description: Fan controller base register
> + - description: Programmable logic registers base
> + - description: Function 2 registers base
Drop "register" and "base" from all descriptions
> +
> + reg-names:
> + items:
> + - const: base
> + - const: plreg
Drop reg suffix
> + - const: fn2reg
Drop reg suffix
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + fanctrl@1000c00 {
fan-controller
> + compatible = "hpe,gxp-fan-ctrl";
> + reg = <0x1000c00 0x200>, <0xd1000000 0xff>, <0x80200000 0x100000>;
> + reg-names = "base", "plreg", "fn2reg";
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-06 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 19:36 [PATCH v1 0/6] ARM: Add GXP Fan and SPI controllers nick.hawkins
2022-11-04 19:36 ` [PATCH v1 1/6] hwmon: (gxp-fan-ctrl) Add GXP fan controller nick.hawkins
2022-11-04 20:01 ` Guenter Roeck
2022-11-08 16:59 ` Hawkins, Nick
2022-11-08 17:07 ` Hawkins, Nick
2022-11-07 3:56 ` Bagas Sanjaya
2022-11-08 0:45 ` kernel test robot
2022-11-04 19:36 ` [PATCH v1 2/6] ABI: sysfs-class-hwmon: add a description for fanY_fault nick.hawkins
2022-11-04 19:36 ` [PATCH v1 3/6] dt-bindings: hwmon: Add hpe,gxp-fan-ctrl nick.hawkins
2022-11-06 10:38 ` Krzysztof Kozlowski [this message]
2022-11-07 22:36 ` Hawkins, Nick
2022-11-08 11:22 ` Krzysztof Kozlowski
2022-11-04 19:36 ` [PATCH v1 4/6] ARM: dts: add GXP Support for fans and SPI nick.hawkins
2022-11-04 19:36 ` [PATCH v1 5/6] ARM: multi_v7_defconfig: Add GXP Fan and SPI support nick.hawkins
2022-11-06 10:40 ` Krzysztof Kozlowski
2022-11-04 19:36 ` [PATCH v1 6/6] MAINTAINERS: add gxp fan controller and documents nick.hawkins
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=1b90f86c-9c0f-225b-38b5-6f37a4eded69@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=nick.hawkins@hpe.com \
--cc=robh+dt@kernel.org \
--cc=verdun@hpe.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®