From: Bryan Brattlof <bb@ti.com> To: "Rafael J. Wysocki" <rafael@kernel.org>, Daniel Lezcano <daniel.lezcano@linaro.org>, Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>, Tero Kristo <kristo@kernel.org> Cc: Keerthy <j-keerthy@ti.com>, Linux PM <linux-pm@vger.kernel.org>, Device Trees <devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>, LKML ARM <linux-arm-kernel@lists.infradead.org>, Bryan Brattlof <bb@ti.com> Subject: [PATCH v3 00/11] enable VTM node for all TI's K3 SoCs Date: Mon, 31 Oct 2022 18:26:51 -0500 [thread overview] Message-ID: <20221031232702.10339-1-bb@ti.com> (raw) Hello again everyone! This series enables the VTM nodes for all of Texas Instrument's K3 SoCs Most of this series updates the k3_j72xx_bandgap driver to conditionally map an eFuse region used by the j721e to work around an issue in its VTM implementation and allows us to save the SPARE_FUSE region on other SoCs We can then update the device tree bindings for the driver and finally define the VTM nodes for each device Thanks for reviewing again ~Bryan **** v2 -> v3 changes[0]: - removed a errant devm_iounmap() I introduced between patches in v2 - collected tags v1 -> v2 changes[1]: - when removing 'fuse_base' from the 'k3_j72xx_bandgap' structure, I forgot to pass 'fuse_base' to get_efuse_values() - removed the descriptions to the generic 'power-domains' property - incorporated Krzysztof's suggestions to the binding description - refactored binding to use allOf: if: {min,max}Items over what I was doing :) Thanks Krzysztof [0] https://lore.kernel.org/lkml/20221025191515.9151-1-bb@ti.com/ [1] https://lore.kernel.org/lkml/20221011231727.8090-1-bb@ti.com/ Bryan Brattlof (11): thermal: k3_j72xx_bandgap: simplify k3_thermal_get_temp() function thermal: k3_j72xx_bandgap: use bool for i2128 erratum flag thermal: k3_j72xx_bandgap: remove fuse_base from structure thermal: k3_j72xx_bandgap: map fuse_base only for erratum workaround dt-bindings: thermal: k3-j72xx: elaborate on binding description dt-bindings: thermal: k3-j72xx: conditionally require efuse reg range arm64: dts: ti: k3-am64-main: add VTM node arm64: dts: ti: k3-am62-wakeup: add VTM node arm64: dts: ti: k3-j721e-mcu-wakeup: add VTM node arm64: dts: ti: k3-j721s2-mcu-wakeup: add VTM node arm64: dts: ti: k3-j7200-mcu-wakeup: add VTM node .../bindings/thermal/ti,j72xx-thermal.yaml | 35 +++++- arch/arm64/boot/dts/ti/k3-am62-thermal.dtsi | 33 ++++++ arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 8 ++ arch/arm64/boot/dts/ti/k3-am62.dtsi | 7 +- arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 8 ++ arch/arm64/boot/dts/ti/k3-am64-thermal.dtsi | 33 ++++++ arch/arm64/boot/dts/ti/k3-am64.dtsi | 4 + .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 8 ++ arch/arm64/boot/dts/ti/k3-j7200-thermal.dtsi | 47 ++++++++ arch/arm64/boot/dts/ti/k3-j7200.dtsi | 3 + .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 9 ++ arch/arm64/boot/dts/ti/k3-j721e-thermal.dtsi | 75 +++++++++++++ arch/arm64/boot/dts/ti/k3-j721e.dtsi | 3 + .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 8 ++ arch/arm64/boot/dts/ti/k3-j721s2-thermal.dtsi | 103 ++++++++++++++++++ arch/arm64/boot/dts/ti/k3-j721s2.dtsi | 3 + drivers/thermal/k3_j72xx_bandgap.c | 67 ++++++------ 17 files changed, 420 insertions(+), 34 deletions(-) create mode 100644 arch/arm64/boot/dts/ti/k3-am62-thermal.dtsi create mode 100644 arch/arm64/boot/dts/ti/k3-am64-thermal.dtsi create mode 100644 arch/arm64/boot/dts/ti/k3-j7200-thermal.dtsi create mode 100644 arch/arm64/boot/dts/ti/k3-j721e-thermal.dtsi create mode 100644 arch/arm64/boot/dts/ti/k3-j721s2-thermal.dtsi -- 2.38.1
WARNING: multiple messages have this Message-ID (diff)
From: Bryan Brattlof <bb@ti.com> To: "Rafael J. Wysocki" <rafael@kernel.org>, Daniel Lezcano <daniel.lezcano@linaro.org>, Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>, Tero Kristo <kristo@kernel.org> Cc: Keerthy <j-keerthy@ti.com>, Linux PM <linux-pm@vger.kernel.org>, Device Trees <devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>, LKML ARM <linux-arm-kernel@lists.infradead.org>, Bryan Brattlof <bb@ti.com> Subject: [PATCH v3 00/11] enable VTM node for all TI's K3 SoCs Date: Mon, 31 Oct 2022 18:26:51 -0500 [thread overview] Message-ID: <20221031232702.10339-1-bb@ti.com> (raw) Hello again everyone! This series enables the VTM nodes for all of Texas Instrument's K3 SoCs Most of this series updates the k3_j72xx_bandgap driver to conditionally map an eFuse region used by the j721e to work around an issue in its VTM implementation and allows us to save the SPARE_FUSE region on other SoCs We can then update the device tree bindings for the driver and finally define the VTM nodes for each device Thanks for reviewing again ~Bryan **** v2 -> v3 changes[0]: - removed a errant devm_iounmap() I introduced between patches in v2 - collected tags v1 -> v2 changes[1]: - when removing 'fuse_base' from the 'k3_j72xx_bandgap' structure, I forgot to pass 'fuse_base' to get_efuse_values() - removed the descriptions to the generic 'power-domains' property - incorporated Krzysztof's suggestions to the binding description - refactored binding to use allOf: if: {min,max}Items over what I was doing :) Thanks Krzysztof [0] https://lore.kernel.org/lkml/20221025191515.9151-1-bb@ti.com/ [1] https://lore.kernel.org/lkml/20221011231727.8090-1-bb@ti.com/ Bryan Brattlof (11): thermal: k3_j72xx_bandgap: simplify k3_thermal_get_temp() function thermal: k3_j72xx_bandgap: use bool for i2128 erratum flag thermal: k3_j72xx_bandgap: remove fuse_base from structure thermal: k3_j72xx_bandgap: map fuse_base only for erratum workaround dt-bindings: thermal: k3-j72xx: elaborate on binding description dt-bindings: thermal: k3-j72xx: conditionally require efuse reg range arm64: dts: ti: k3-am64-main: add VTM node arm64: dts: ti: k3-am62-wakeup: add VTM node arm64: dts: ti: k3-j721e-mcu-wakeup: add VTM node arm64: dts: ti: k3-j721s2-mcu-wakeup: add VTM node arm64: dts: ti: k3-j7200-mcu-wakeup: add VTM node .../bindings/thermal/ti,j72xx-thermal.yaml | 35 +++++- arch/arm64/boot/dts/ti/k3-am62-thermal.dtsi | 33 ++++++ arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 8 ++ arch/arm64/boot/dts/ti/k3-am62.dtsi | 7 +- arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 8 ++ arch/arm64/boot/dts/ti/k3-am64-thermal.dtsi | 33 ++++++ arch/arm64/boot/dts/ti/k3-am64.dtsi | 4 + .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 8 ++ arch/arm64/boot/dts/ti/k3-j7200-thermal.dtsi | 47 ++++++++ arch/arm64/boot/dts/ti/k3-j7200.dtsi | 3 + .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 9 ++ arch/arm64/boot/dts/ti/k3-j721e-thermal.dtsi | 75 +++++++++++++ arch/arm64/boot/dts/ti/k3-j721e.dtsi | 3 + .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 8 ++ arch/arm64/boot/dts/ti/k3-j721s2-thermal.dtsi | 103 ++++++++++++++++++ arch/arm64/boot/dts/ti/k3-j721s2.dtsi | 3 + drivers/thermal/k3_j72xx_bandgap.c | 67 ++++++------ 17 files changed, 420 insertions(+), 34 deletions(-) create mode 100644 arch/arm64/boot/dts/ti/k3-am62-thermal.dtsi create mode 100644 arch/arm64/boot/dts/ti/k3-am64-thermal.dtsi create mode 100644 arch/arm64/boot/dts/ti/k3-j7200-thermal.dtsi create mode 100644 arch/arm64/boot/dts/ti/k3-j721e-thermal.dtsi create mode 100644 arch/arm64/boot/dts/ti/k3-j721s2-thermal.dtsi -- 2.38.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-10-31 23:27 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-31 23:26 Bryan Brattlof [this message] 2022-10-31 23:26 ` [PATCH v3 00/11] enable VTM node for all TI's K3 SoCs Bryan Brattlof 2022-10-31 23:26 ` [PATCH v3 01/11] thermal: k3_j72xx_bandgap: simplify k3_thermal_get_temp() function Bryan Brattlof 2022-10-31 23:26 ` Bryan Brattlof 2022-12-09 15:26 ` [thermal: thermal/next] thermal/drivers/k3_j72xx_bandgap: Simplify " thermal-bot for Bryan Brattlof 2022-10-31 23:26 ` [PATCH v3 02/11] thermal: k3_j72xx_bandgap: use bool for i2128 erratum flag Bryan Brattlof 2022-10-31 23:26 ` Bryan Brattlof 2022-12-09 15:26 ` [thermal: thermal/next] thermal/drivers/k3_j72xx_bandgap: Use " thermal-bot for Bryan Brattlof 2022-10-31 23:26 ` [PATCH v3 03/11] thermal: k3_j72xx_bandgap: remove fuse_base from structure Bryan Brattlof 2022-10-31 23:26 ` Bryan Brattlof 2022-12-09 15:26 ` [thermal: thermal/next] thermal/drivers/k3_j72xx_bandgap: Remove " thermal-bot for Bryan Brattlof 2022-10-31 23:26 ` [PATCH v3 04/11] thermal: k3_j72xx_bandgap: map fuse_base only for erratum workaround Bryan Brattlof 2022-10-31 23:26 ` Bryan Brattlof 2022-12-09 15:26 ` [thermal: thermal/next] thermal/drivers/k3_j72xx_bandgap: Map " thermal-bot for Bryan Brattlof 2022-10-31 23:26 ` [PATCH v3 05/11] dt-bindings: thermal: k3-j72xx: elaborate on binding description Bryan Brattlof 2022-10-31 23:26 ` Bryan Brattlof 2022-12-09 15:26 ` [thermal: thermal/next] " thermal-bot for Bryan Brattlof 2022-10-31 23:26 ` [PATCH v3 06/11] dt-bindings: thermal: k3-j72xx: conditionally require efuse reg range Bryan Brattlof 2022-10-31 23:26 ` Bryan Brattlof 2022-12-09 15:26 ` [thermal: thermal/next] " thermal-bot for Bryan Brattlof 2022-10-31 23:26 ` [PATCH v3 07/11] arm64: dts: ti: k3-am64-main: add VTM node Bryan Brattlof 2022-10-31 23:26 ` Bryan Brattlof 2022-10-31 23:26 ` [PATCH v3 08/11] arm64: dts: ti: k3-am62-wakeup: " Bryan Brattlof 2022-10-31 23:26 ` Bryan Brattlof 2022-10-31 23:27 ` [PATCH v3 09/11] arm64: dts: ti: k3-j721e-mcu-wakeup: " Bryan Brattlof 2022-10-31 23:27 ` Bryan Brattlof 2022-10-31 23:27 ` [PATCH v3 10/11] arm64: dts: ti: k3-j721s2-mcu-wakeup: " Bryan Brattlof 2022-10-31 23:27 ` Bryan Brattlof 2022-10-31 23:27 ` [PATCH v3 11/11] arm64: dts: ti: k3-j7200-mcu-wakeup: " Bryan Brattlof 2022-10-31 23:27 ` Bryan Brattlof 2022-12-06 17:02 ` [PATCH v3 00/11] enable VTM node for all TI's K3 SoCs Daniel Lezcano 2022-12-06 17:02 ` Daniel Lezcano
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20221031232702.10339-1-bb@ti.com \ --to=bb@ti.com \ --cc=amitk@kernel.org \ --cc=daniel.lezcano@linaro.org \ --cc=devicetree@vger.kernel.org \ --cc=j-keerthy@ti.com \ --cc=kristo@kernel.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=nm@ti.com \ --cc=rafael@kernel.org \ --cc=robh+dt@kernel.org \ --cc=rui.zhang@intel.com \ --cc=vigneshr@ti.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.