From: Jerome Brunet <jbrunet@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, narmstrong@baylibre.com,
linux-clk@vger.kernel.org
Cc: devicetree@vger.kernel.org, khilman@baylibre.com,
carlo@caione.org, sboyd@codeaurora.org, mturquette@baylibre.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] clk: meson-gxbb: un-export the CPU clock
Date: Mon, 15 May 2017 17:54:50 +0200 [thread overview]
Message-ID: <1494863690.13948.0.camel@baylibre.com> (raw)
In-Reply-To: <20170504181920.21880-2-martin.blumenstingl@googlemail.com>
On Thu, 2017-05-04 at 20:19 +0200, Martin Blumenstingl wrote:
> The CPU clock defined in the Meson GX clock driver is actually a
> left-over from the Meson8b clock controller. Un-export the clock so we
> can remove it from the driver.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> drivers/clk/meson/gxbb.h | 2 +-
> include/dt-bindings/clock/gxbb-clkc.h | 1 -
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/clk/meson/gxbb.h b/drivers/clk/meson/gxbb.h
> index 3e5f375af7b6..c15bbce8c585 100644
> --- a/drivers/clk/meson/gxbb.h
> +++ b/drivers/clk/meson/gxbb.h
> @@ -171,7 +171,7 @@
> * to be exposed to client nodes in DT: include/dt-bindings/clock/gxbb-clkc.h
> */
> #define CLKID_SYS_PLL 0
> -/* CLKID_CPUCLK */
> +#define CLKID_CPUCLK 1
> /* CLKID_HDMI_PLL */
> #define CLKID_FIXED_PLL 3
> /* CLKID_FCLK_DIV2 */
> diff --git a/include/dt-bindings/clock/gxbb-clkc.h b/include/dt-
> bindings/clock/gxbb-clkc.h
> index 3190e30b9398..46ff81fbc02e 100644
> --- a/include/dt-bindings/clock/gxbb-clkc.h
> +++ b/include/dt-bindings/clock/gxbb-clkc.h
> @@ -5,7 +5,6 @@
> #ifndef __GXBB_CLKC_H
> #define __GXBB_CLKC_H
>
> -#define CLKID_CPUCLK 1
> #define CLKID_HDMI_PLL 2
> #define CLKID_FCLK_DIV2 4
> #define CLKID_FCLK_DIV3 5
Applied. Thanks
Jerome
next prev parent reply other threads:[~2017-05-15 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 12:55 [PATCH 0/1] remove the "cpu_clk" from the GXBB/GXL/GXM driver Martin Blumenstingl
2017-04-01 12:55 ` [PATCH 1/1] clk: meson: gxbb: remove the "cpu_clk" from the GXBB and GXL driver Martin Blumenstingl
[not found] ` <20170401125519.7339-2-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-04-02 15:57 ` Jerome Brunet
2017-05-04 18:19 ` [PATCH v2 0/2] remove the "cpu_clk" from the GXBB/GXL/GXM driver Martin Blumenstingl
2017-05-04 18:19 ` [PATCH v2 1/2] clk: meson-gxbb: un-export the CPU clock Martin Blumenstingl
2017-05-15 15:54 ` Jerome Brunet [this message]
2017-05-04 18:19 ` [PATCH v2 2/2] clk: meson: gxbb: remove the "cpu_clk" from the GXBB and GXL driver Martin Blumenstingl
[not found] ` <20170504181920.21880-3-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-05-15 15:56 ` Jerome Brunet
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=1494863690.13948.0.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=sboyd@codeaurora.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).