linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] clk fixes for v5.0-rc4
Date: Thu, 31 Jan 2019 23:10:37 -0800	[thread overview]
Message-ID: <20190201071037.215136-1-sboyd@kernel.org> (raw)

The following changes since commit b488517b28a47d16b228ce8dcf07f5cb8e5b3dc5:

  clk: socfpga: stratix10: fix naming convention for the fixed-clocks (2019-01-15 12:58:38 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus

for you to fetch changes up to 9ff1a3b4912528f853048ccd9757ba6a2cc75557:

  clk: qcom: gcc: Use active only source for CPUSS clocks (2019-01-24 11:41:48 -0800)

----------------------------------------------------------------
Mostly driver fixes, but there's a core framework fix in here too.

 - Revert the commits that introduce clk management for the SP
   clk on MMP2 SoCs (used for OLPC). Turns out it wasn't a good
   idea and there isn't any need to manage this clk, it just causes
   more headaches.

 - A performance regression that went unnoticed for many years where
   we would traverse the entire clk tree looking for a clk by name
   when we already have the pointer to said clk that we're looking
   for

 - A parent linkage fix for the qcom SDM845 clk driver

 - An i.MX clk driver rate miscalculation fix where order of operations
   were messed up

 - One error handling fix from the static checkers

----------------------------------------------------------------
Abel Vesa (1):
      clk: imx: Fix fractional clock set rate computation

Dan Carpenter (1):
      clk: ti: Fix error handling in ti_clk_parse_divider_data()

Derek Basehore (1):
      clk: Remove global clk traversal on fetch parent index

Lubomir Rintel (3):
      Revert "Input: olpc_apsp - enable the SP clock"
      Revert "clk: mmp2: add SP clock"
      Revert "dt-bindings: marvell,mmp2: Add clock id for the SP clock"

Taniya Das (1):
      clk: qcom: gcc: Use active only source for CPUSS clocks

 Documentation/devicetree/bindings/serio/olpc,ap-sp.txt |  4 ----
 drivers/clk/clk.c                                      | 14 ++++++++++++--
 drivers/clk/imx/clk-frac-pll.c                         |  5 +++--
 drivers/clk/mmp/clk-of-mmp2.c                          |  4 ----
 drivers/clk/qcom/gcc-sdm845.c                          | 14 ++++++++++----
 drivers/clk/ti/divider.c                               | 11 ++++++++++-
 drivers/input/serio/olpc_apsp.c                        | 14 --------------
 include/dt-bindings/clock/marvell,mmp2.h               |  1 -
 8 files changed, 35 insertions(+), 32 deletions(-)

-- 
Sent by a computer through tubes

             reply	other threads:[~2019-02-01  7:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01  7:10 Stephen Boyd [this message]
2019-02-01  7:25 ` [GIT PULL] clk fixes for v5.0-rc4 pr-tracker-bot

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=20190201071037.215136-1-sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=torvalds@linux-foundation.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).