From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Andrej Picej <andrej.picej@norik.com>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.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>,
Guenter Roeck <linux@roeck-us.net>
Subject: RE: [RFC PATCH] watchdog: da9062: Correct the timeout values [Klartext]
Date: Mon, 13 Dec 2021 21:47:14 +0000 [thread overview]
Message-ID: <97b298dcf6614cfca5ece40284779b47@dh-electronics.com> (raw)
In-Reply-To: <1450af96-f279-c545-20a0-9361a070ca13@norik.com>
From: Andrej Picej
Sent: Monday, December 13, 2021 3:31 PM
[...]
>> @Andrej
>> I guess, you are using an external oscillator, aren't you?
>
> You are correct, we are using external oscillator (32,768KHz).
Thanks for the info.
Regards
Christoph
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Andrej Picej <andrej.picej@norik.com>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.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>,
Guenter Roeck <linux@roeck-us.net>
Subject: RE: [RFC PATCH] watchdog: da9062: Correct the timeout values [Klartext]
Date: Mon, 13 Dec 2021 21:47:14 +0000 [thread overview]
Message-ID: <97b298dcf6614cfca5ece40284779b47@dh-electronics.com> (raw)
In-Reply-To: <1450af96-f279-c545-20a0-9361a070ca13@norik.com>
From: Andrej Picej
Sent: Monday, December 13, 2021 3:31 PM
[...]
>> @Andrej
>> I guess, you are using an external oscillator, aren't you?
>
> You are correct, we are using external oscillator (32,768KHz).
Thanks for the info.
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-13 21:48 UTC|newest]
Thread overview: 17+ 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 13:58 ` Guenter Roeck
2021-12-13 16:16 ` Christoph Niedermaier
2021-12-13 16:16 ` Christoph Niedermaier
2021-12-13 22:44 ` Christoph Niedermaier
2021-12-13 22:44 ` Christoph Niedermaier
2022-02-14 18:02 ` Christoph Niedermaier
2022-02-14 18:02 ` Christoph Niedermaier
2022-02-15 9:16 ` Adam Thomson
2022-02-15 9:16 ` Adam Thomson
2021-12-13 14:31 ` Andrej Picej
2021-12-13 14:31 ` Andrej Picej
2021-12-13 21:47 ` Christoph Niedermaier [this message]
2021-12-13 21:47 ` Christoph Niedermaier
2021-12-13 14:53 ` Adam Thomson
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=97b298dcf6614cfca5ece40284779b47@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=Support.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=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.