From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Andrej Picej <andrej.picej@norik.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Cc: Support Opensource <support.opensource@diasemi.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: RE: [RFC PATCH] watchdog: da9062: Correct the timeout values
Date: Mon, 6 Dec 2021 07:47:51 +0000 [thread overview]
Message-ID: <46136729bb564aa6b9f332fa584b2575@dh-electronics.com> (raw)
In-Reply-To: <a0b6a801-f911-3371-1067-479b66240bdc@norik.com>
From: Andrej Picej
Sent: Monday, December 6, 2021 8:29 AM
>>>> I measured the timeout values of my DA9061 chip. According to the
>>>> information in the data sheet the formula should be:
>>>>
>>>> timeout = 2.048 * 2^(regval - 1)
>>>>
>>>> But my measured values differ from that.
>>>> Accoring to my measured values the formula must be:
>>>>
>>>> timeout = 3.2 * 2^(regval - 1)
>>>>
>>>> Is there something wrong with my chip, or has anyone else noticed this as well?
>>>
>>> The driver assumes a static and well defined clock rate. Maybe that rate
>>> is different in your system (if that is possible) ?
>>>
>>> Guenter
>>
>> @Andrej
>> Do the values in the driver match what your chip does?
>>
>
> Just did a quick test. The values in the driver match what the chip
> does. I checked multiple timeouts 16, 32, 65 and 131 seconds. The
> timeout triggers quite accurately.
>
>> I have not changed anything. After power on, the chip behaves like this.
>> So I guess it either come from an OTP value or the wiring outside the chip.
>> Does anyone know what needs to be checked?
>
> Can't help you here, sorry.
>
Thanks anyway, so now I know it must be
problem with my DA9061 chip.
@Adam
Where can it come from?
Can you give we a hint what to check?
Thanks and best regards
Christoph
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Andrej Picej <andrej.picej@norik.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Cc: Support Opensource <support.opensource@diasemi.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: RE: [RFC PATCH] watchdog: da9062: Correct the timeout values
Date: Mon, 6 Dec 2021 07:47:51 +0000 [thread overview]
Message-ID: <46136729bb564aa6b9f332fa584b2575@dh-electronics.com> (raw)
In-Reply-To: <a0b6a801-f911-3371-1067-479b66240bdc@norik.com>
From: Andrej Picej
Sent: Monday, December 6, 2021 8:29 AM
>>>> I measured the timeout values of my DA9061 chip. According to the
>>>> information in the data sheet the formula should be:
>>>>
>>>> timeout = 2.048 * 2^(regval - 1)
>>>>
>>>> But my measured values differ from that.
>>>> Accoring to my measured values the formula must be:
>>>>
>>>> timeout = 3.2 * 2^(regval - 1)
>>>>
>>>> Is there something wrong with my chip, or has anyone else noticed this as well?
>>>
>>> The driver assumes a static and well defined clock rate. Maybe that rate
>>> is different in your system (if that is possible) ?
>>>
>>> Guenter
>>
>> @Andrej
>> Do the values in the driver match what your chip does?
>>
>
> Just did a quick test. The values in the driver match what the chip
> does. I checked multiple timeouts 16, 32, 65 and 131 seconds. The
> timeout triggers quite accurately.
>
>> I have not changed anything. After power on, the chip behaves like this.
>> So I guess it either come from an OTP value or the wiring outside the chip.
>> Does anyone know what needs to be checked?
>
> Can't help you here, sorry.
>
Thanks anyway, so now I know it must be
problem with my DA9061 chip.
@Adam
Where can it come from?
Can you give we a hint what to check?
Thanks and best regards
Christoph
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-06 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 16:35 [RFC PATCH] watchdog: da9062: Correct the timeout values Christoph Niedermaier
2021-12-03 16:35 ` Christoph Niedermaier
2021-12-03 16:52 ` Guenter Roeck
2021-12-03 16:52 ` Guenter Roeck
2021-12-03 17:31 ` Christoph Niedermaier
2021-12-06 7:29 ` Andrej Picej
2021-12-06 7:29 ` Andrej Picej
2021-12-06 7:47 ` Christoph Niedermaier [this message]
2021-12-06 7:47 ` Christoph Niedermaier
2021-12-06 16:37 ` Adam Thomson
2021-12-06 16:37 ` Adam Thomson
2021-12-07 15:17 ` Christoph Niedermaier
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=46136729bb564aa6b9f332fa584b2575@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=andrej.picej@norik.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=support.opensource@diasemi.com \
--cc=wim@linux-watchdog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.