Linux clock framework development
 help / color / mirror / Atom feed
From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: <linux-tegra@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	<jonathanh@nvidia.com>, <thierry.reding@gmail.com>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>
Subject: [PATCH v2 0/2] Correct clk_out_mux parents
Date: Thu, 19 Jul 2018 17:22:53 +0300	[thread overview]
Message-ID: <1532010175-28364-1-git-send-email-pdeschrijver@nvidia.com> (raw)

This series corrects the parents for the clk_out_mux clocks. Patch 1 does
some cleanup work to keep checkpatch.pl and the compiler happy. Patch 2
does the actual work.

v2:

Fixed const compiler warnings


Peter De Schrijver (2):
  clk: tegra: Fix const for clk_out parents
  clk: tegra: Correct clk_out_mux parents

 drivers/clk/tegra/clk-id.h               |  5 +++++
 drivers/clk/tegra/clk-tegra-fixed.c      | 16 ++++++++++++++
 drivers/clk/tegra/clk-tegra-pmc.c        | 36 ++++++++++++++++++++++++++++----
 drivers/clk/tegra/clk-tegra210.c         | 14 ++++++-------
 include/dt-bindings/clock/tegra210-car.h |  9 ++++++--
 5 files changed, 67 insertions(+), 13 deletions(-)

-- 
1.9.1


             reply	other threads:[~2018-07-19 15:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 14:22 Peter De Schrijver [this message]
2018-07-19 14:22 ` [PATCH v2 1/2] clk: tegra: Fix const for clk_out parents Peter De Schrijver
2018-07-25 22:44   ` Stephen Boyd
2018-07-26  8:19     ` Peter De Schrijver
2018-07-26  8:26       ` Jon Hunter
2018-07-19 14:22 ` [PATCH v2 2/2] clk: tegra: Correct clk_out_mux parents Peter De Schrijver
2018-07-19 15:06   ` Jon Hunter
2018-07-25 22:44     ` Stephen Boyd
2018-07-26  8:19       ` Peter De Schrijver
2018-07-26 16:07         ` 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=1532010175-28364-1-git-send-email-pdeschrijver@nvidia.com \
    --to=pdeschrijver@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.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