On Tue, Jun 20, 2017 at 4:32 PM, Wangtao (Kevin, Kirin) <kevin.wangtao@xxxxxxxxxxxxx> wrote: > > > 在 2017/6/20 15:38, Guodong Xu 写道: >> >> >> >> 2017年6月20日 上午11:49,"Tao Wang" <kevin.wangtao@xxxxxxxxxxxxx >> <mailto:kevin.wangtao@xxxxxxxxxxxxx>>写道: >> >> Bind thermal sensor driver for Hi3660. >> >> Signed-off-by: Tao Wang <kevin.wangtao@xxxxxxxxxxxxx >> <mailto:kevin.wangtao@xxxxxxxxxxxxx>> >> Signed-off-by: Leo Yan <leo.yan@xxxxxxxxxx >> <mailto:leo.yan@xxxxxxxxxx>> >> --- >> arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 7 +++++++ >> 1 file changed, 7 insertions(+) >> >> diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi >> b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi >> index 3983086..cc67958 100644 >> --- a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi >> +++ b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi >> @@ -156,5 +156,12 @@ >> >> >> i am wondering which tree this patch should be applied to. Actually Olof >> Johansson olof@xxxxxxxxx <mailto:olof@xxxxxxxxx> just merged hi3660 dts into >> his tree. You should better rebase you dts patch onto that. > > Can you share me the git path? As of this morning, it has shown up in linux next tag: next-20170620 https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm64/boot/dts/hisilicon?h=next-20170620 -Guodong >> >> >> >> clock-names = "uartclk", "apb_pclk"; >> status = "disabled"; >> }; >> + >> + tsensor: tsensor { >> + compatible = "hisilicon,thermal-hi3660"; >> + reg = <0x0 0xfff30000 0x0 0x1000>; >> + #thermal-sensor-cells = <1>; >> + status = "ok"; >> >> >> please remove status ok. that's default. redundant. > > ok >> >> >> + }; >> }; >> }; >> -- >> 1.7.9.5 >> >> >> _______________________________________________ >> linux-arm-kernel mailing list >> linux-arm-kernel@xxxxxxxxxxxxxxxxxxx >> <mailto:linux-arm-kernel@xxxxxxxxxxxxxxxxxxx> >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >> <http://lists.infradead.org/mailman/listinfo/linux-arm-kernel> >> >> > -- 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