From: Tero Kristo <kristo@kernel.org>
To: Lokesh Vutla <lokeshvutla@ti.com>,
mturquette@baylibre.com, sboyd@kernel.org,
Rob Herring <robh+dt@kernel.org>
Cc: Device Tree Mailing List <devicetree@vger.kernel.org>,
ssantosh@kernel.org, Vignesh R <vigneshr@ti.com>,
linux-clk@vger.kernel.org,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v2 0/2] clk: keystone: Add support for AM64 specific ehrpwm-tbclk
Date: Thu, 3 Jun 2021 09:08:04 +0300 [thread overview]
Message-ID: <a33393b0-db88-ca2d-a51c-9f25880ff0e3@kernel.org> (raw)
In-Reply-To: <20210528045743.16537-1-lokeshvutla@ti.com>
On 28/05/2021 07:57, Lokesh Vutla wrote:
> This series adds support for AM64 specific ehrpwm Time-base submodule
> clock.
>
> Changes since v1:
> - Fixed register offsets and bits for clocks.
> - Update the compatible to ti,am64-epwm-tbclk, as high resolution is not
> supported in AM64.
>
> Lokesh Vutla (2):
> dt-bindings: clock: ehrpwm: Add support for AM64 specific compatible
> clk: keystone: syscon-clk: Add support for AM64 specific ehrpwm-tbclk
>
> .../bindings/clock/ti,am654-ehrpwm-tbclk.yaml | 4 +++-
> drivers/clk/keystone/syscon-clk.c | 17 +++++++++++++++++
> 2 files changed, 20 insertions(+), 1 deletion(-)
>
For the whole series:
Reviewed-by: Tero Kristo <kristo@kernel.org>
next prev parent reply other threads:[~2021-06-03 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 4:57 [PATCH v2 0/2] clk: keystone: Add support for AM64 specific ehrpwm-tbclk Lokesh Vutla
2021-05-28 4:57 ` [PATCH v2 1/2] dt-bindings: clock: ehrpwm: Add support for AM64 specific compatible Lokesh Vutla
2021-06-04 20:56 ` Rob Herring
2021-06-22 21:18 ` Stephen Boyd
2021-05-28 4:57 ` [PATCH v2 2/2] clk: keystone: syscon-clk: Add support for AM64 specific epwm-tbclk Lokesh Vutla
2021-06-22 21:18 ` Stephen Boyd
2021-06-03 6:08 ` Tero Kristo [this message]
2021-06-21 11:56 ` [PATCH v2 0/2] clk: keystone: Add support for AM64 specific ehrpwm-tbclk Lokesh Vutla
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=a33393b0-db88-ca2d-a51c-9f25880ff0e3@kernel.org \
--to=kristo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).