From: Joel Fernandes <joelf@ti.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
Kevin Hilman <khilman@linaro.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, bcousson@baylibre.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, 9 Sep 2013 13:27:49 -0500 [thread overview]
Message-ID: <522E1325.8050906@ti.com> (raw)
In-Reply-To: <BBAC0939-A4F9-4FEA-B137-0307D8787DC3@dominion.thruhere.net>
On 09/09/2013 10:51 AM, Koen Kooi wrote:
>
> Op 9 sep. 2013, om 17:23 heeft Kevin Hilman <khilman@linaro.org> het volgende geschreven:
>
>> 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?
>
> Yes, I blame it on being monday :)
The series you're posting will require rebasing on the current MMC DT series
that is being discussed last couple of weeks on the mailing list which were
waiting until now as DMA support was missing. Now that DMA support is pulled in,
it is safe to apply those patches so I will be reposting them shortly.
Please hold off any changes until those patches are posted. This will avoid
unnecessary conflicts.
Thanks,
-Joel
next prev parent reply other threads:[~2013-09-09 18:27 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
2013-09-09 15:51 ` Koen Kooi
2013-09-09 18:27 ` Joel Fernandes [this message]
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=522E1325.8050906@ti.com \
--to=joelf@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@linaro.org \
--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).