From: Guenter Roeck <linux@roeck-us.net>
To: Lei YU <mine260309@gmail.com>, Jean Delvare <jdelvare@suse.com>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
linux-hwmon@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (aspeed-pwm-tacho) Use 24MHz clock
Date: Tue, 8 May 2018 06:51:52 -0700 [thread overview]
Message-ID: <8a801894-4293-d2e8-4673-3d9ff5c2a5bb@roeck-us.net> (raw)
In-Reply-To: <1525772367-20627-1-git-send-email-mine260309@gmail.com>
On 05/08/2018 02:39 AM, Lei YU wrote:
> The clock source for aspeed pwm is set to 24MHz, so use the hard-coded
> clock frequency instead of the one in device tree.
>
> Otherwise, in case of the clock specified in device tree is not 24MHz,
> the fan speed will be incorrect.
>
> Signed-off-by: Lei YU <mine260309@gmail.com>
> ---
> drivers/hwmon/aspeed-pwm-tacho.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/hwmon/aspeed-pwm-tacho.c b/drivers/hwmon/aspeed-pwm-tacho.c
> index 693a3d5..e83b8df 100644
> --- a/drivers/hwmon/aspeed-pwm-tacho.c
> +++ b/drivers/hwmon/aspeed-pwm-tacho.c
> @@ -922,7 +922,6 @@ static int aspeed_pwm_tacho_probe(struct platform_device *pdev)
> void __iomem *regs;
> struct resource *res;
> struct device *hwmon;
> - struct clk *clk;
> int ret;
>
> np = dev->of_node;
> @@ -956,12 +955,10 @@ static int aspeed_pwm_tacho_probe(struct platform_device *pdev)
> regmap_write(priv->regmap, ASPEED_PTCR_TACH_SOURCE, 0);
> regmap_write(priv->regmap, ASPEED_PTCR_TACH_SOURCE_EXT, 0);
>
> - clk = devm_clk_get(dev, NULL);
> - if (IS_ERR(clk))
> - return -ENODEV;
> - priv->clk_freq = clk_get_rate(clk);
> aspeed_set_clock_enable(priv->regmap, true);
> + // The clock source is set to 24MHz
No mixed C/C++ comments in hwmon drivers.
> aspeed_set_clock_source(priv->regmap, 0);
> + priv->clk_freq = 24000000;
>
Are you saying that clk_get_rate() is wrong ? Anyway, if the DT is bad, it should be fixed.
I am not a friend of hacking drivers to fix up bad DTs, and much less so without explanation.
Plus, how do we know that the next chip supported by the driver doesn't have a 32MHz clock ?
Really, please fix the DT.
Guenter
> aspeed_create_type(priv);
>
>
next prev parent reply other threads:[~2018-05-08 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 9:39 Lei YU
2018-05-08 13:51 ` Guenter Roeck [this message]
2018-05-09 3:18 ` Lei YU
2018-05-09 3:43 ` Guenter Roeck
2018-05-09 3:50 ` Lei YU
2018-05-09 4:03 ` Benjamin Herrenschmidt
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=8a801894-4293-d2e8-4673-3d9ff5c2a5bb@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@aj.id.au \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mine260309@gmail.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®