From: detheridge@ti.com (Darren Etheridge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] arm: dts: add support for AM437x StarterKit
Date: Tue, 24 Jun 2014 21:07:50 -0500 [thread overview]
Message-ID: <53AA2EF6.6070604@ti.com> (raw)
In-Reply-To: <1403547659-24558-3-git-send-email-balbi@ti.com>
On 06/23/2014 01:20 PM, Felipe Balbi wrote:
> Add support for TI's AM437x StarterKit Evaluation
> Module.
>
> Cc: Josh Elliot <jelliott@ti.com>
> Cc: Darren Etheridge <detheridge@ti.com>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
Tested-by: Darren Etheridge <detheridge@ti.com>
I tested with omap2plus_defconfig + additionally enabling OMAPDSS and
Backlight in .config. Working great for me with ethernet, sdcard, lcd
panel and backlight all functional.
dmesg log attached - generated by kernel built from the repo/branch
Felipe pointed to in the cover letter for this series and obviously
running on an AM437x StarterKit EVM.
Darren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg-am437x-sk.log
Type: text/x-log
Size: 21088 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140624/05b3e521/attachment-0001.bin>
next prev parent reply other threads:[~2014-06-25 2:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 18:20 [PATCH v3 0/2] arm: dts: add support for am437x sk Felipe Balbi
2014-06-23 18:20 ` [PATCH v3 1/2] arm: dts: am4372: let boards access all nodes through phandles Felipe Balbi
2014-06-24 18:39 ` Cooper Jr., Franklin
2014-06-24 20:51 ` Tom Rini
2014-06-24 21:11 ` Rob Herring
2014-06-25 1:40 ` Felipe Balbi
2014-06-25 11:14 ` Mark Rutland
2014-06-23 18:20 ` [PATCH v3 2/2] arm: dts: add support for AM437x StarterKit Felipe Balbi
2014-06-24 18:36 ` Cooper Jr., Franklin
2014-06-24 20:51 ` Tom Rini
2014-06-25 2:07 ` Darren Etheridge [this message]
2014-06-30 16:45 ` [PATCH v3 0/2] arm: dts: add support for am437x sk Felipe Balbi
2014-07-01 12:50 ` 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=53AA2EF6.6070604@ti.com \
--to=detheridge@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).