On Tue 21 Jun 10:22 PDT 2016, Srinivas Kandagatla wrote: [..] > diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dts b/arch/arm64/boot/dts/qcom/apq8096-db820c.dts [..] > + > +/ { > + model = "Qualcomm Technologies, Inc. DB820c"; > + compatible = "qcom,apq8096-sbc"; I'm still not buying the concept of this being the one and only single-board-computer. If this compatible fully and exclusively identifies this particular board then dtbTool should be updated to follow the product name "qcom,apq8096-db820c". If on the other hand this identifies a class of single-board-computers, then the compatible should list both "qcom,apq8096-dtb820c" and "qcom,apq8096-sbc". Further more, the ePAPR defines this property as: "Specifies a list of platform architectures with which this platform is compatible. This property can be used by operating systems in selecting platform specific code." So I think we should follow the common pattern of having the least significant entry being "qcom,apq8096". > +}; Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html