linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: tegra: harmony: initialize the TPS65862 PMIC
Date: Wed, 9 Mar 2011 12:22:22 +0000	[thread overview]
Message-ID: <20110309122222.GG6923@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4D776A42.9030107@compulab.co.il>

On Wed, Mar 09, 2011 at 01:53:38PM +0200, Mike Rapoport wrote:

> As for me, I'd be fine with registering only the pex_clk supply and ldo0 to
> allow PCI-e on Harmony :)
> If Tegra folks are Ok with it, I'd drop the rest and we'll add more regulators
> and supplies together with drivers that use them.

Note that there's no issue with having no supplies set for a regulator
so no reason not to register the supplies themselves, it's just the
supply map that I was flagging.

  reply	other threads:[~2011-03-09 12:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 12:58 [PATCH 0/3] Harmony PCI-e and regulators Mike Rapoport
2011-03-08 12:58 ` [PATCH 1/3] ARM: tegra: harmony: update PCI-e initialization sequence Mike Rapoport
2011-03-08 12:58 ` [PATCH 2/3] ARM: tegra: harmony: initialize the TPS65862 PMIC Mike Rapoport
2011-03-08 13:15   ` Mark Brown
2011-03-09  7:41     ` Mike Rapoport
2011-03-09 10:15       ` Mark Brown
2011-03-09 11:53         ` Mike Rapoport
2011-03-09 12:22           ` Mark Brown [this message]
2011-03-09 13:19             ` Mike Rapoport
2011-03-09 13:15               ` Mark Brown
2011-03-09 13:23                 ` Mike Rapoport
2011-03-08 22:12   ` Marc Dietrich
2011-03-09  6:23     ` Mike Rapoport
2011-03-09 11:14       ` Marvin
2011-03-08 12:58 ` [PATCH 3/3] ARM: tegra: update defconfig Mike Rapoport
2011-03-08 18:06 ` [PATCH 0/3] Harmony PCI-e and regulators Olof Johansson

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=20110309122222.GG6923@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.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).