[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141002170519.GA29052@gmail.com>
Date: Thu, 2 Oct 2014 19:05:19 +0200
From: Beniamino Galvani <b.galvani@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-arm-kernel@...ts.infradead.org,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, Victor Wan <victor.wan@...ogic.com>,
Russell King <linux@....linux.org.uk>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Kumar Gala <galak@...eaurora.org>,
Carlo Caione <carlo@...one.org>,
Jerry Cao <jerry.cao@...ogic.com>
Subject: Re: [PATCH 1/6] ARM: meson: add meson8 machine definition
On Thu, Oct 02, 2014 at 11:24:54AM +0200, Arnd Bergmann wrote:
> On Wednesday 01 October 2014 23:29:41 Beniamino Galvani wrote:
> >
> > +static const char * const m8_common_board_compat[] = {
> > + "amlogic,meson8",
> > + NULL,
> > +};
> > +
> > DT_MACHINE_START(AML8726_MX, "Amlogic Meson6 platform")
> > .dt_compat = m6_common_board_compat,
> > MACHINE_END
> >
> > +DT_MACHINE_START(MESON8, "Amlogic Meson8 platform")
> > + .dt_compat = m8_common_board_compat,
> > +MACHINE_END
> >
>
> I'd just add the meson8 string to the m6_common_board_compat list and
> rename it.
>From what I've seen so far the two families are very similar and share
most of the IP cores, so a unique DT machine is a good idea.
Does the MACH_MESON8 Kconfig symbol still make sense or can I drop it
and rename MACH_MESON6 to MACH_MESON?
Beniamino
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists