From: Billy Tsai <billy_tsai@aspeedtech.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [v2 3/3] hwmon: Add Aspeed ast2600 TACH support
Date: Wed, 2 Nov 2022 06:54:43 +0000 [thread overview]
Message-ID: <271C521D-8F20-4C86-B3DA-9C0AD74242D4@aspeedtech.com> (raw)
In-Reply-To: <20221101131456.GA1310110@roeck-us.net>
Hi Guenter,
On 2022/11/1, 9:15 PM, "Guenter Roeck" <groeck7 at gmail.com on behalf of linux@roeck-us.net> wrote:
On Tue, Nov 01, 2022 at 05:51:56PM +0800, Billy Tsai wrote:
> > +
> > + /* Restart the Tach channel to guarantee the value is fresh */
> > + aspeed_tach_ch_enable(priv, fan_tach_ch, false);
> > + aspeed_tach_ch_enable(priv, fan_tach_ch, true);
> Is that really needed ? Doesn't the controller measure values continuously ?
Yes, the controller will measure values continuously by hardware. I will remove it.
If the user want to get the fresh value, it should be done by the application layer
(e.g. read two times).
> > +
> > + if (ret) {
> > + /* return 0 if we didn't get an answer because of timeout*/
> > + if (ret == -ETIMEDOUT)
> > + return 0;
> > + else
> > + return ret;
> else after return is unnecessary, and why would a timeout be be ignored ?
When the user sets the correct fan information (i.e., min_rpm, max_rpm), the read
poll timeout will only occur if the tach pin does not get any signal (i.e. rpm=0).
> > + }
> > +
> > + raw_data = val & TACH_ASPEED_VALUE_MASK;
> > + /*
> > + * We need the mode to determine if the raw_data is double (from
> > + * counting both edges).
> > + */
> > + if (priv->tach_channel[fan_tach_ch].tach_edge == BOTH_EDGES)
> > + raw_data <<= 1;
> > +
> > + tach_div = raw_data * (priv->tach_channel[fan_tach_ch].divisor) *
> > + (priv->tach_channel[fan_tach_ch].pulse_pr);
> > +
> > + clk_source = clk_get_rate(priv->clk);
> > + dev_dbg(priv->dev, "clk %ld, raw_data %d , tach_div %d\n", clk_source,
> > + raw_data, tach_div);
> > +
> > + if (tach_div == 0)
> > + return -EDOM;
> If the fan is off or not connected, would that return an error ?
> If so, that would be inappropriate; it should return a speed
> of 0 in that case.
It will be handled by the regmap_read_poll_timeout.
Thanks
Best Regards,
Billy Tsai
next prev parent reply other threads:[~2022-11-02 6:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 9:51 [v2 0/3] upport pwm/tach driver for aspeed ast26xx Billy Tsai
2022-11-01 9:51 ` [v2 1/3] dt-bindings: Add bindings for aspeed pwm-tach Billy Tsai
2022-11-01 18:40 ` Rob Herring
2022-11-02 3:21 ` Billy Tsai
2022-11-02 18:19 ` Rob Herring
2022-11-03 7:39 ` Billy Tsai
2022-11-14 8:26 ` Billy Tsai
2022-11-01 9:51 ` [v2 2/3] pwm: Add Aspeed ast2600 PWM support Billy Tsai
2022-11-01 10:03 ` Christophe JAILLET
2022-11-01 9:51 ` [v2 3/3] hwmon: Add Aspeed ast2600 TACH support Billy Tsai
2022-11-01 10:16 ` Christophe JAILLET
2022-11-01 13:14 ` Guenter Roeck
2022-11-02 6:54 ` Billy Tsai [this message]
2022-11-02 17:01 ` Guenter Roeck
2022-11-03 3:52 ` Billy Tsai
2022-11-03 4:30 ` Guenter Roeck
2022-11-03 5:40 ` Billy Tsai
2022-11-03 14:30 ` Guenter Roeck
2022-11-08 7:17 ` Billy Tsai
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=271C521D-8F20-4C86-B3DA-9C0AD74242D4@aspeedtech.com \
--to=billy_tsai@aspeedtech.com \
--cc=linux-aspeed@lists.ozlabs.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