linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sergio.prado@e-labworks.com (Sergio Prado)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: imx6: Add dts for Embest MarS Board
Date: Wed, 13 Apr 2016 17:58:03 -0300	[thread overview]
Message-ID: <570EB2DB.20707@e-labworks.com> (raw)
In-Reply-To: <CAOMZO5D80VWGad7Lz+Crp8on5xLJzHDXL88FBh7x8d4Mc2XKww@mail.gmail.com>

Hi Fabio,

On 11-04-2016 22:04, Fabio Estevam wrote:
> Hi Sergio,
>
> On Mon, Apr 11, 2016 at 9:25 PM, Sergio Prado
> <sergio.prado@e-labworks.com> wrote:
>> Embest MarS Board [1] is a multi-core platform based on Freescale i.MX6
>> Cortex-A9 Dual Core, running up to 1GHz with 1 GB of RAM, 4GB of eMMC
>> and with a 4MB SPI flash.
>>
>> [1] http://www.embest-tech.com/shop/star/marsboard.html
>>
>> Signed-off-by: Sergio Prado <sergio.prado@e-labworks.com>
>
> Can't the Mars board re-use arch/arm/boot/dts/imx6dl-riotboard.dts ?
>

Although the boards are similar, there are a lot of differences:

Marsboard -> imx6dual, no sound, sst25vf016b spi flash, 1 external 
sd/mmc interface (sdhc2) and one eMMC (sdhc3), different PMUX config for 
no sdhc3, no pmic, i2c1, i2c2 and i2c3 externally available, no ssi 
interface.

Riotboard -> imx6solo, sound (sgtl5000), no spi flash, 2 external sd/mmc 
interface (sdhc2 and sdhc3) and one eMMC (sdhc4), pmic (pfuze100), i2c1, 
i2c2 and i2c4 externally available, ssi interface.

We could certainly create a dtsi file to be shared between them, but I 
do not know if it is worth the effort.

What do you think?

Best regards,

Sergio Prado

  reply	other threads:[~2016-04-13 20:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12  0:25 [PATCH v2] ARM: dts: imx6: Add dts for Embest MarS Board Sergio Prado
2016-04-12  1:04 ` Fabio Estevam
2016-04-13 20:58   ` Sergio Prado [this message]
2016-04-19 11:22     ` Fabio Estevam
2016-04-12 14:06 ` Vladimir Zapolskiy
2016-04-19 11:30 ` Fabio Estevam
2016-04-19 11:34 ` Fabio Estevam
2016-04-20 19:41   ` Sergio Prado

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=570EB2DB.20707@e-labworks.com \
    --to=sergio.prado@e-labworks.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).