linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hvaibhav@ti.com (Vaibhav Hiremath)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP AM33XX: clock data: Enable clkout2 output on SoC pad
Date: Tue, 7 May 2013 15:09:32 +0530	[thread overview]
Message-ID: <1367919574-21353-1-git-send-email-hvaibhav@ti.com> (raw)

'clkout2' comes out on the device pad and is being used by various
external on-board peripherals like, Audio codecs, Wilink and stuff.
So enable the clkout2 by default during init sequence itself
along with right pinmux configuration clkout2 output.

Also, add the missing entry of "clkout2_ck" to the AM33xx clock table.

As far as enabling of clkout2 during init is concerned,
we can argue that it can be handled using DT property and enable
the clock only when specified; but not until OMAP clock-tree
migration to DT.

Vaibhav Hiremath (2):
  ARM: OMAP AM33XX: clock data: Enable clkout2 as part of init
  ARM: dts: AM33XX: Set pinmux for clkout2 pad used for clock output

 arch/arm/boot/dts/am335x-bone.dts     |    8 +++++++-
 arch/arm/boot/dts/am335x-evm.dts      |    8 +++++++-
 arch/arm/boot/dts/am335x-evmsk.dts    |    8 +++++++-
 arch/arm/mach-omap2/cclock33xx_data.c |    2 ++
 4 files changed, 23 insertions(+), 3 deletions(-)

             reply	other threads:[~2013-05-07  9:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07  9:39 Vaibhav Hiremath [this message]
2013-05-07  9:39 ` [PATCH 1/2] ARM: OMAP AM33XX: clock data: Enable clkout2 as part of init Vaibhav Hiremath
2013-05-20  2:50   ` Paul Walmsley
2013-05-20  5:30     ` Hiremath, Vaibhav
2013-05-07  9:39 ` [PATCH 2/2] ARM: dts: AM33XX: Set pinmux for clkout2 pad used for clock output Vaibhav Hiremath
2013-05-20  2:51   ` Paul Walmsley
2013-05-20  5:30     ` Hiremath, Vaibhav
2013-05-17 11:07 ` [PATCH 0/2] ARM: OMAP AM33XX: clock data: Enable clkout2 output on SoC pad Hiremath, Vaibhav
2013-05-20  2:47   ` Paul Walmsley
2013-05-20  5:31     ` Hiremath, Vaibhav
2013-05-27 12:27     ` Benoit Cousson
2013-05-29 19:06       ` Paul Walmsley
2013-06-03 12:35         ` Benoit Cousson

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=1367919574-21353-1-git-send-email-hvaibhav@ti.com \
    --to=hvaibhav@ti.com \
    --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).