public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] ARM: dts: support I2SE Duckbill device
Date: Wed, 26 Oct 2016 21:55:50 +0800	[thread overview]
Message-ID: <20161026135550.GQ30578@tiger> (raw)
In-Reply-To: <2694949.M3JJFNG6Xz@kerker>

On Mon, Oct 24, 2016 at 09:45:56PM +0200, Michael Heimpold wrote:
> Actually it would even be 11 files for 8 boards, thats right.
> There is no mechanism (no EEPROM, GPIO...) to automatically probe for the 
> device variants, and the "variant-forming daugther boards" are
> not switchable like the expansion boards e.g. for Raspberry Pi.
> Another point is, that this would really require to use U-Boot to apply
> the overlay (or another DT capable bootloader with this functionality).
> For booting very fast, the good old Freescale bootlets are still
> an option, which could not handle the overlays - at least at the moment...
> However, it still an option to have a second look...
> 
> To reduce the number of files, I see the following other approaches:
> - don't use the three "common" files which are included: -3 files (8 total)
> - don't mainline Duckbill EnOcean, Duckbill 485 and Duckbill SPI:
>   they are EOL, only Duckbill 2 variants are still sold;
>   however, since Duckbill (without 2) is/was already mainlined, we
>   should keep this, leaving 4 new variants + 1 old variant: -3 files (5 total)
> - only mainline Duckbill 2 (generic board) and maintain all other variants
>   in a private Github repo (this is what we are doing now): -3 files (2 total)
> 
> So, I'll discuss this again internally. Do you have any preference?

I'm fine with the second one.

Shawn

      reply	other threads:[~2016-10-26 13:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22 19:22 [PATCH 0/7] ARM: dts: support I2SE Duckbill device Michael Heimpold
2016-10-22 19:22 ` [PATCH 1/7] ARM: dts: imx28: add alternative pinmuxing for mmc2 Michael Heimpold
2016-10-22 19:22 ` [PATCH 2/7] ARM: dts: imx28: rename mmc2_sck_cfg to prepare for an alternative muxing setup Michael Heimpold
2016-10-22 19:22 ` [PATCH 3/7] ARM: dts: imx28: add alternative muxing for mmc2_sck_cfg Michael Heimpold
2016-10-22 19:22 ` [PATCH 4/7] ARM: dts: add I2SE Duckbill common definitions Michael Heimpold
2016-10-26 13:53   ` Shawn Guo
2016-10-22 19:22 ` [PATCH 5/7] ARM: dts: duckbill: simplify DT and use " Michael Heimpold
2016-10-22 19:22 ` [PATCH 6/7] ARM: dts: add support for remaining members of Duckbill series Michael Heimpold
2016-10-22 19:22 ` [PATCH 7/7] ARM: dts: add support for Duckbill 2 series devices Michael Heimpold
2016-10-24 13:12 ` [PATCH 0/7] ARM: dts: support I2SE Duckbill device Shawn Guo
2016-10-24 19:45   ` Michael Heimpold
2016-10-26 13:55     ` Shawn Guo [this message]

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=20161026135550.GQ30578@tiger \
    --to=shawnguo@kernel.org \
    --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