在 2015/3/20 14:13, Leo Yan 写道: > On Fri, Mar 20, 2015 at 11:10:16AM +0800, kongxinwei wrote: >> hi Mark Rutland: >> >> 在 2015/3/19 21:59, Mark Rutland 写道: >>> On Thu, Mar 19, 2015 at 07:57:26AM +0000, kongxinwei wrote: >>>> The Linaro connect introduce 96boards series in Hong Kong,The HiKey board >>>> is the first board to be certified 96Boards Consumer Edition compatible. >>>> This board is based on the HiSilicon SoC. you can get more information >>>> from https://www.96boards.org. >>>> >>>> The hisilicon SoC contains thermal module, this thermal module has 4 sensors, >>>> >>>> - sensor 0: local sensor; >>>> - sensor 1: remote sensor for ACPU cluster 1; >>>> - sensor 2: remote sensor for ACPU cluster 2; >>>> - sensor 3: remote sensor for GPU; >>>> >>>> It can obtain this device temperature by operating this hardware. The new >>>> sensor driver satisfies thermal framework and to realize the ACPU ,GPU and >>>> so on to cool function. >>>> >>>> kongxinwei (3): >>>> thermal: hisilicon: add new hisilicon thermal sensor driver >>>> dts: hi6220: enable thermal sensor for hisilicon SoC >>>> dt-bindings: Document the hi6220 thermal sensor bindings >>>> >>>> .../bindings/thermal/hisilicon-thermal.txt | 51 ++ >>>> arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 153 ++++++ >>>> drivers/thermal/Kconfig | 8 + >>>> drivers/thermal/Makefile | 1 + >>>> drivers/thermal/hisi_thermal.c | 531 +++++++++++++++++++++ >>> >>> Mainline does not have a hi6220 dtsi. >>> >>> Which tree is this against? >>> >>> What are your dependencies? >>> >>> Mark. >>> >> Hikey board code are being upstreamed by our team.If hi6220 dtsi be accepted, this patch is ok. > > Xinwei, u could resend this patch after hi6220 dtsi related patches has > been merged. Suggest this patchset are only for thermal driver. > > Thanks, > Leo Yan > Oh,i wish that many persons review it and give some comments, then i will send v2 patch and reduce dts file. Thanks, Xin Wei > . > -- 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
