From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: sbc-t54: add support for sbc-t54 with cm-t54
Date: Fri, 18 Apr 2014 10:08:18 -0700 [thread overview]
Message-ID: <20140418170818.GI5354@atomide.com> (raw)
In-Reply-To: <1396962531-27729-2-git-send-email-lifshitz@compulab.co.il>
* Dmitry Lifshitz <lifshitz@compulab.co.il> [140408 06:14]:
> Add support for CM-T54 CoM and SBC-T54 board:
>
> http://compulab.co.il/products/computer-on-modules/cm-t54/
> http://compulab.co.il/products/sbcs/sbc-t54/
>
> SBC-T54 is a single board computer based on OMAP5432 CPU.
> It is implemented with a CM-T54 CoM providing most of the functions,
> and SB-T54 carrier board providing connectors and several additional
> functions.
>
> Added basic support for:
>
> * PMIC
> * LED
> * MMC/SD
> * eMMC
> * USB
> * I2C1/4
> * SB-T54 and CM-T54 EEPROMs
> * RTC
You probably want to use the OMAP5_CORE_IOPAD and OMAP5_WKUP_IOPAD
macros for new boards as then you can easily check them against
the TRM based on the physical offset of the register.
Regards,
Tony
next prev parent reply other threads:[~2014-04-18 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 13:08 [PATCH 0/2] ARM: dts: sbc-t54: add support for sbc-t54 with cm-t54 Dmitry Lifshitz
2014-04-08 13:08 ` [PATCH 1/2] " Dmitry Lifshitz
2014-04-18 17:08 ` Tony Lindgren [this message]
2014-04-08 13:08 ` [PATCH 2/2] ARM: dts: cm-t54: add WiFi/BT support Dmitry Lifshitz
2014-04-28 11:41 ` [PATCH v2 0/2] ARM: dts: sbc-t54: add support for sbc-t54 with cm-t54 Dmitry Lifshitz
2014-04-28 11:41 ` [PATCH v2 1/2] " Dmitry Lifshitz
2014-04-28 11:41 ` [PATCH v2 2/2] ARM: dts: cm-t54: add WiFi/BT support Dmitry Lifshitz
2014-05-05 22:31 ` [PATCH v2 0/2] ARM: dts: sbc-t54: add support for sbc-t54 with cm-t54 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=20140418170818.GI5354@atomide.com \
--to=tony@atomide.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).