On Sep 9, 2013, at 4:42 PM, Rohit Vaswani wrote:
On 9/9/2013 2:25 PM, Kumar Gala wrote:I was saying qcom,apq8074-dragonboard or we can do the dir thing as we don't have that mean qcom/msm device trees.<snip>Coming back to this, it would be better if the naming to be consistent with what we call our ARCH - msm and not qcom.
On Fri, Sep 06, 2013 at 12:32:22PM -0700, Rohit Vaswani wrote:
If we do this we should use qcom, not msm as the prefix. Match the device tree vendor prefix.Will do.This patch adds basic board support for APQ8074 DragonboardPlease add boards alphabetically.
<snip>
dtb-$(CONFIG_ARCH_MSM) += msm8660-surf.dtb \
- msm8960-cdp.dtb
+ msm8960-cdp.dtb \
+ apq8074-dragonboard.dtb
Sure. But the board is called an APQ8074 and we wanted to keep the naming consistent with that.dtb-$(CONFIG_ARCH_MVEBU) += armada-370-db.dtb \arch/arm/boot/dts/ is getting really crowded. It's been working best if the SoC
armada-370-mirabox.dtb \
armada-370-rd.dtb \
diff --git a/arch/arm/boot/dts/apq8074-dragonboard.dts b/arch/arm/boot/dts/apq8074-dragonboard.dts
new file mode 100644
index 0000000..5b7b6a0
--- /dev/null
+++ b/arch/arm/boot/dts/apq8074-dragonboard.dts
family or vendor is used as a prefix to keep things a bit more organized. In
that spirit, prefixing these with msm-<foo> makes sense. Can you please do so?
msm8974-dragonboard signifies quite clearly what the board is.
- k