linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
	Andrej Picej <andrej.picej@norik.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
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>
Subject: RE: [RFC PATCH] watchdog: da9062: Correct the timeout values [Klartext]
Date: Tue, 15 Feb 2022 09:16:10 +0000	[thread overview]
Message-ID: <DB9PR10MB46529728D2574AE35CB84D3680349@DB9PR10MB4652.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <3bb120e2fcb649f09cf0f8c881f442ff@dh-electronics.com>

On 14 February 2022 18:03, Christoph Niedermaier wrote:

> I come to the conclusion that under normal condition (room temperature) the
> timeout values could be improved, but due to the used internal ring oscillator
> on the DA9061 chip under extreme conditions like automotive (125 degrees) the
> values come close to the DA9062 timeout values, if an external oscillator
> is used. In order not to trigger too early in extreme situations, the values
> must be left as they are. But I told Dialog to add a note in the data sheet
> explaining the deviation when the internal oscillator is used (DA9061).
> 
> Thanks for helping me and best regards
> Christoph

Thanks for the update. I'll also push internally for the Datasheet update
so this is clearer in the future, to avoid any misunderstandings.

  reply	other threads:[~2022-02-15  9:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  9:11 [RFC PATCH] watchdog: da9062: Correct the timeout values [Klartext] Christoph Niedermaier
2021-12-13 13:58 ` Guenter Roeck
2021-12-13 16:16   ` Christoph Niedermaier
2021-12-13 22:44   ` Christoph Niedermaier
2022-02-14 18:02     ` Christoph Niedermaier
2022-02-15  9:16       ` Adam Thomson [this message]
2021-12-13 14:31 ` Andrej Picej
2021-12-13 21:47   ` Christoph Niedermaier
2021-12-13 14:53 ` Adam Thomson

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=DB9PR10MB46529728D2574AE35CB84D3680349@DB9PR10MB4652.EURPRD10.PROD.OUTLOOK.COM \
    --to=adam.thomson.opensource@diasemi.com \
    --cc=Support.Opensource@diasemi.com \
    --cc=andrej.picej@norik.com \
    --cc=cniedermaier@dh-electronics.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=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 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).