On 05/14, Maxime Ripard wrote: > On Tue, May 13, 2014 at 03:47:32PM -0700, Stephen Boyd wrote: > > On 05/13, Matthias Brugger wrote: > > > + "mediatek,mt6589", > > > + NULL, > > > +}; > > > + > > > +DT_MACHINE_START(MEDIATEK_DT, "Mediatek Cortex-A7 (Device Tree)") > > > + .dt_compat = mediatek_board_dt_compat, > > > +MACHINE_END > > > > You shouldn't need this file at all if the platform is part of > > the multi-platform kernel. > > From a technical point of view, you don't. But it's interesting to > keep it mostly for two things: > - You get to see the platform name in /proc/cpuinfo > - If you ever need to add platform quirks, it's already there > > We had a similar discussion two weeks ago for mach-sunxi with Olof and > Arnd, and ended up keeping this minimal machine. > It looks like it's only useful to make /proc/cpuinfo have the platform name because it really isn't that hard to add this file if we need to add platform quirks. The downside is we have to keep adding compatibles when we support new SoCs. This all leads back to the patch from Rob that removes the .name field from the DT based machine descriptor[1]. I'm not sure that thread ever resolved but it looked like a step in the right direction. At least it matches what arm64 (and what looks like mips) are doing. The concern there was finding which machine descriptor was used for the init path. Perhaps we should only use of_flat_dt_get_machine_name() for the generic machine descriptor so platforms that are using their own machine descriptor get their .name field printed and they know that their descriptor was used (assuming the .name field is unique) but the platforms using the generic descriptor would get more meaningful information and we wouldn't need to have these skeleton machine descriptors. [1] http://thread.gmane.org/gmane.linux.ports.arm.kernel/277536 -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
