On Wed, Oct 12, 2016 at 02:37:32AM -0700, Jeremy McNicoll wrote: > +/ { > + model = "HUAWEI MSM8994 ANGLER rev-1.01"; > + compatible = "qcom,msm8994"; > + qcom,board-id= <8026 0>; > +}; This last property is undocumented, and unused. > +/ { > + model = "Qualcomm Technologies, Inc. MSM 8994v2.0"; > + compatible = "qcom,msm8994"; > + qcom,msm-id = <207 0x20000>; > + > +}; Likewise here. [...] > +/memreserve/ 0x00000000 0x00001000; > +/memreserve/ 0xac1c0000 0x00001000; Why? What are these attempting to protect? Given the kernel can still map these regions with cacheable mappings, is this definitely sufficient? [...] > +/ { > + model = "Qualcomm Technologies, Inc. MSM 8994"; > + compatible = "qcom,msm8994"; > + qcom,msm-id = <207 0x0>; > + qcom,pmic-id = <0x10009 0x1000A 0x0 0x0>; Two undocumented and unused properties. > + timer { > + compatible = "arm,armv8-timer"; > + interrupts = <1 2 0xff08>, > + <1 3 0xff08>, > + <1 4 0xff08>, > + <1 1 0xff08>; > + clock-frequency = <19200000>; > + }; Why is the bootloader not configuring the frequency register? > + clocks { > + xo_board: xo_board { > + compatible = "fixed-clock"; > + #clock-cells = <0>; > + clock-frequency = <19200000>; > + }; > + > + sleep_clk: sleep_clk { > + compatible = "fixed-clock"; > + #clock-cells = <0>; > + clock-frequency = <32768>; > + }; > + }; No clocks node is necessary. Please put these under the root node. Thanks, Mark. -- 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