From: Rob Herring <robh@kernel.org>
To: Samuel Holland <samuel@sholland.org>
Cc: linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Icenowy Zheng <icenowy@aosc.io>,
linux-watchdog@vger.kernel.org,
Maxime Ripard <mripard@kernel.org>,
devicetree@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/3] dt-bindings: watchdog: sunxi: Add compatibles for R329
Date: Fri, 3 Sep 2021 11:07:46 -0500 [thread overview]
Message-ID: <YTJIUocojn3h4R25@robh.at.kernel.org> (raw)
In-Reply-To: <20210902225750.29313-2-samuel@sholland.org>
On Thu, 02 Sep 2021 17:57:48 -0500, Samuel Holland wrote:
> On existing SoCs, the watchdog has a single clock input: HOSC (OSC24M)
> divided by 750. However, starting with R329, LOSC (OSC32k) is added as
> an alternative clock source, with a bit to switch between them.
>
> Since 24 MHz / 750 == 32 kHz, not 32.768 kHz, the hardware adjusts the
> cycle counts to keep the timeouts independent of the clock source. This
> keeps the programming interface backward-compatible.
>
> Furthermore, the R329 has two watchdogs: one for use by the ARM CPUs
> at 0x20000a0, and a second one for use by the DSPs at 0x7020400. The
> first of these adds two more new registers, to allow software to
> immediately assert the SoC reset signal. Add an additional "-reset"
> suffix to signify the presence of this feature.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
> Changes v2 to v3:
> - Add else case
> - Add additional allwinner,sun50i-r329-wdt-reset compatible
> Changes v1 to v2:
> - Switch clock-names from enum to const
> - Add descriptions to "clocks" items
>
> .../watchdog/allwinner,sun4i-a10-wdt.yaml | 42 ++++++++++++++++++-
> 1 file changed, 41 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Samuel Holland <samuel@sholland.org>
Cc: linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Icenowy Zheng <icenowy@aosc.io>,
linux-watchdog@vger.kernel.org,
Maxime Ripard <mripard@kernel.org>,
devicetree@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/3] dt-bindings: watchdog: sunxi: Add compatibles for R329
Date: Fri, 3 Sep 2021 11:07:46 -0500 [thread overview]
Message-ID: <YTJIUocojn3h4R25@robh.at.kernel.org> (raw)
In-Reply-To: <20210902225750.29313-2-samuel@sholland.org>
On Thu, 02 Sep 2021 17:57:48 -0500, Samuel Holland wrote:
> On existing SoCs, the watchdog has a single clock input: HOSC (OSC24M)
> divided by 750. However, starting with R329, LOSC (OSC32k) is added as
> an alternative clock source, with a bit to switch between them.
>
> Since 24 MHz / 750 == 32 kHz, not 32.768 kHz, the hardware adjusts the
> cycle counts to keep the timeouts independent of the clock source. This
> keeps the programming interface backward-compatible.
>
> Furthermore, the R329 has two watchdogs: one for use by the ARM CPUs
> at 0x20000a0, and a second one for use by the DSPs at 0x7020400. The
> first of these adds two more new registers, to allow software to
> immediately assert the SoC reset signal. Add an additional "-reset"
> suffix to signify the presence of this feature.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
> Changes v2 to v3:
> - Add else case
> - Add additional allwinner,sun50i-r329-wdt-reset compatible
> Changes v1 to v2:
> - Switch clock-names from enum to const
> - Add descriptions to "clocks" items
>
> .../watchdog/allwinner,sun4i-a10-wdt.yaml | 42 ++++++++++++++++++-
> 1 file changed, 41 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
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-09-03 16:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 22:57 [PATCH v3 0/3] Allwinner R329 and D1 watchdog support Samuel Holland
2021-09-02 22:57 ` Samuel Holland
2021-09-02 22:57 ` [PATCH v3 1/3] dt-bindings: watchdog: sunxi: Add compatibles for R329 Samuel Holland
2021-09-02 22:57 ` Samuel Holland
2021-09-03 9:30 ` Maxime Ripard
2021-09-03 9:30 ` Maxime Ripard
2021-09-03 16:07 ` Rob Herring [this message]
2021-09-03 16:07 ` Rob Herring
2021-09-04 15:10 ` Guenter Roeck
2021-09-04 15:10 ` Guenter Roeck
2021-09-02 22:57 ` [PATCH v3 2/3] dt-bindings: watchdog: sunxi: Add compatibles for D1 Samuel Holland
2021-09-02 22:57 ` Samuel Holland
2021-09-03 9:30 ` Maxime Ripard
2021-09-03 9:30 ` Maxime Ripard
2021-09-04 15:11 ` Guenter Roeck
2021-09-04 15:11 ` Guenter Roeck
2021-09-07 19:09 ` Rob Herring
2021-09-07 19:09 ` Rob Herring
2021-09-02 22:57 ` [PATCH v3 3/3] watchdog: sunxi_wdt: Add support " Samuel Holland
2021-09-02 22:57 ` Samuel Holland
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=YTJIUocojn3h4R25@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.org \
--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.