From: grygorii.strashko@ti.com (Grygorii Strashko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: dts: am335x: Add initial support for ICEv2 board
Date: Wed, 23 Mar 2016 11:46:20 +0200 [thread overview]
Message-ID: <56F265EC.5050208@ti.com> (raw)
In-Reply-To: <1458704054-18152-2-git-send-email-lokeshvutla@ti.com>
On 03/23/2016 05:34 AM, Lokesh Vutla wrote:
> TI's Industrial Communication Engine EVM is a low cost hardware mainly
> developed for industrial communication type applications using serial
> or Ethernet based interfaces. This platform features TI's AM3359 with
> 800MHz single core Cortex-A8 processor, 256MB DDR3, 64MB SPI flash,
> 8MB NOR Flash, mmc, usb, can, dual Ethernet ports.
>
> For more information, look at HW user guide[1], Data manual[2].
>
> Just add basic support for the moment.
>
> [1] http://processors.wiki.ti.com/index.php/AM335x_Industrial_Communication_Engine_EVM_Rev2_1_HW_User_Guide
> [2] http://www.ti.com/lit/ds/symlink/am3359.pdf
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
> ---
> Changes since v1:
> - Add separate nodes for gpio leds and tpic2810 leds.
>
> .../devicetree/bindings/arm/omap/omap.txt | 3 +
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/am335x-icev2.dts | 306 +++++++++++++++++++++
> 3 files changed, 310 insertions(+)
> create mode 100644 arch/arm/boot/dts/am335x-icev2.dts
>
[...]
--
regards,
-grygorii
next prev parent reply other threads:[~2016-03-23 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 3:34 [PATCH v2 0/2] ARM: am335x: Add support for ICEv2 board Lokesh Vutla
2016-03-23 3:34 ` [PATCH v2 1/2] ARM: dts: am335x: Add initial " Lokesh Vutla
2016-03-23 9:46 ` Grygorii Strashko [this message]
2016-04-12 21:10 ` Tony Lindgren
2016-03-23 3:34 ` [PATCH v2 2/2] ARM: omap2plus_defconfig: Enable GPIO_TPIC2810 Lokesh Vutla
2016-04-13 21:41 ` 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=56F265EC.5050208@ti.com \
--to=grygorii.strashko@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).