From: Kevin Hilman <khilman@linaro.org>
To: Koen Kooi <koen@dominion.thruhere.net>, bcousson@baylibre.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux@arm.linux.org.uk, pawel.moll@arm.com,
swarren@wwwdotorg.org, tony@atomide.com,
ijc+devicetree@hellion.org.uk, linux-kernel@vger.kernel.org,
rob.herring@calxeda.com, olof@lixom.net,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP2+: am335x-bone*: add DT for BeagleBone Black
Date: Mon, 09 Sep 2013 08:23:50 -0700 [thread overview]
Message-ID: <87zjrm81dl.fsf@linaro.org> (raw)
In-Reply-To: <1378736961-21005-1-git-send-email-koen@dominion.thruhere.net> (Koen Kooi's message of "Mon, 9 Sep 2013 16:29:21 +0200")
Koen Kooi <koen@dominion.thruhere.net> writes:
> The BeagleBone Black is basically a regular BeagleBone with eMMC and HDMI added,
> so create a common dtsi both can use.
>
> IMPORTANT: booting the existing am335x-bone.dts will blow up the HDMI transceiver
> after a dozen boots with an uSD card inserted because LDO will be at 3.3V instead
> of 1.8.
>
> MMC support for AM335x still isn't in, so only the LDO change has been added.
>
> Cc: stable@vger.kernel.org
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> Tested-by: Tom Rini <trini@ti.com>
> Tested-by: Matt Porter <matt.porter@linaro.org>
I guess the subject should've included v5? Also, if this is to be
stable material, it will likely need rework since I don't think it will
apply cleanly to older trees due to DT churn.
Anyways, for this patch...
Acked-by: Kevin Hilman <khilman@linaro.org>
Even though I've probably already fried my HDMI transciever due to using
the original DTS a lot more than a dozen times. (and to TI: yes, I'd
accept a new BB black as a sympathy gift.) ;)
Also, I tested this on both BBW and BBW:
Tested-by: Kevin Hilman <khilman@linaro.org>
Benoit, assuming this looks good to you, can you queue this for v3.12-rc
please? It applies to Linus' HEAD today (which has most of arm-soc
merged), so it should apply cleanly on top of all your stuff.
Kevin
next prev parent reply other threads:[~2013-09-09 15:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 14:29 [PATCH] ARM: OMAP2+: am335x-bone*: add DT for BeagleBone Black Koen Kooi
2013-09-09 15:23 ` Kevin Hilman [this message]
2013-09-09 15:51 ` Koen Kooi
2013-09-09 18:27 ` Joel Fernandes
2013-09-09 18:43 ` Koen Kooi
2013-09-09 18:51 ` Joel Fernandes
2013-09-09 19:50 ` Joel Fernandes
2013-09-09 20:00 ` Koen Kooi
2013-09-09 20:12 ` Joel Fernandes
2013-09-09 23:42 ` Joel Fernandes
2013-09-10 5:45 ` Koen Kooi
2013-09-10 5:53 ` Fernandes, Joel
-- strict thread matches above, loose matches on Subject: below --
2013-09-06 6:33 Koen Kooi
2013-09-06 6:57 ` George Cherian
2013-09-06 7:10 ` Koen Kooi
2013-09-06 7:49 ` George Cherian
2013-09-06 8:51 ` Koen Kooi
2013-09-06 12:51 ` Koen Kooi
2013-09-09 14:50 ` Kevin Hilman
2013-09-09 14:54 ` Kevin Hilman
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=87zjrm81dl.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=koen@dominion.thruhere.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.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 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).