From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: am335x-boneblack: move fixed regulator to board level
Date: Fri, 20 Sep 2013 11:21:54 -0500 [thread overview]
Message-ID: <20130920162154.GB18721@radagast> (raw)
In-Reply-To: <1379610764-758-1-git-send-email-nm@ti.com>
On Thu, Sep 19, 2013 at 12:12:44PM -0500, Nishanth Menon wrote:
> 3.3V fixed regulator does not belong to TPS node - as a result
> the fixed regulator is never probed and MMC is continually deferred due
> to lack of regulator.
>
> Move the fixed regulator to be at root of platform.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Tested-by: Felipe Balbi <balbi@ti.com>
I boot tested this on my BBB.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130920/d67cbab2/attachment-0001.sig>
next prev parent reply other threads:[~2013-09-20 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 17:12 [PATCH] ARM: dts: am335x-boneblack: move fixed regulator to board level Nishanth Menon
2013-09-20 16:21 ` Felipe Balbi [this message]
2013-09-27 14:37 ` Balaji T K
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=20130920162154.GB18721@radagast \
--to=balbi@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