From: Kevin Hilman <khilman@kernel.org>
To: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: Add dts file for odroid XU3 board
Date: Wed, 03 Dec 2014 20:40:04 -0800 [thread overview]
Message-ID: <7hlhmoxc2j.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1417638971.21830.42.camel@collabora.co.uk> (Sjoerd Simons's message of "Wed, 03 Dec 2014 21:36:11 +0100")
Sjoerd Simons <sjoerd.simons@collabora.co.uk> writes:
> On Wed, 2014-12-03 at 11:53 -0800, Kevin Hilman wrote:
>> Sjoerd Simons <sjoerd.simons@collabora.co.uk> writes:
>> Tried this on top of linux-next (next-20141125 and next20141203) and
>> boots fine on my odroid-xu3.
>>
>> Thanks for doing this, I've been meaning to get a DTS upstream for this
>> platform myself. I also noticed that the imprecise aborts I've been
>> seeing when booting this board with the smdk5420 DTS are gone, so I
>> don't have to dig into those now either. Thanks! :)
>
> For completeness, the problem with running the smdk5420 DTS on the XU3
> is that the XU3 runs secure firmware while the SMD5420 doesn't.. Hence
> the imprecise aborts you were seeing.
OK, that's what I suspected but didn't take the time to verify. Thanks
for the update.
BTW, I'll have some DTS updates for the xu3 to enable the on-board
INA2xx current sensors for easy power measurements without external
instrumentation. Will send a patch for those soon.
Kevin
next prev parent reply other threads:[~2014-12-04 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 12:59 [PATCH] ARM: dts: Add dts file for odroid XU3 board Sjoerd Simons
2014-12-02 6:17 ` Heesub Shin
2014-12-02 8:32 ` Sjoerd Simons
2014-12-03 19:53 ` Kevin Hilman
2014-12-03 20:36 ` Sjoerd Simons
2014-12-04 4:40 ` Kevin Hilman [this message]
2014-12-03 20:24 ` Tyler Baker
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=7hlhmoxc2j.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.martinez@collabora.co.uk \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sjoerd.simons@collabora.co.uk \
/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).