This is another series of tsens cleanups before we add interrupt support. This applies on top of the earlier two series[1][2] that have already been accepted for 4.19. In this series, we have the following: - splitup 8916 and 8974 register address spaces for SROT and TM - cleanups: move to spdx, dead code removal, removal of id field - Add support to map the SROT address space for DTs that list it separately - Check if TSENS IP is enabled in firmware by querying the SROT space - Add reg-names property to get more readable outputs in /proc/iomem - Add myself as maintainer of tsens Regards, Amit [1] https://lore.kernel.org/lkml/cover.1531895128.git.amit.kucheria@xxxxxxxxxx/ [2] https://lore.kernel.org/lkml/cover.1532600791.git.amit.kucheria@xxxxxxxxxx/ Amit Kucheria (10): arm/arm64: dts: msm8974/msm8916: thermal: Split address space into two dt-bindings: thermal: Fix a typo in documentation thermal: tsens: Add SPDX license identifiers thermal: tsens: Get rid of dead code thermal: tsens: Rename map field in order to add a second address map thermal: tsens: Add the SROT address map thermal: tsens: Check if the IP is correctly enabled by firmware thermal: tsens: Get rid of 'id' field arm64: dts: qcom: Add reg-names for all tsens nodes MAINTAINERS: Add entry for Qualcomm TSENS thermal drivers .../devicetree/bindings/thermal/thermal.txt | 2 +- MAINTAINERS | 7 +++ arch/arm/boot/dts/qcom-msm8974.dtsi | 7 ++- arch/arm64/boot/dts/qcom/msm8916.dtsi | 7 ++- arch/arm64/boot/dts/qcom/msm8996.dtsi | 2 + arch/arm64/boot/dts/qcom/sdm845.dtsi | 2 + drivers/thermal/qcom/tsens-8916.c | 11 +--- drivers/thermal/qcom/tsens-8960.c | 41 +++++------- drivers/thermal/qcom/tsens-8974.c | 11 +--- drivers/thermal/qcom/tsens-common.c | 62 ++++++++++++------- drivers/thermal/qcom/tsens-v2.c | 6 +- drivers/thermal/qcom/tsens.c | 21 +------ drivers/thermal/qcom/tsens.h | 24 +++---- 13 files changed, 99 insertions(+), 104 deletions(-) -- 2.17.1 -- To unsubscribe from this list: send the line "unsubscribe linux-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
