public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: andrew@lunn•ch (Andrew Lunn)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] arm: mvebu: support for the PlatHome OpenBlocks AX3 board
Date: Wed, 24 Oct 2012 17:31:31 +0200	[thread overview]
Message-ID: <20121024153131.GG11837@lunn.ch> (raw)
In-Reply-To: <20121024172050.412ff1bf@skate>

On Wed, Oct 24, 2012 at 05:20:50PM +0200, Thomas Petazzoni wrote:
> Andrew,
> 
> On Wed, 24 Oct 2012 17:06:14 +0200, Andrew Lunn wrote:
> 
> > There are two variants of this box, ax3/2 and ax3/4. The ax3/4 can
> > have more RAM and has a mini pci express slot. Do you expect both
> > boards to be supported with one dts file?
> 
> I have the ax3/4 version apparently.
> 
> So, we can have the following possible schemes:
> 
>  + openblocks-ax3.dtsi
>    + openblocks-ax3-2.dts
>    + openblocks-ax3-4.dts
> 
> But I am not sure if using a .dtsi to factorize things common between
> multiple boards is OK. Or we can do:
> 
>  + openblocks-ax3-2.dts
>    + openblocks-ax3-4.dts
> 
> With openblocks-ax3-4.dts being the simple addition of PCIe slot + more
> RAM. That said, I don't have the ax3/2 board anyway, so should we plan
> for something that nobody can test at the moment, or wait for someone
> to get a ax3/2 board, and therefore be able to do the testing? I think
> I prefer to submit dts files that are know to work and have been tested
> on hardware that we have.

Hi Thomas

I agree with the last point. So maybe have a openblocks-ax3-4.dts and
set the compatibility string to plathome,openblocks-ax3-4. 

When somebody gets a ax3/2, they can refactor the common DT into a
dtsi file without causing any compatibility issues.

     Andrew

  reply	other threads:[~2012-10-24 15:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  8:19 [PATCH] arm: mvebu: support for the PlatHome OpenBlocks AX3 board Thomas Petazzoni
2012-10-23  8:42 ` Andrew Lunn
2012-10-23  8:45   ` Thomas Petazzoni
2012-10-23 11:16     ` Jason Cooper
2012-10-24  8:58 ` Gregory CLEMENT
2012-10-24 14:15   ` Thomas Petazzoni
2012-10-24 15:06 ` Andrew Lunn
2012-10-24 15:20   ` Thomas Petazzoni
2012-10-24 15:31     ` Andrew Lunn [this message]
2012-10-24 15:35       ` Thomas Petazzoni
2012-11-26  9:18     ` Hector Oron
2012-11-26  9:25       ` Thomas Petazzoni
2012-11-27 13:00         ` Jason Cooper
2012-11-28  2:45           ` Mio Watanabe
2012-12-16 16:18             ` Hector Oron
2012-10-24 19:33 ` [PATCH v2] arm: mvebu: support for the PlatHome OpenBlocks AX3-4 board Thomas Petazzoni
2012-11-05 17:48   ` Olof Johansson

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=20121024153131.GG11837@lunn.ch \
    --to=andrew@lunn$(echo .)ch \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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