From: Rob Herring <robh@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Biju Das <biju.das@bp.renesas.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org,
Chris Paterson <Chris.Paterson2@renesas.com>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: watchdog: renesas,wdt: Add support for RZ/G2L
Date: Sun, 28 Nov 2021 18:38:13 -0600 [thread overview]
Message-ID: <YaQg9ezHdQQtB0P+@robh.at.kernel.org> (raw)
In-Reply-To: <20211122113554.15990-2-biju.das.jz@bp.renesas.com>
On Mon, 22 Nov 2021 11:35:53 +0000, Biju Das wrote:
> Describe the WDT hardware in the RZ/G2L series.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> V2->v3:
> * No change.
> V1->V2:
> * No Change
> RFC->V1:
> * Added clock-names and interrupt-names as required properties for RZ/G2L
> * Re-order clocknames with internal module clock first
> ---
> .../bindings/watchdog/renesas,wdt.yaml | 75 ++++++++++++++-----
> 1 file changed, 57 insertions(+), 18 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-11-29 0:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 11:35 [PATCH v3 0/2] Add WDT driver for RZ/G2L Biju Das
2021-11-22 11:35 ` [PATCH v3 1/2] dt-bindings: watchdog: renesas,wdt: Add support " Biju Das
2021-11-23 13:35 ` Geert Uytterhoeven
2021-11-29 0:38 ` Rob Herring [this message]
2021-11-29 15:33 ` Guenter Roeck
2021-11-22 11:35 ` [PATCH v3 2/2] watchdog: Add Watchdog Timer driver " Biju Das
2021-11-30 2:24 ` Guenter Roeck
2021-11-30 9:58 ` Biju Das
2021-11-30 10:10 ` Geert Uytterhoeven
2021-11-30 10:22 ` Biju Das
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=YaQg9ezHdQQtB0P+@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=wsa+renesas@sang-engineering.com \
/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