From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: <linux-omap@vger.kernel.org>, <rogerq@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Nishanth Menon <nm@ti.com>
Subject: [PATCH 0/2] ARM: dts: dra7-evm: fixes for mux and VTT control
Date: Thu, 4 Sep 2014 08:23:26 -0500 [thread overview]
Message-ID: <1409837008-32144-1-git-send-email-nm@ti.com> (raw)
Hi,
The following series was inspired in part by http://marc.info/?l=linux-omap&m=140974309205295&w=2
causing me to try and do an audit of pinctrl configurations on the platform.
Further, failures on latest board updates in the automated farm also
caused identification of a fix which was yet to be send to upstream
from product kernel. Slightly unrelated patches in this series.
So here they are..
based on v3.17-rc1:
before-dra7xx-evm: Boot FAIL: http://paste.ubuntu.org.cn/1477597
(fails can be at different times though.. random crashes without VTT is usual)..
after-dra7xx-evm: Boot PASS: http://paste.ubuntu.org.cn/1477596
Lokesh Vutla (1):
ARM: dts: dra7-evm: Add vtt regulator support
Nishanth Menon (1):
ARM: dts: dra7-evm: Fix spi1 mux documentation
arch/arm/boot/dts/dra7-evm.dts | 39 ++++++++++++++++++++++++++++++++-------
1 file changed, 32 insertions(+), 7 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-09-04 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 13:23 Nishanth Menon [this message]
2014-09-04 13:23 ` [PATCH 1/2] ARM: dts: dra7-evm: Fix spi1 mux documentation Nishanth Menon
2014-09-04 13:33 ` Nishanth Menon
2014-09-04 13:23 ` [PATCH 2/2] ARM: dts: dra7-evm: Add vtt regulator support Nishanth Menon
2014-09-04 19:49 ` [PATCH 0/2] ARM: dts: dra7-evm: fixes for mux and VTT control Tony Lindgren
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=1409837008-32144-1-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=rogerq@ti.com \
--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
all inboxes | Powered by JetHome®