public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: mturquette@baylibre.com, sboyd@codeaurora.org
Cc: linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	sjoerd.simons@collabora.co.uk, wxt@rock-chips.com,
	Heiko Stuebner <heiko@sntech.de>
Subject: [PATCH v2 0/5] clk: rockchip: fix handling of fractional dividers
Date: Tue, 22 Dec 2015 22:27:57 +0100	[thread overview]
Message-ID: <1450819682-4932-1-git-send-email-heiko@sntech.de> (raw)

Essentially unchanged from the first iteration from back in august, just
including additional patches depending on that and fixing fractional
dividers on the rk3036 and spdif parent settings.

In v1, Stephen seemed essentially ok with it but Mike put forward his wish
to use his planned approach for connected clocks for handling this.

While that in itself will be very interesting also for handling Rockchip's
armclk generically, we're now in the situation that everything related
to audio output relies on working fractional dividers to produce the
needed clock frequencies, making audio-output essentially non-working on
all Rockchip socs in mainline at the moment.

So I'm somewhat hoping for some sort of intermediate solution here :-)


changes in v2:
- rebase original 3 patches onto 4.4
- add the 2 new patches from other series, that need that change

Heiko Stuebner (3):
  clk: add flag for clocks that need to be enabled on rate changes
  clk: rockchip: handle mux dependency of fractional dividers
  clk: rockchip: include downstream muxes into fractional dividers

Sjoerd Simons (1):
  clk: rockchip: Allow the RK3288 SPDIF clocks to change their parent

Xing Zheng (1):
  clk: rockchip: rk3036: include downstream muxes into fractional
    dividers

 drivers/clk/clk.c                 |  18 +++++
 drivers/clk/rockchip/clk-rk3036.c |  34 +++++-----
 drivers/clk/rockchip/clk-rk3188.c |  80 +++++++++++-----------
 drivers/clk/rockchip/clk-rk3288.c |  70 +++++++++----------
 drivers/clk/rockchip/clk.c        | 137 ++++++++++++++++++++++++++++++++++----
 drivers/clk/rockchip/clk.h        |  19 ++++++
 include/linux/clk-provider.h      |   1 +
 7 files changed, 254 insertions(+), 105 deletions(-)

-- 
2.6.4

             reply	other threads:[~2015-12-22 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 21:27 Heiko Stuebner [this message]
2015-12-22 21:27 ` [PATCH v2 1/5] clk: add flag for clocks that need to be enabled on rate changes Heiko Stuebner
2015-12-22 21:27 ` [PATCH v2 2/5] clk: rockchip: handle mux dependency of fractional dividers Heiko Stuebner
2015-12-22 21:28 ` [PATCH v2 3/5] clk: rockchip: include downstream muxes into " Heiko Stuebner
2015-12-22 21:28 ` [PATCH v2 4/5] clk: rockchip: rk3036: " Heiko Stuebner
2015-12-22 21:28 ` [PATCH v2 5/5] clk: rockchip: Allow the RK3288 SPDIF clocks to change their parent Heiko Stuebner
2015-12-24  0:11 ` [PATCH v2 0/5] clk: rockchip: fix handling of fractional dividers Michael Turquette

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=1450819682-4932-1-git-send-email-heiko@sntech.de \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=sjoerd.simons@collabora.co.uk \
    --cc=wxt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox