All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <jhovold@gmail.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, Johan Hovold <jhovold@gmail.com>
Subject: [PATCH 0/2] mfd: tps65910: add support for enabling external 32-kHz oscillator
Date: Thu, 28 Jun 2012 12:20:20 +0200	[thread overview]
Message-ID: <1340878822-28444-1-git-send-email-jhovold@gmail.com> (raw)

These patches (against v3.5-rc4) add support for enabling the external 32-kHz
oscillator input in tps6591x devices. Depending on boot-mode, the internal
RC-oscillator may be used by default and the external crystal-oscillator input
must be enabled by clearing a flag in the device-control register.

These patches are needed in order to get an accurate system clock on boards
such as the Craneboard.

Thanks,
Johan

Johan Hovold (2):
  mfd: tps65910: add support for enabling external 32-kHz oscillator
  mfd: tps65910: add device-tree entry to enable external 32-kHz
    oscillator

 Documentation/devicetree/bindings/mfd/tps65910.txt |    4 ++-
 drivers/mfd/tps65910.c                             |   24 +++++++++++++++++++-
 include/linux/mfd/tps65910.h                       |    1 +
 3 files changed, 27 insertions(+), 2 deletions(-)

-- 
1.7.8.6


             reply	other threads:[~2012-06-28 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 10:20 Johan Hovold [this message]
2012-06-28 10:20 ` [PATCH 1/2] mfd: tps65910: add support for enabling external 32-kHz oscillator Johan Hovold
2012-06-28 10:20 ` [PATCH 2/2] mfd: tps65910: add device-tree entry to enable " Johan Hovold
2012-07-05 15:23 ` [PATCH 0/2] mfd: tps65910: add support for enabling " Samuel Ortiz
2012-07-05 15:23   ` Samuel Ortiz
2012-07-11 13:44   ` [PATCH] mfd: add tps65910 32-kHz-crystal-input init Johan Hovold
2012-07-16 13:43     ` Samuel Ortiz
2012-07-16 13:43       ` Samuel Ortiz

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=1340878822-28444-1-git-send-email-jhovold@gmail.com \
    --to=jhovold@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=sameo@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.