From: Rob Herring <robh@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: mturquette@baylibre.com, sboyd@kernel.org,
linux-rockchip@lists.infradead.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, mark.rutland@arm.com
Subject: Re: [PATCH] clk: rockchip: remove deprecated gate-clk code and dt-binding
Date: Tue, 22 May 2018 17:33:13 -0500 [thread overview]
Message-ID: <20180522223313.GA12580@rob-hp-laptop> (raw)
In-Reply-To: <20180512143038.30447-1-heiko@sntech.de>
On Sat, May 12, 2018 at 04:30:38PM +0200, Heiko Stuebner wrote:
> Initially we tried modeling clocks via the devicetree before switching
> to clocks declared in the clock drivers and only exporting specific
> ids to the devicetree.
>
> As the old code was in the kernel for 1-2 releases when the new mode
> of operation was added we kept it for backwards compatibility.
>
> That deprecation notice is in the binding since july 2014, so nearly
> 4 years now and I think it's time to drop the old cruft.
>
> Especially as at the time using the mainline kernel on Rockchip devices
> was not really possible, except for experiments on the really old socs of
> the rk3066 + rk3188 line, so there shouldn't be any devicetrees still
> around that rely on that code.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> .../devicetree/bindings/clock/rockchip.txt | 77 ---------------
> drivers/clk/rockchip/Makefile | 1 -
> drivers/clk/rockchip/clk-rockchip.c | 98 -------------------
> 3 files changed, 176 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/rockchip.txt
> delete mode 100644 drivers/clk/rockchip/clk-rockchip.c
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-05-22 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 14:30 [PATCH] clk: rockchip: remove deprecated gate-clk code and dt-binding Heiko Stuebner
2018-05-15 16:57 ` Stephen Boyd
2018-05-22 22:33 ` Rob Herring [this message]
2018-05-23 11:20 ` Heiko Stübner
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=20180522223313.GA12580@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--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