On 11/03, Andy Gross wrote: > On Thu, Nov 03, 2016 at 03:42:36PM -0700, Stephen Boyd wrote: > > On 11/03/2016 03:32 PM, Andy Gross wrote: > > >> On 2016-10-27 5:06 PM, Stephen Boyd wrote: > > >>> Please replace this with something more specific for the actual > > >>> board. Preferably with the board manufacturer vendor prefix and > > >>> some sort of string for the board. > > > Something like? > > > > > > "huawei,nexus-6P", "qcom,msm8994" > > > > Sure, except completely remove qcom,msm8994 from there. > > Hmmm ok. I just briefly looked at one of the sony boards and used that as an > example. So there shouldn't be any link to the underlying soc in the compat? Two people asked the same question. I don't see how having the SoC in the root compatible string does anything. Of course, having it there doesn't hurt anything either so I don't really care. And it may help if we want to test for SoC compatibility at some point. Of course, we have an SoC node, so I'd think we would put the SoC model number into that node's compatible string. In the ePAPR it looks like they have compatible = “fsl,mpc8572ds”, which is a board/platform. The "SoC" on there is an mpc8572e. In practice, there doesn't seem to be any consistency here and it feels like everything is vague on purpose with regards to compatible strings, so either way is fine for me. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
