linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: imx6q: clean up board specific CLKO setup
Date: Thu, 18 Jul 2013 15:31:06 +0800	[thread overview]
Message-ID: <1374132670-791-1-git-send-email-shawn.guo@linaro.org> (raw)

The CLKO is widely used by imx6q board designs to clock audio codec.
Currently, imx6q-sabrelite and imx6qdl-sabresd set up CLKO in board
specific hooks, while imx6qdl-wandboard handles that in U-Boot.
Since most audio codecs accept 24 MHz frequency, the series adds missing
CLKO pieces into clock driver, and initially sets up CLKO with OSC24M
(cko <-- cko2 <-- osc).  Then those board specific CLKO setup for audio
codec can be removed, while it improves the power efficiency@the same
time by saving the use of PLL.

Shawn

Shawn Guo (4):
  ARM: imx6q: add spdif gate clock
  ARM: imx6q: add cko2 clocks
  ARM: imx6q: add the missing cko output selection
  ARM: imx6q: remove board specific CLKO setup

 .../devicetree/bindings/clock/imx6q-clock.txt      |    5 ++
 arch/arm/boot/dts/imx6q-sabrelite.dts              |    2 +-
 arch/arm/boot/dts/imx6qdl-sabresd.dtsi             |    2 +-
 arch/arm/boot/dts/imx6qdl-wandboard.dtsi           |    2 +-
 arch/arm/mach-imx/clk-imx6q.c                      |   30 ++++++++-
 arch/arm/mach-imx/mach-imx6q.c                     |   69 --------------------
 6 files changed, 37 insertions(+), 73 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2013-07-18  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  7:31 Shawn Guo [this message]
2013-07-18  7:31 ` [PATCH 1/4] ARM: imx6q: add spdif gate clock Shawn Guo
2013-07-18  7:31 ` [PATCH 2/4] ARM: imx6q: add cko2 clocks Shawn Guo
2013-07-18  7:31 ` [PATCH 3/4] ARM: imx6q: add the missing cko output selection Shawn Guo
2013-07-18  7:31 ` [PATCH 4/4] ARM: imx6q: remove board specific CLKO setup Shawn Guo
2013-07-18  8:36   ` Sascha Hauer
2013-07-18 11:55     ` Shawn Guo

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=1374132670-791-1-git-send-email-shawn.guo@linaro.org \
    --to=shawn.guo@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).