linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/9] ARM: dts: support I2SE Duckbill devices
Date: Mon, 23 Jan 2017 18:05:04 +0100	[thread overview]
Message-ID: <2d2cf6f5-f264-7744-a5ec-35c47d58e39f@i2se.com> (raw)
In-Reply-To: <1485123764-14754-1-git-send-email-mhei@heimpold.de>

Am 22.01.2017 um 23:22 schrieb Michael Heimpold:
> This series updates/adds Device Tree support for I2SE's Duckbill
> device family.
>
> The Duckbill devices are small, pen-drive sized boards based on
> NXP's i.MX28 SoC. While the initial variants (Duckbill series) were
> equipped with a micro SD card slot only, the latest generation
> (Duckbill 2 series) have an additional internal eMMC onboard.
>
> Both device generations consists of four "family members":
>
> - Duckbill/Duckbill 2: generic board, intended to be used as
>   baseboard for custom designs and/or as development board
>
> - Duckbill EnOcean/Duckbill 2 EnOcean: come with an EnOcean
>   daugther board equipped with the popular TCM310 module
>
> - Duckbill 485/Duckbill 2 485: as the name implies, these
>   devices are intended to be used as Ethernet - RS485 converters
>
> - Duckbill SPI/Duckbill 2 SPI: not sold separately, but used
>   in I2SE's development kits for Green PHY HomePlug Powerline
>   communication
>
> Because the Duckbill series is EOL, this patch series only adds
> support for the latest Duckbill 2 series devices. However,
> support for the generic Duckbill board was already mainline,
> so update it to match vendor tree DT.

Acked-by: Stefan Wahren <stefan.wahren@i2se.com>

for patches 1,2,3,5

  parent reply	other threads:[~2017-01-23 17:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 22:22 [PATCH v2 0/9] ARM: dts: support I2SE Duckbill devices Michael Heimpold
2017-01-22 22:22 ` [PATCH v2 1/9] ARM: dts: imx28: add alternative pinmuxing for mmc2 Michael Heimpold
2017-01-22 22:22 ` [PATCH v2 2/9] ARM: dts: imx28: rename mmc2_sck_cfg to prepare for an alternative muxing setup Michael Heimpold
2017-01-22 22:22 ` [PATCH v2 3/9] ARM: dts: imx28: add alternative muxing for mmc2_sck_cfg Michael Heimpold
2017-01-22 22:22 ` [PATCH v2 4/9] ARM: dts: imx28-duckbill: enable spi, i2c and uart pins Michael Heimpold
2017-01-23 17:00   ` Stefan Wahren
2017-01-24 13:00     ` Shawn Guo
2017-01-22 22:22 ` [PATCH v2 5/9] ARM: dts: add support for I2SE Duckbill 2 boards Michael Heimpold
2017-01-22 22:22 ` [PATCH v2 6/9] ARM: dts: add support for I2SE Duckbill 2 485 Michael Heimpold
2017-01-23 17:10   ` Stefan Wahren
2017-01-22 22:22 ` [PATCH v2 7/9] ARM: dts: add support for I2SE Duckbill 2 EnOcean Michael Heimpold
2017-01-22 22:22 ` [PATCH v2 8/9] ARM: dts: add support for I2SE Duckbill 2 SPI Michael Heimpold
2017-01-23 17:16   ` Stefan Wahren
2017-01-22 22:22 ` [PATCH v2 9/9] Documentation: DT: add entries for I2SE boards Michael Heimpold
2017-01-23 17:20   ` Stefan Wahren
2017-01-23 17:05 ` Stefan Wahren [this message]
2017-01-23 18:18 ` [PATCH v2 0/9] ARM: dts: support I2SE Duckbill devices Fabio Estevam
2017-01-24  6:44   ` Michael Heimpold

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=2d2cf6f5-f264-7744-a5ec-35c47d58e39f@i2se.com \
    --to=stefan.wahren@i2se.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).