From: Carlo Caione <carlo@caione.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-serial@vger.kernel.org, linux@arm.linux.org.uk,
robh+dt@kernel.org, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, daniel.lezcano@linaro.org,
tglx@linutronix.de, gregkh@linuxfoundation.org, jslaby@suse.cz,
grant.likely@linaro.org, b.galvani@gmail.com
Subject: Re: [PATCH 4/7] ARM: meson: add basic support for MesonX SoCs
Date: Mon, 18 Aug 2014 15:27:13 +0200 [thread overview]
Message-ID: <20140818132713.GA28819@carlo-MacBookPro> (raw)
In-Reply-To: <20140817142115.GB15297@lukather>
On Sun, Aug 17, 2014 at 04:21:15PM +0200, Maxime Ripard wrote:
> Hi Carlo,
Hi Maxime,
thank you for reviewing also these patches, I'll keep you in CC for the
next revisions if you are interested.
> > +static __init void meson_init_machine_devicetree(void)
> > +{
> > + of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL);
> > +}
>
> This is the default, you can just remove it
Agree
> > +static const char * const m6_common_board_compat[] = {
> > + "amlogic,8726_mx",
> > + "amlogic,8726_mxs",
> > + "amlogic,8726_mxl",
> > + "amlogic,meson6",
>
> Why are all those compatibles needed? Usually, you add a single one
> per SoC (which would be the last in your case I guess.
They are taken from the weird DTS in the original Amlogic sources but I
guess you are right. I am actually more inclined to just leave "8726_mx"
and "meson6" since online you can find equally both the versions for
exactly the same SoCs.
> > + NULL,
> > +};
> > +
> > +DT_MACHINE_START(AML8726_MX, "Amlogic Meson6 platform")
> > + .init_machine = meson_init_machine_devicetree,
>
> And since you don't need the init machine, you can just use the
> generic machine support. I'm not sure what's been decided on this,
> should we remove such empty machines?
I can get rid of the .init_machine but what about the .dt_compat field?
Thanks,
--
Carlo Caione
next prev parent reply other threads:[~2014-08-18 13:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 10:49 [PATCH 0/7] ARM: meson: add preliminary support for MesonX/Meson6 SoCs Carlo Caione
2014-08-17 10:49 ` [PATCH 1/7] ARM: meson: debug: add debug UART for earlyprintk support Carlo Caione
2014-08-17 10:49 ` [PATCH 2/7] ARM: meson: serial: add MesonX SoC on-chip uart driver Carlo Caione
2014-08-28 7:51 ` Carlo Caione
2014-09-06 18:28 ` Carlo Caione
2014-09-06 18:38 ` Greg KH
2014-09-06 18:51 ` Carlo Caione
2014-08-17 10:49 ` [PATCH 3/7] ARM: meson6: clocksource: add Meson6 timer support Carlo Caione
2014-08-18 11:59 ` Matthias Brugger
2014-08-18 14:11 ` Carlo Caione
2014-08-18 16:27 ` Mark Rutland
2014-08-19 16:01 ` Carlo Caione
2014-08-17 10:49 ` [PATCH 4/7] ARM: meson: add basic support for MesonX SoCs Carlo Caione
2014-08-17 14:21 ` Maxime Ripard
2014-08-18 13:27 ` Carlo Caione [this message]
2014-08-18 15:10 ` Matthias Brugger
2014-08-18 19:11 ` Maxime Ripard
2014-08-17 10:49 ` [PATCH 5/7] ARM: meson: dts: add basic Meson/Meson6/Meson6-atv1200 DTSI/DTS Carlo Caione
2014-08-17 14:42 ` Beniamino Galvani
2014-08-17 15:21 ` Carlo Caione
2014-08-18 16:15 ` Mark Rutland
2014-08-18 16:17 ` Mark Rutland
2014-08-19 16:16 ` Carlo Caione
2014-08-23 11:27 ` Andreas Färber
2014-08-17 10:49 ` [PATCH 6/7] ARM: meson: update defconfigs Carlo Caione
2014-08-18 10:31 ` Matthias Brugger
2014-08-18 13:31 ` Carlo Caione
[not found] ` <1408272594-10814-1-git-send-email-carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org>
2014-08-17 10:49 ` [PATCH 7/7] ARM: meson: update documentation (uart, timer and vendors) Carlo Caione
2014-08-18 10:36 ` Matthias Brugger
2014-08-18 13:33 ` Carlo Caione
2014-08-23 12:24 ` Andreas Färber
2014-08-17 14:29 ` [PATCH 0/7] ARM: meson: add preliminary support for MesonX/Meson6 SoCs Beniamino Galvani
2014-08-17 15:25 ` Carlo Caione
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=20140818132713.GA28819@carlo-MacBookPro \
--to=carlo@caione.org \
--cc=b.galvani@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jslaby@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).