From: Guenter Roeck <linux@roeck-us.net>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
蔡承達 <billyking19920205@gmail.com>,
"jdelvare@suse.com" <jdelvare@suse.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"andrew@aj.id.au" <andrew@aj.id.au>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>,
"corbet@lwn.net" <corbet@lwn.net>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"patrick@stwcx.xyz" <patrick@stwcx.xyz>,
"Billy Tsai" <billy_tsai@aspeedtech.com>
Subject: Re: [v6 2/4] dt-bindings: hwmon: Add ASPEED TACH Control documentation
Date: Fri, 14 Jul 2023 02:59:40 -0700 [thread overview]
Message-ID: <0ba3767c-d481-6e2c-2d32-b79af0e1efd8@roeck-us.net> (raw)
In-Reply-To: <0b9dd5cf-f4ca-2e6b-624d-0b451bbc2f30@linaro.org>
On 7/14/23 00:13, Krzysztof Kozlowski wrote:
> On 14/07/2023 09:04, 蔡承達 wrote:
>
>> > This is because our register layout for PWM and Tach is not
>> continuous.
>>
>> > PWM0 used 0x0 0x4, Tach0 used 0x8 0xc
>>
>> > PWM1 used 0x10 0x14, Tach1 used 0x18 0x1c
>>
>> > ...
>>
>> > Each PWM/Tach instance has its own controller register and is not
>> dependent on others.
>
> Your email reply quoting style is very difficult to read.
>
>>
>>
>>
>> Hi Guenter,
>>
>>
>>
>> Did you receive a response to my previous email?
>>
>> I would like to inquire if you have any further concerns regarding the PWM
>> and Tach with 16 instances.
>
> But isn't like this in all PWMs in all SoCs?
>
Correct, pretty much every fan controller is implemented that way.
I don't understand the logic.
Guenter
next prev parent reply other threads:[~2023-07-14 9:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGUgbhCqOJaEPjS96o2au21uW4NhqFScm4Ayd8PzOQvqxQ94SQ@mail.gmail.com>
2023-07-14 7:13 ` [v6 2/4] dt-bindings: hwmon: Add ASPEED TACH Control documentation Krzysztof Kozlowski
2023-07-14 9:59 ` Guenter Roeck [this message]
2023-07-14 10:18 ` 蔡承達
2023-07-14 10:26 ` Guenter Roeck
2023-07-14 11:17 ` 蔡承達
2023-07-16 16:08 ` Krzysztof Kozlowski
2023-07-16 17:00 ` Guenter Roeck
2023-07-17 9:01 ` 蔡承達
2023-07-17 9:39 ` Krzysztof Kozlowski
2023-07-18 4:01 ` 蔡承達
2023-07-18 6:04 ` Krzysztof Kozlowski
2023-07-18 6:39 ` Thierry Reding
2023-07-18 6:54 ` Guenter Roeck
2023-07-18 7:14 ` Thierry Reding
2023-08-15 6:32 ` 蔡承達
2023-07-18 6:45 ` Guenter Roeck
2023-06-08 2:18 [v6 0/4] Support pwm/tach driver for aspeed ast26xx Billy Tsai
2023-06-08 2:18 ` [v6 2/4] dt-bindings: hwmon: Add ASPEED TACH Control documentation Billy Tsai
2023-06-08 4:58 ` Guenter Roeck
[not found] ` <SG2PR06MB3365E360F3FCDE639F3D2D1E8B50A@SG2PR06MB3365.apcprd06.prod.outlook.com>
2023-06-08 13:18 ` Guenter Roeck
2023-06-08 6:40 ` Krzysztof Kozlowski
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=0ba3767c-d481-6e2c-2d32-b79af0e1efd8@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@aj.id.au \
--cc=billy_tsai@aspeedtech.com \
--cc=billyking19920205@gmail.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=patrick@stwcx.xyz \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).