From: Arseny Demidov <a.demidov@yadro.com>
To: Guenter Roeck <linux@roeck-us.net>, Arseny Demidov <arsdemal@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] hwmon : (mr75203) fix macro typo
Date: Wed, 15 Dec 2021 12:36:32 +0000 [thread overview]
Message-ID: <c1d036c0cfa14fbb9c289f792780f003@yadro.com> (raw)
In-Reply-To: <06d7c6ee-2db5-f250-50f7-9a47e33a35b5@roeck-us.net>
Yes, I have access to the datasheet and caught an error on simulation IP-block.
The datasheet says that register "Expressed in units of IP clk cycles."
Typical power-up delays for Temperature Sensor are 256 cycles i. e. 0x100
-----Original Message-----
From: Guenter Roeck <groeck7@gmail.com> On Behalf Of Guenter Roeck
Sent: Wednesday, December 15, 2021 3:31 PM
To: Arseny Demidov <arsdemal@gmail.com>
Cc: Arseny Demidov <a.demidov@yadro.com>; Jean Delvare <jdelvare@suse.com>; linux-hwmon@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon : (mr75203) fix macro typo
On 12/15/21 3:59 AM, Guenter Roeck wrote:
> On 12/15/21 3:30 AM, Arseny Demidov wrote:
>> In the file mr75203.c we have a macro named POWER_DELAY_CYCLE_256,
>> the correct value should be 0x100
>>
>
> How do you know that ? Do you have access to the datasheet, or is it
> just an assumption based on the name of the define ?
>
Also, how do you know that the value is wrong, not the name of the define ?
Guenter
> Guenter
>
>> Signed-off-by: Arseny Demidov <a.demidov@yadro.com>
>> ---
>> drivers/hwmon/mr75203.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/hwmon/mr75203.c b/drivers/hwmon/mr75203.c index
>> 868243dba1ee..1ba1e3145969 100644
>> --- a/drivers/hwmon/mr75203.c
>> +++ b/drivers/hwmon/mr75203.c
>> @@ -93,7 +93,7 @@
>> #define VM_CH_REQ BIT(21)
>> #define IP_TMR 0x05
>> -#define POWER_DELAY_CYCLE_256 0x80
>> +#define POWER_DELAY_CYCLE_256 0x100
>> #define POWER_DELAY_CYCLE_64 0x40
>> #define PVT_POLL_DELAY_US 20
>>
>
next prev parent reply other threads:[~2021-12-15 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 11:30 [PATCH] hwmon : (mr75203) fix macro typo Arseny Demidov
2021-12-15 11:59 ` Guenter Roeck
2021-12-15 12:31 ` Guenter Roeck
2021-12-15 12:36 ` Arseny Demidov [this message]
2021-12-15 16:27 ` Guenter Roeck
2021-12-16 14:26 ` Andy Shevchenko
2021-12-16 14:40 ` Guenter Roeck
2021-12-16 14:54 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2021-12-16 8:33 Arseny Demidov
2021-12-16 14:19 ` Andy Shevchenko
2021-12-17 16:05 ` Guenter Roeck
2021-12-17 16:45 ` Andy Shevchenko
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=c1d036c0cfa14fbb9c289f792780f003@yadro.com \
--to=a.demidov@yadro.com \
--cc=arsdemal@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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