mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "SZ Lin (林上智)" <sz.lin@moxa.com>
To: linux-kernel@vger.kernel.org
Cc: robh+dt@kernel.org, bcousson@baylibre.com, tony@atomide.com,
	mark.rutland@arm.com, linux-omap@vger.kernel.org,
	devicetree@vger.kernel.org, "SZ Lin (林上智)" <sz.lin@moxa.com>
Subject: [PATCH v2 0/3] Add support for Moxa UC-2100 series
Date: Fri, 28 Sep 2018 18:46:14 +0800	[thread overview]
Message-ID: <20180928104614.30601-1-sz.lin@moxa.com> (raw)

The UC-2100 series open computing platform is designed for industrial
embedded data acquisition and processing applications. In order to
fulfill various industrial applications, there're many boards with
different peripheral devices and wireless modules in this series.

The features of UC-2100 series are:
* eMMC
* SPI flash
* {1,2}x LAN (100/1000 Mbps in option)
* {1,2}x RS-232/422/485 ports, software-selectable
* EEPROM
* TPM 2.0
* Watchdog
* RTC
* User gpio-keys
* User LEDs
* User button
* GPS (option)
* 2x CANBus (option)
* Cellular module (option)
* Mini PCIe form factor with USB signal (option)
* MicroSD slot (option)

---
Changes from v1:
- Use property phy-handle instead of phy_id
- Separate DT binding docs and dts file
- Remove am335x-moxa-uc-2102.dts

SZ Lin (林上智) (3):
  ARM: dts: am335x: add common file for UC-2100 series
  dt-bindings: arm: omap: Add binding for Moxa UC-2101 open platform
  ARM: dts: am335x: add support for Moxa UC-2101 open platform

 .../devicetree/bindings/arm/omap/omap.txt     |   3 +
 arch/arm/boot/dts/Makefile                    |   1 +
 .../boot/dts/am335x-moxa-uc-2100-common.dtsi  | 249 ++++++++++++++++++
 arch/arm/boot/dts/am335x-moxa-uc-2101.dts     |  69 +++++
 4 files changed, 322 insertions(+)
 create mode 100644 arch/arm/boot/dts/am335x-moxa-uc-2100-common.dtsi
 create mode 100644 arch/arm/boot/dts/am335x-moxa-uc-2101.dts

-- 
2.19.0


                 reply	other threads:[~2018-09-28 10:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180928104614.30601-1-sz.lin@moxa.com \
    --to=sz.lin@moxa.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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

all inboxes | Powered by JetHome®