From: Rob Herring <robh@kernel.org>
To: Alex Helms <alexander.helms.jy@renesas.com>
Cc: robh+dt@kernel.org, geert+renesas@glider.be,
mturquette@baylibre.com, linux-renesas-soc@vger.kernel.org,
david.cater.jc@renesas.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sboyd@kernel.org,
michal.simek@xilinx.com, linux-clk@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: Add binding for Renesas 8T49N241
Date: Mon, 19 Jul 2021 16:48:04 -0600 [thread overview]
Message-ID: <20210719224804.GA2768983@robh.at.kernel.org> (raw)
In-Reply-To: <20210719182001.1573-2-alexander.helms.jy@renesas.com>
On Mon, 19 Jul 2021 11:20:00 -0700, Alex Helms wrote:
> Renesas 8T49N241 has 4 outputs, 1 integral and 3 fractional dividers.
> The 8T49N241 accepts up to two differential or single-ended input clocks
> and a fundamental-mode crystal input. The internal PLL can lock to either
> of the input reference clocks or to the crystal to behave as a frequency
> synthesizer.
>
> Signed-off-by: Alex Helms <alexander.helms.jy@renesas.com>
> ---
> .../bindings/clock/renesas,8t49n241.yaml | 190 ++++++++++++++++++
> MAINTAINERS | 6 +
> 2 files changed, 196 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/renesas,8t49n241.yaml
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
next prev parent reply other threads:[~2021-07-20 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 18:19 [PATCH v5 0/2] Renesas 8T49N241 device driver Alex Helms
2021-07-19 18:20 ` [PATCH v5 1/2] dt-bindings: Add binding for Renesas 8T49N241 Alex Helms
2021-07-19 22:48 ` Rob Herring [this message]
2021-07-20 16:58 ` Alex Helms
2021-07-22 14:19 ` Rob Herring
2021-07-19 18:20 ` [PATCH v5 2/2] clk: Add ccf driver " Alex Helms
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=20210719224804.GA2768983@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexander.helms.jy@renesas.com \
--cc=david.cater.jc@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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).