From: Heiko Stuebner <heiko@sntech.de>
To: andi.shyti@gmail.com
Cc: Jeffy Chen <jeffy.chen@rock-chips.com>,
Xing Zheng <zhengxing@rock-chips.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Andi Shyti <andi@etezian.org>
Subject: Re: [PATCH 0/2] use the CLK_IS_CRITICAL flag for critical clocks
Date: Tue, 28 Jun 2016 17:11:40 +0200 [thread overview]
Message-ID: <2143021.IyFNGTj97L@phil> (raw)
In-Reply-To: <1467125137-25999-1-git-send-email-andi@etezian.org>
Hi Andi,
Am Dienstag, 28. Juni 2016, 17:45:35 schrieb andi.shyti@gmail.com:
> From: Andi Shyti <andi@etezian.org>
> this patchset is the first of a series and it aims to remove
> the handling of critical clock on the rockchip clock drivers.
I'm actually waiting on the second part of that to land.
The series introducing critical clocks also wanted to provide so called
hand-off clocks (clocks being critical until a driver takes possession of
them).
What are currently critical clocks in Rockchip drivers are essentially a mix
of those two types, and I was somehow hoping that the handoff type also
lands soonish so that we can limit ourselfs to one conversion step.
Heiko
> Patch 32b9b10961860860268961d9aad0c56a73018c37 has added a
> generic clock critical handling that can be used from the
> drivers.
>
> Because I'm not expert in the clock framework, I want to check if
> this is fine and, if so, I will fire the other patches.
>
> Thanks,
> Andi
>
> Andi Shyti (2):
> clk: clk-rk3*: set CLK_IS_CRITICAL flag to critical clocks
> clk: rockchip: remove unused rockchip_clk_protect_critical function
>
> drivers/clk/rockchip/clk-rk3036.c | 18 ++-----
> drivers/clk/rockchip/clk-rk3188.c | 25 +++-------
> drivers/clk/rockchip/clk-rk3228.c | 17 ++-----
> drivers/clk/rockchip/clk-rk3288.c | 21 +++-----
> drivers/clk/rockchip/clk-rk3368.c | 22 ++-------
> drivers/clk/rockchip/clk-rk3399.c | 101
> ++++++++++++++++---------------------- drivers/clk/rockchip/clk.c
> | 14 ------
> drivers/clk/rockchip/clk.h | 1 -
> 8 files changed, 69 insertions(+), 150 deletions(-)
>
> --
> 2.8.1
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] use the CLK_IS_CRITICAL flag for critical clocks
Date: Tue, 28 Jun 2016 17:11:40 +0200 [thread overview]
Message-ID: <2143021.IyFNGTj97L@phil> (raw)
In-Reply-To: <1467125137-25999-1-git-send-email-andi@etezian.org>
Hi Andi,
Am Dienstag, 28. Juni 2016, 17:45:35 schrieb andi.shyti at gmail.com:
> From: Andi Shyti <andi@etezian.org>
> this patchset is the first of a series and it aims to remove
> the handling of critical clock on the rockchip clock drivers.
I'm actually waiting on the second part of that to land.
The series introducing critical clocks also wanted to provide so called
hand-off clocks (clocks being critical until a driver takes possession of
them).
What are currently critical clocks in Rockchip drivers are essentially a mix
of those two types, and I was somehow hoping that the handoff type also
lands soonish so that we can limit ourselfs to one conversion step.
Heiko
> Patch 32b9b10961860860268961d9aad0c56a73018c37 has added a
> generic clock critical handling that can be used from the
> drivers.
>
> Because I'm not expert in the clock framework, I want to check if
> this is fine and, if so, I will fire the other patches.
>
> Thanks,
> Andi
>
> Andi Shyti (2):
> clk: clk-rk3*: set CLK_IS_CRITICAL flag to critical clocks
> clk: rockchip: remove unused rockchip_clk_protect_critical function
>
> drivers/clk/rockchip/clk-rk3036.c | 18 ++-----
> drivers/clk/rockchip/clk-rk3188.c | 25 +++-------
> drivers/clk/rockchip/clk-rk3228.c | 17 ++-----
> drivers/clk/rockchip/clk-rk3288.c | 21 +++-----
> drivers/clk/rockchip/clk-rk3368.c | 22 ++-------
> drivers/clk/rockchip/clk-rk3399.c | 101
> ++++++++++++++++---------------------- drivers/clk/rockchip/clk.c
> | 14 ------
> drivers/clk/rockchip/clk.h | 1 -
> 8 files changed, 69 insertions(+), 150 deletions(-)
>
> --
> 2.8.1
next prev parent reply other threads:[~2016-06-28 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 14:45 [PATCH 0/2] use the CLK_IS_CRITICAL flag for critical clocks andi.shyti
2016-06-28 14:45 ` andi.shyti at gmail.com
2016-06-28 14:45 ` [PATCH 1/2] clk: clk-rk3*: set CLK_IS_CRITICAL flag to " andi.shyti
2016-06-28 14:45 ` andi.shyti at gmail.com
2016-06-28 15:17 ` Heiko Stuebner
2016-06-28 15:17 ` Heiko Stuebner
2016-06-28 16:09 ` Andi Shyti
2016-06-28 16:09 ` Andi Shyti
2016-06-28 16:32 ` Heiko Stuebner
2016-06-28 16:32 ` Heiko Stuebner
2016-06-28 14:45 ` [PATCH 2/2] clk: rockchip: remove unused rockchip_clk_protect_critical function andi.shyti
2016-06-28 14:45 ` andi.shyti at gmail.com
2016-06-28 15:11 ` Heiko Stuebner [this message]
2016-06-28 15:11 ` [PATCH 0/2] use the CLK_IS_CRITICAL flag for critical clocks Heiko Stuebner
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=2143021.IyFNGTj97L@phil \
--to=heiko@sntech.de \
--cc=andi.shyti@gmail.com \
--cc=andi@etezian.org \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=zhengxing@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.