From: Jerome Brunet <jbrunet@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-clk@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] clk: meson: g12a: add support for the SPICC SCLK Source clocks
Date: Wed, 19 Feb 2020 18:57:27 +0100 [thread overview]
Message-ID: <1jy2sywjco.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20200219084928.28707-1-narmstrong@baylibre.com>
On Wed 19 Feb 2020 at 09:49, Neil Armstrong <narmstrong@baylibre.com> wrote:
> Like on the AXG SoCs, the SPICC controllers can make use of an external clock
> source instead of it's internal divider over xtal to provide a better SCLK
> clock frequency.
>
> This serie adds the new clock IDs and the associated clocks in the g12a driver.
>
> Neil Armstrong (2):
> dt-bindings: clk: g12a-clkc: add SPICC SCLK Source clock IDs
> clk: meson: g12a: add support for the SPICC SCLK Source clocks
>
> drivers/clk/meson/g12a.c | 129 ++++++++++++++++++++++++++
> drivers/clk/meson/g12a.h | 6 +-
> include/dt-bindings/clock/g12a-clkc.h | 2 +
> 3 files changed, 136 insertions(+), 1 deletion(-)
Applied. Thx
prev parent reply other threads:[~2020-02-19 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 8:49 [PATCH 0/2] clk: meson: g12a: add support for the SPICC SCLK Source clocks Neil Armstrong
2020-02-19 8:49 ` [PATCH 1/2] dt-bindings: clk: g12a-clkc: add SPICC SCLK Source clock IDs Neil Armstrong
2020-02-26 15:29 ` Rob Herring
2020-02-19 8:49 ` [PATCH 2/2] clk: meson: g12a: add support for the SPICC SCLK Source clocks Neil Armstrong
2020-02-19 17:57 ` Jerome Brunet [this message]
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=1jy2sywjco.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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).