From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Hawkins, Nick" <nick.hawkins@hpe.com>,
"jdelvare@suse.com" <jdelvare@suse.com>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"Verdun, Jean-Marie" <verdun@hpe.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1 3/6] dt-bindings: hwmon: Add hpe,gxp-fan-ctrl
Date: Tue, 8 Nov 2022 12:22:08 +0100 [thread overview]
Message-ID: <95f588d2-04f3-0be6-ebce-cb6957f5aa1a@linaro.org> (raw)
In-Reply-To: <236F9C0A-797D-41C6-B342-4C32DF28C426@hpe.com>
On 07/11/2022 23:36, Hawkins, Nick wrote:
>
> > > 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?
>
> Greetings Krzysztof,
>
> Thank you for the feedback. The intention was this binding.. however, that was an error on my part, and I will correct it to reflect the hardware situation of the GXP with the fan controller and how each of the mapped registers provide control to the system. To answer your questions: The fans speeds are controlled through an external CPLD device which we provide a PWM value (0-255) using the "base" register to the CIF interface.
Wrap your emails, it's impossible to simply reply to it.
Then your CIF interface is a PWM device?
> This interface provides access to the CPLD. The CPLD then drives the fan. The CPLD can generate up to 8 unique different PWMs to multiple fans.
So you have other CPLD (not external) which generates PWM based on first
CPLD base register? Hm, I think it's one CPLD.
> The CPLD monitors the fans and reports the status back to the SoC through the CIF interface to the "plreg base". The plreg includes the installation, failed, and identification statuses. The function 2 register base is used to check the power state of the system as that influences the PWM values read back.
> As the PWM generation happens outside the SoC do we still need pwm-cells? If so, should we have a custom compatible for that?
>
Depends, if these are actually tightly coupled and you cannot use PWM
for anything else, then you do not need.
> Thanks,
>
> -Nick
>
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-08 11:22 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
2022-11-07 22:36 ` Hawkins, Nick
2022-11-08 11:22 ` Krzysztof Kozlowski [this message]
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=95f588d2-04f3-0be6-ebce-cb6957f5aa1a@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;
as well as URLs for NNTP newsgroup(s).