linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	Tero Kristo <t-kristo@ti.com>, Ralf Baechle <ralf@linux-mips.org>,
	Paul Burton <paul.burton@mips.com>,
	James Hogan <jhogan@kernel.org>,
	linux-mips@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>,
	linux-pwm@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH] clk: Remove CLK_IS_BASIC clk flag
Date: Fri, 26 Apr 2019 17:24:58 +0200	[thread overview]
Message-ID: <20190426152458.GC19559@ulmo> (raw)
In-Reply-To: <20190425181447.60726-1-sboyd@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]

On Thu, Apr 25, 2019 at 11:14:47AM -0700, Stephen Boyd wrote:
> This flag was historically used to indicate that a clk is a "basic" type
> of clk like a mux, divider, gate, etc. This never turned out to be very
> useful though because it was hard to cleanly split "basic" clks from
> other clks in a system. This one flag was a way for type introspection
> and it just didn't scale. If anything, it was used by the TI clk driver
> to indicate that a clk_hw wasn't contained in the SoC specific clk
> structure. We can get rid of this define now that TI is finding those
> clks a different way.
> 
> Cc: Tero Kristo <t-kristo@ti.com>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: Paul Burton <paul.burton@mips.com>
> Cc: James Hogan <jhogan@kernel.org>
> Cc: <linux-mips@vger.kernel.org>
> Cc: Thierry Reding <thierry.reding@gmail.com>
> Cc: Kevin Hilman <khilman@baylibre.com>
> Cc: <linux-pwm@vger.kernel.org>
> Cc: <linux-amlogic@lists.infradead.org>
> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> ---
>  arch/mips/alchemy/common/clock.c     | 2 +-
>  drivers/clk/clk-composite.c          | 2 +-
>  drivers/clk/clk-divider.c            | 2 +-
>  drivers/clk/clk-fixed-factor.c       | 2 +-
>  drivers/clk/clk-fixed-rate.c         | 2 +-
>  drivers/clk/clk-fractional-divider.c | 2 +-
>  drivers/clk/clk-gate.c               | 2 +-
>  drivers/clk/clk-gpio.c               | 2 +-
>  drivers/clk/clk-mux.c                | 2 +-
>  drivers/clk/clk-pwm.c                | 2 +-
>  drivers/clk/clk.c                    | 1 -
>  drivers/clk/mmp/clk-gate.c           | 2 +-
>  drivers/pwm/pwm-meson.c              | 2 +-
>  include/linux/clk-provider.h         | 2 +-
>  14 files changed, 13 insertions(+), 14 deletions(-)

Acked-by: Thierry Reding <treding@nvidia.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-04-26 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 18:14 [PATCH] clk: Remove CLK_IS_BASIC clk flag Stephen Boyd
2019-04-26 15:24 ` Thierry Reding [this message]
2019-04-26 15:26 ` Thierry Reding
2019-04-26 17:59   ` 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=20190426152458.GC19559@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=jhogan@kernel.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=paul.burton@mips.com \
    --cc=ralf@linux-mips.org \
    --cc=sboyd@kernel.org \
    --cc=t-kristo@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).