From: Rob Herring <robh@kernel.org>
To: Alex Helms <alexander.helms.jy@renesas.com>
Cc: sboyd@kernel.org, linux-clk@vger.kernel.org,
mturquette@baylibre.com, linux-kernel@vger.kernel.org,
michal.simek@xilinx.com, devicetree@vger.kernel.org,
robh+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: Renesas versaclock7 device tree bindings
Date: Mon, 16 May 2022 13:49:59 -0500 [thread overview]
Message-ID: <20220516184959.GA3069296-robh@kernel.org> (raw)
In-Reply-To: <20220503194201.25714-2-alexander.helms.jy@renesas.com>
On Tue, 03 May 2022 12:42:00 -0700, Alex Helms wrote:
> Renesas Versaclock7 is a family of configurable clock generator ICs
> with fractional and integer dividers. This driver has basic support
> for the RC21008A device, a clock synthesizer with a crystal input and
> 8 outputs. The supports changing the FOD and IOD rates, and each
> output can be gated.
>
> Signed-off-by: Alex Helms <alexander.helms.jy@renesas.com>
> ---
> .../bindings/clock/renesas,versaclock7.yaml | 64 +++++++++++++++++++
> MAINTAINERS | 5 ++
> 2 files changed, 69 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/renesas,versaclock7.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-05-16 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 19:41 [PATCH 0/2] Renesas Versaclock7 Bindings and Clock Driver Alex Helms
2022-05-03 19:42 ` [PATCH 1/2] dt-bindings: Renesas versaclock7 device tree bindings Alex Helms
2022-05-16 18:49 ` Rob Herring [this message]
2022-05-03 19:42 ` [PATCH 2/2] clk: Renesas versaclock7 ccf device driver Alex Helms
-- strict thread matches above, loose matches on Subject: below --
2022-09-12 18:36 [PATCH v2 0/2] Renesas Versaclock7 Bindings and Clock Driver Alex Helms
2022-09-12 18:36 ` [PATCH 1/2] dt-bindings: Renesas versaclock7 device tree bindings Alex Helms
2022-10-01 0:32 ` Stephen Boyd
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=20220516184959.GA3069296-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexander.helms.jy@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@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).