devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: "Tony Lindgren" <tony@atomide.com>,
	"Benoît Cousson" <bcousson@baylibre.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org, Nishanth Menon <nm@ti.com>
Subject: [PATCH 0/2] ARM: dts: am57xx-beagle-x15: Updates for production X15
Date: Thu, 9 Apr 2015 17:33:15 -0500	[thread overview]
Message-ID: <1428618797-17190-1-git-send-email-nm@ti.com> (raw)

Hi,

BeagleBoard-X15 has had a few critical changes that impact
functionality. All previous BeagleBoard-X15s should now have been
updated or replaced with changes. If there are any further untracked
boards in the wild, TI will replace those platforms with updated ones
all-cost inclusive.

Obviously, we also need to add vbus-detect-gpio to enable complete
client functionality.

Further, these are not exactly 4.0-rc material anyways, but would be
nice to get into 4.1-rcs if possible - all our boards'd be broken in
upstream now till we merge these.

Bootlog after these fixes:
http://pastebin.ubuntu.com/10786281/

These patches are based off next-20150409

Nishanth Menon (2):
  ARM: dts: am57xx-beagle-x15: Switch UART mux pins
  ARM: dts: am57xx-beagle-x15: Switch GPIO fan number

 arch/arm/boot/dts/am57xx-beagle-x15.dts |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Regards,
Nishanth Menon
-- 
1.7.9.5

             reply	other threads:[~2015-04-09 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 22:33 Nishanth Menon [this message]
     [not found] ` <1428618797-17190-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2015-04-09 22:33   ` [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Switch UART mux pins Nishanth Menon
2015-04-09 22:56     ` Nishanth Menon
2015-05-04 16:24       ` Tony Lindgren
2015-04-09 22:33 ` [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Switch GPIO fan number Nishanth Menon

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=1428618797-17190-1-git-send-email-nm@ti.com \
    --to=nm@ti.com \
    --cc=bcousson@baylibre.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=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).