soc: imx: Enable additional functionality of i.MX8M Mini
Subsystems (2)
v2 cover soc: imx: Enable additional functionality of i.MX8M Mini
The GPCv2 controller on the i.MX8M Mini is compatible with the driver used for the i.MX8MQ except for the register locations and names. The GPCv2 controller is used to enable additional periperals currently unavailable on the i.MX8M Mini. In order to make them function, the GPCv2 needs to be adapted so the drivers can associate their power domain to the GPCv2 to enable them.
This series makes one include file slightly more generic, adds the iMX8M Mini entries, updates the bindings, adds them to the device tree, then associates the new power domain to both the OTG and PCIe controllers.
Some peripherals may need additional power domain drivers in the future due to limitations of the GPC driver, but the drivers for VPU and others are not available yet.
Adam Ford (7):
soc: imx: gpcv2: Rename imx8mq-power.h to imx8m-power.h
soc: imx: gpcv2: Update imx8m-power.h to include iMX8M Mini
soc: imx: gpcv2: add support for i.MX8M Mini SoC
dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
arm64: dts: imx8mm: add GPC power domains
ARM64: dts: imx8mm: Fix clocks and power domain for USB OTG
arm64: dts: imx8mm: Add PCIe support
.../bindings/power/fsl,imx-gpcv2.txt | 6 +-
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 127 ++++++++-
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +-
drivers/soc/imx/gpcv2.c | 246 +++++++++++++++++-
.../power/{imx8mq-power.h => imx8m-power.h} | 14 +
5 files changed, 387 insertions(+), 8 deletions(-)
rename include/dt-bindings/power/{imx8mq-power.h => imx8m-power.h} (57%)Signature · 1 line
2.20.1
PATCH v2 1/7 soc: imx: gpcv2: Rename imx8mq-power.h to imx8m-power.h
In preparation to add support for i.MX8M Mini, this renames the existing file to be more generic, so it doesn't become necessary to include multiple files to accomplish the same task in the future.
---
V2: No Change
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +-
drivers/soc/imx/gpcv2.c | 2 +-
include/dt-bindings/power/{imx8mq-power.h => imx8m-power.h} | 0
3 files changed, 2 insertions(+), 2 deletions(-)arch/arm64/boot/dts/freescale/imx8mq.dtsi +1 -1
@@ -5,7 +5,7 @@ */ #include <dt-bindings/clock/imx8mq-clock.h> -#include <dt-bindings/power/imx8mq-power.h> +#include <dt-bindings/power/imx8m-power.h> #include <dt-bindings/reset/imx8mq-reset.h> #include <dt-bindings/gpio/gpio.h> #include "dt-bindings/input/input.h"
drivers/soc/imx/gpcv2.c +1 -1
@@ -15,7 +15,7 @@#include <linux/regmap.h> #include <linux/regulator/consumer.h> #include <dt-bindings/power/imx7-power.h> -#include <dt-bindings/power/imx8mq-power.h> +#include <dt-bindings/power/imx8m-power.h> #define GPC_LPCR_A_CORE_BSC 0x000
include/dt-bindings/power/imx8m-power.h renamed from include/dt-bindings/power/imx8mq-power.h +0 -0
Signature · 1 line
2.20.1
PATCH v2 2/7 soc: imx: gpcv2: Update imx8m-power.h to include iMX8M Mini
In reply to Adam FordIn preparation for i.MX8M Mini support in the GPC driver, the include file used by both the device tree and the source needs to have the appropriate references for it.
---
V2: No Change
include/dt-bindings/power/imx8m-power.h | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
include/dt-bindings/power/imx8m-power.h +14 -0
@@ -18,4 +18,18 @@#define IMX8M_POWER_DOMAIN_MIPI_CSI2 9#define IMX8M_POWER_DOMAIN_PCIE2 10 +#define IMX8MM_POWER_DOMAIN_MIPI 0 +#define IMX8MM_POWER_DOMAIN_PCIE 1 +#define IMX8MM_POWER_DOMAIN_USB_OTG1 2 +#define IMX8MM_POWER_DOMAIN_USB_OTG2 3 +#define IMX8MM_POWER_DOMAIN_DDR1 4 +#define IMX8MM_POWER_DOMAIN_GPU2D 5 +#define IMX8MM_POWER_DOMAIN_GPU 6 +#define IMX8MM_POWER_DOMAIN_VPU 7 +#define IMX8MM_POWER_DOMAIN_GPU3D 8 +#define IMX8MM_POWER_DOMAIN_DISP 9 +#define IMX8MM_POWER_VPU_G1 10 +#define IMX8MM_POWER_VPU_G2 11 +#define IMX8MM_POWER_VPU_H1 12 +#endif
Signature · 1 line
2.20.1
Rob Herring
maintainerRe: [PATCH V2 2/7] soc: imx: gpcv2: Update imx8m-power.h to include iMX8M Mini
Quoted 22 lines · Adam Ford
In preparation for i.MX8M Mini support in the GPC driver, the include file used by both the device tree and the source needs to have the appropriate references for it.
Signed-off-by Adam Ford <[email protected]>---
V2: No Changeinclude/dt-bindings/power/imx8m-power.h | 14 ++++++++++++++ 1 file changed, 14 insertions(+)include/dt-bindings/power/imx8m-power.h +3
-0@@ -18,4 +18,18 @@#define IMX8M_POWER_DOMAIN_MIPI_CSI2 9#define IMX8M_POWER_DOMAIN_PCIE2 10 +#define IMX8MM_POWER_DOMAIN_MIPI 0 +#define IMX8MM_POWER_DOMAIN_PCIE 1 +#define IMX8MM_POWER_DOMAIN_USB_OTG1 2
include/dt-bindings/power/imx8m-power.h line 33
Quoted 10 lines
include/dt-bindings/power/imx8m-power.h +10
-0+#define IMX8MM_POWER_DOMAIN_USB_OTG2 3 +#define IMX8MM_POWER_DOMAIN_DDR1 4 +#define IMX8MM_POWER_DOMAIN_GPU2D 5 +#define IMX8MM_POWER_DOMAIN_GPU 6 +#define IMX8MM_POWER_DOMAIN_VPU 7 +#define IMX8MM_POWER_DOMAIN_GPU3D 8 +#define IMX8MM_POWER_DOMAIN_DISP 9 +#define IMX8MM_POWER_VPU_G1 10 +#define IMX8MM_POWER_VPU_G2 11 +#define IMX8MM_POWER_VPU_H1 12
Why is _DOMAIN missing from the last 3?
Quoted 5 lines
include/dt-bindings/power/imx8m-power.h +1
-0+#endif Signature · 1 line
2.20.1
Re: [PATCH V2 2/7] soc: imx: gpcv2: Update imx8m-power.h to include iMX8M Mini
Quoted 21 lines · Rob Herring
Quoted 19 lines · Adam Ford
In preparation for i.MX8M Mini support in the GPC driver, the include file used by both the device tree and the source needs to have the appropriate references for it.
Signed-off-by Adam Ford <[email protected]>---
V2: No Changeinclude/dt-bindings/power/imx8m-power.h | 14 ++++++++++++++ 1 file changed, 14 insertions(+)include/dt-bindings/power/imx8m-power.h +0
-0@@ -18,4 +18,18 @@#define IMX8M_POWER_DOMAIN_MIPI_CSI2 9#define IMX8M_POWER_DOMAIN_PCIE2 10
Quoted 15 lines
include/dt-bindings/power/imx8m-power.h line 33
Quoted 13 lines
include/dt-bindings/power/imx8m-power.h +13
-0+#define IMX8MM_POWER_DOMAIN_MIPI 0 +#define IMX8MM_POWER_DOMAIN_PCIE 1 +#define IMX8MM_POWER_DOMAIN_USB_OTG1 2 +#define IMX8MM_POWER_DOMAIN_USB_OTG2 3 +#define IMX8MM_POWER_DOMAIN_DDR1 4 +#define IMX8MM_POWER_DOMAIN_GPU2D 5 +#define IMX8MM_POWER_DOMAIN_GPU 6 +#define IMX8MM_POWER_DOMAIN_VPU 7 +#define IMX8MM_POWER_DOMAIN_GPU3D 8 +#define IMX8MM_POWER_DOMAIN_DISP 9 +#define IMX8MM_POWER_VPU_G1 10 +#define IMX8MM_POWER_VPU_G2 11 +#define IMX8MM_POWER_VPU_H1 12Why is
_DOMAINmissing from the last 3?
I will go back and review it.
adam
Quoted 6 lines
Quoted 6 lines
include/dt-bindings/power/imx8m-power.h +1
-1+#endif --2.20.1
PATCH v2 3/7 soc: imx: gpcv2: add support for i.MX8M Mini SoC
In reply to Adam FordThe GPCv2 on the Freescale i.MX8M Mini SoC works in the same way as the GPCv2 on the i.MX8MQ, but with slightly different power domains and mapping.
This patch adds the necessary tables so the GPC can operate on the i.MX8M Mini.
---
V2: No Change
drivers/soc/imx/gpcv2.c | 244 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 244 insertions(+)
drivers/soc/imx/gpcv2.c +244 -0
@@ -41,6 +41,20 @@#define IMX8M_PCIE1_A53_DOMAIN BIT(3)#define IMX8M_MIPI_A53_DOMAIN BIT(2) +#define IMX8MM_VPU_H1_A53_DOMAIN BIT(15) +#define IMX8MM_VPU_G2_A53_DOMAIN BIT(14) +#define IMX8MM_VPU_G1_A53_DOMAIN BIT(13) +#define IMX8MM_DISP_MIX_A53_DOMAIN BIT(12) +#define IMX8MM_GPU_3D_A53_DOMAIN BIT(11) +#define IMX8MM_VPUMIX_A53_DOMAIN BIT(10) +#define IMX8MM_GPUMIX_A53_DOMAIN BIT(9) +#define IMX8MM_GPU_2D_A53_DOMAIN BIT(8) +#define IMX8MM_DDR1_A53_DOMAIN BIT(7) +#define IMX8MM_OTG2_A53_DOMAIN BIT(5) +#define IMX8MM_OTG1_A53_DOMAIN BIT(4) +#define IMX8MM_PCIE_A53_DOMAIN BIT(3) +#define IMX8MM_MIPI_A53_DOMAIN BIT(2) +#define GPC_PU_PGC_SW_PUP_REQ 0x0f8#define GPC_PU_PGC_SW_PDN_REQ 0x104
@@ -64,6 +78,20 @@#define IMX8M_PCIE1_SW_Pxx_REQ BIT(1)#define IMX8M_MIPI_SW_Pxx_REQ BIT(0) +#define IMX8MM_VPU_H1_SW_Pxx_REQ BIT(13) +#define IMX8MM_VPU_G2_SW_Pxx_REQ BIT(12) +#define IMX8MM_VPU_G1_SW_Pxx_REQ BIT(11) +#define IMX8MM_DISP_SW_Pxx_REQ BIT(10) +#define IMX8MM_GPU_3D_SW_Pxx_REQ BIT(9) +#define IMX8MM_VPU_SW_Pxx_REQ BIT(8) +#define IMX8MM_GPU_SW_Pxx_REQ BIT(7) +#define IMX8MM_GPU_2D_SW_PXX_REQ BIT(6) +#define IMX8MM_DDR1_SW_Pxx_REQ BIT(5) +#define IMX8MM_OTG2_SW_Pxx_REQ BIT(3) +#define IMX8MM_OTG1_SW_Pxx_REQ BIT(2) +#define IMX8MM_PCIE_SW_Pxx_REQ BIT(1) +#define IMX8MM_MIPI_SW_Pxx_REQ BIT(0) +#define GPC_M4_PU_PDN_FLG 0x1bc#define GPC_PU_PWRHSK 0x1fc
@@ -72,6 +100,10 @@#define IMX8M_VPU_HSK_PWRDNREQN BIT(5)#define IMX8M_DISP_HSK_PWRDNREQN BIT(4) +#define IMX8MM_GPU_HSK_PWRDNREQN BIT(9) +#define IMX8MM_VPU_HSK_PWRDNREQN BIT(8) +#define IMX8MM_DISP_HSK_PWRDNREQN BIT(7) +/* * The PGC offset values in Reference Manual * (Rev. 1, 01/2018 and the older ones) GPC chapter's
@@ -94,6 +126,24 @@#define IMX8M_PGC_MIPI_CSI2 28#define IMX8M_PGC_PCIE2 29 +/* +* Taken from i.MX8M Mini values from Reference +* Manual, Rev. 2, 08/2019 +*/ +#define IMX8MM_PGC_MIPI 16 +#define IMX8MM_PGC_PCIE 17 +#define IMX8MM_PGC_OTG1 18 +#define IMX8MM_PGC_OTG2 19 +#define IMX8MM_PGC_DDR1 21 +#define IMX8MM_PGC_GPU2D 22 +#define IMX8MM_PGC_GPU 23 +#define IMX8MM_PGC_VPU 24 +#define IMX8MM_PGC_GPU3D 25 +#define IMX8MM_PGC_DISP 26 +#define IMX8MM_PGC_VPU_G1 27 +#define IMX8MM_PGC_VPU_G2 28 +#define IMX8MM_PGC_VPU_H1 29 +#define GPC_PGC_CTRL (n) (0x800 + (n) * 0x40)#define GPC_PGC_SR (n) (GPC_PGC_CTRL(n) + 0xc)
@@ -278,6 +328,7 @@ static const struct imx_pgc_domain_data imx7_pgc_domain_data = { .reg_access_table = &imx7_access_table, }; +/* i.MX8M dual/QuadLite/Quad */ static const struct imx_pgc_domain imx8m_pgc_domains[] = { [IMX8M_POWER_DOMAIN_MIPI ] = { .genpd = {
@@ -442,6 +493,198 @@ static const struct imx_pgc_domain_data imx8m_pgc_domain_data = { .reg_access_table = &imx8m_access_table, }; +/* i.MX8M Mini */ +static const struct imx_pgc_domain imx8mm_pgc_domains[] = { + [IMX8MM_POWER_DOMAIN_MIPI ] = { + .genpd = { + .name ="mipi" , + }, + .bits = { + .pxx = IMX8MM_MIPI_SW_Pxx_REQ, + .map =IMX8MM_MIPI_A53_DOMAIN , + }, + .pgc =IMX8M_PGC_MIPI , + }, + + [IMX8MM_POWER_DOMAIN_PCIE ] = { + .genpd = { + .name ="pcie1" , + }, + .bits = { + .pxx = IMX8MM_PCIE_SW_Pxx_REQ, + .map =IMX8MM_PCIE_A53_DOMAIN , + }, + .pgc =IMX8MM_PGC_PCIE , + }, + + [IMX8MM_POWER_DOMAIN_USB_OTG1 ] = { + .genpd = { + .name ="usb-otg1" , + }, + .bits = { + .pxx = IMX8MM_OTG1_SW_Pxx_REQ, + .map =IMX8MM_OTG1_A53_DOMAIN , + }, + .pgc =IMX8M_PGC_OTG1 , + }, + + [IMX8MM_POWER_DOMAIN_USB_OTG2 ] = { + .genpd = { + .name ="usb-otg2" , + }, + .bits = { + .pxx = IMX8MM_OTG2_SW_Pxx_REQ, + .map =IMX8MM_OTG2_A53_DOMAIN , + }, + .pgc =IMX8M_PGC_OTG2 , + }, + + [IMX8MM_POWER_DOMAIN_DDR1 ] = { + .genpd = { + .name ="ddr1" , + }, + .bits = { + .pxx = IMX8MM_DDR1_SW_Pxx_REQ, + .map =IMX8MM_DDR1_A53_DOMAIN , + }, + .pgc =IMX8M_PGC_DDR1 , + }, + + [IMX8MM_POWER_DOMAIN_GPU2D ] = { + .genpd = { + .name ="gpu2d" , + }, + .bits = { + .pxx =IMX8MM_GPU_2D_SW_PXX_REQ , + .map =IMX8MM_GPU_2D_A53_DOMAIN , + .hsk =IMX8MM_GPU_HSK_PWRDNREQN , + }, + .pgc =IMX8MM_PGC_GPU2D , + }, + + + [IMX8MM_POWER_DOMAIN_GPU ] = { + .genpd = { + .name ="gpu" , + }, + .bits = { + .pxx = IMX8MM_GPU_SW_Pxx_REQ, + .map =IMX8MM_GPUMIX_A53_DOMAIN , + .hsk =IMX8MM_GPU_HSK_PWRDNREQN , + }, + .pgc =IMX8M_PGC_GPU , + }, + + [IMX8MM_POWER_DOMAIN_VPU ] = { + .genpd = { + .name ="vpu" , + }, + .bits = { + .pxx = IMX8MM_VPU_SW_Pxx_REQ, + .map =IMX8MM_VPUMIX_A53_DOMAIN , + .hsk =IMX8MM_VPU_HSK_PWRDNREQN , + }, + .pgc =IMX8M_PGC_VPU , + }, + + [IMX8MM_POWER_DOMAIN_GPU3D ] = { + .genpd = { + .name ="gpu3d" , + }, + .bits = { + .pxx = IMX8MM_GPU_3D_SW_Pxx_REQ, + .map =IMX8MM_GPU_3D_A53_DOMAIN , + .hsk =IMX8MM_GPU_HSK_PWRDNREQN , + }, + .pgc =IMX8MM_PGC_GPU2D , + }, + + [IMX8MM_POWER_DOMAIN_DISP ] = { + .genpd = { + .name ="disp" , + }, + .bits = { + .pxx = IMX8MM_DISP_SW_Pxx_REQ, + .map =IMX8MM_DISP_MIX_A53_DOMAIN , + .hsk =IMX8MM_DISP_HSK_PWRDNREQN , + }, + .pgc =IMX8M_PGC_DISP , + }, + + [IMX8MM_POWER_VPU_G1 ] = { + .genpd = { + .name ="vpu_g1" , + }, + .bits = { + .pxx = IMX8MM_VPU_G1_SW_Pxx_REQ, + .map =IMX8MM_VPU_G1_A53_DOMAIN , + }, + .pgc =IMX8M_PGC_MIPI_CSI1 , + }, + + [IMX8MM_POWER_VPU_G2 ] = { + .genpd = { + .name ="vpu_g2" , + }, + .bits = { + .pxx = IMX8MM_VPU_G2_SW_Pxx_REQ, + .map =IMX8MM_VPU_G2_A53_DOMAIN , + }, + .pgc =IMX8M_PGC_MIPI_CSI2 , + }, + + [IMX8MM_POWER_VPU_H1 ] = { + .genpd = { + .name ="vpu_h1" , + }, + .bits = { + .pxx = IMX8MM_VPU_H1_SW_Pxx_REQ, + .map =IMX8MM_VPU_H1_A53_DOMAIN , + }, + .pgc =IMX8M_PGC_PCIE2 , + }, +}; + +static const struct regmap_range imx8mm_yes_ranges[] = { +regmap_reg_range (GPC_LPCR_A_CORE_BSC , +GPC_PU_PWRHSK ), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_MIPI ), +GPC_PGC_SR (IMX8MM_PGC_MIPI )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_PCIE ), +GPC_PGC_SR (IMX8MM_PGC_PCIE )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_OTG1 ), +GPC_PGC_SR (IMX8MM_PGC_OTG1 )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_OTG2 ), +GPC_PGC_SR (IMX8MM_PGC_OTG2 )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_DDR1 ), +GPC_PGC_SR (IMX8MM_PGC_DDR1 )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_GPU2D ), +GPC_PGC_SR (IMX8MM_PGC_GPU2D )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_GPU ), +GPC_PGC_SR (IMX8MM_PGC_GPU )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_VPU ), +GPC_PGC_SR (IMX8MM_PGC_VPU )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_DISP ), +GPC_PGC_SR (IMX8MM_PGC_DISP )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_VPU_G1 ), +GPC_PGC_SR (IMX8MM_PGC_VPU_G1 )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_VPU_G2 ), +GPC_PGC_SR (IMX8MM_PGC_VPU_G2 )), +regmap_reg_range (GPC_PGC_CTRL (IMX8MM_PGC_VPU_H1 ), +GPC_PGC_SR (IMX8MM_PGC_VPU_H1 )), +}; + +static const struct regmap_access_table imx8mm_access_table = { + .yes_ranges = imx8mm_yes_ranges, + .n_yes_ranges =ARRAY_SIZE (imx8mm_yes_ranges), +}; + +static const struct imx_pgc_domain_data imx8mm_pgc_domain_data = { + .domains = imx8mm_pgc_domains, + .domains_num =ARRAY_SIZE (imx8mm_pgc_domains), + .reg_access_table = &imx8mm_access_table, +}; +static int imx_pgc_get_clocks (struct imx_pgc_domain *domain) {int i, ret;
@@ -641,6 +884,7 @@ static int imx_gpcv2_probe(struct platform_device *pdev)static const struct of_device_id imx_gpcv2_dt_ids[] = { { .compatible ="fsl,imx7d-gpc" , .data = &imx7_pgc_domain_data, }, { .compatible ="fsl,imx8mq-gpc" , .data = &imx8m_pgc_domain_data, }, + { .compatible ="fsl,imx8mm-gpc" , .data = &imx8mm_pgc_domain_data, }, { } };
Signature · 1 line
2.20.1
PATCH v2 4/7 dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
In reply to Adam FordThe with the recent additions to the driver, the GPCv2 driver can support the i.MX8M Mini, but it needs updated 'compatible' entry to use the proper table.
This patch adds the i.MX8MM to the compatible list of devices.
---
V2: No Change
Documentation/devicetree/bindings/power/fsl,imx-gpcv2.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/power/fsl,imx-gpcv2.txt +4 -2
@@ -9,6 +9,7 @@ Required properties: - compatible: Should be one of: - "fsl,imx7d-gpc" - "fsl,imx8mq-gpc" + - "fsl,imx8mm-gpc" - reg: should be register base and length as documented in the datasheet
@@ -24,8 +25,9 @@ which, in turn, is expected to contain the following: Required properties: - reg: Power domain index. Valid values are defined in - include/dt-bindings/power/imx7-power.h for fsl,imx7d-gpc and - include/dt-bindings/power/imx8m-power.h for fsl,imx8mq-gpc + include/dt-bindings/power/imx7-power.h for fsl,imx7d-gpc, + include/dt-bindings/power/imx8m-power.h for fsl,imx8mq-gpc, and + include/dt-bindings/power/imx8m-power.h for fsl,imx8mm-gpc - #power-domain-cells: Should be 0
Signature · 1 line
2.20.1
Re: [PATCH V2 4/7] dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
Quoted 4 lines · Adam Ford
The with the recent additions to the driver, the GPCv2 driver can support the i.MX8M Mini, but it needs updated 'compatible' entry to use the proper table.
Quoted 9 lines
This patch adds the i.MX8MM to the compatible list of devices.
Signed-off-by Adam Ford <[email protected]>---
V2: No ChangeDocumentation/devicetree/bindings/power/fsl,imx-gpcv2.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
PATCH v2 5/7 arm64: dts: imx8mm: add GPC power domains
In reply to Adam FordThere is a power domain controller on the i.XM8M Mini used for handling interrupts and controlling certain peripherals like USB OTG and PCIe, which are currently unavailable.
This patch enables support the controller itself to the help facilitate enabling additional peripherals.
---
V2: Removed references making GPC an interrupt controller.
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 78 +++++++++++++++++++++++ 1 file changed, 78 insertions(+)
arch/arm64/boot/dts/freescale/imx8mm.dtsi +78 -0
@@ -4,6 +4,7 @@ */ #include <dt-bindings/clock/imx8mm-clock.h> +#include <dt-bindings/power/imx8m-power.h> #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> #include <dt-bindings/interrupt-controller/arm-gic.h>
@@ -495,6 +496,83 @@ interrupts = <GIC_SPI 89 IRQ_TYPE_LEVEL_HIGH>; #reset-cells = <1>; }; + + gpc: gpc@303a0000 { + compatible = "fsl,imx8mm-gpc"; + reg = <0x303a0000 0x10000>; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 87 IRQ_TYPE_LEVEL_HIGH>; + + pgc { + #address-cells = <1>; + #size-cells = <0>; + + pgc_mipi: power-domain@0 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_MIPI>; + }; + + pgc_pcie: power-domain@1 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_PCIE>; + }; + + pgc_otg1: power-domain@2 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_USB_OTG1>; + }; + + pgc_otg2: power-domain@3 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_USB_OTG2>; + }; + + pgc_ddr1: power-domain@4 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_DDR1>; + }; + + pgc_gpu2d: power-domain@5 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_GPU2D>; + }; + + pgc_gpu: power-domain@6 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_GPU>; + }; + + pgc_vpu: power-domain@7 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_VPU>; + }; + + pgc_gpu3d: power-domain@8 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_GPU3D>; + }; + + pgc_disp: power-domain@9 { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_DOMAIN_DISP>; + }; + + pgc_vpu_g1: power-domain@a { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_VPU_G1>; + }; + + pgc_vpu_g2: power-domain@b { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_VPU_G2>; + }; + + pgc_vpu_h1: power-domain@c { + #power-domain-cells = <0>; + reg = <IMX8MM_POWER_VPU_H1>; + }; + }; + }; }; aips2: bus@30400000 {
Signature · 1 line
2.20.1
PATCH v2 6/7 ARM64: dts: imx8mm: Fix clocks and power domain for USB OTG
In reply to Adam FordThere are two USB OTG controllers on the i.MX8M Mini, but currently neither are functional.
According to the device tree entries published on the NXP kernel for the imx8m mini, these both need to be assigned to the proper clocks and power domain in order to function.
This patch configures both USB OTG controllers to enable a missing clock and define the power domain so boards wishing to enable the USB OTG can do so.
---
V2: No Change
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)
arch/arm64/boot/dts/freescale/imx8mm.dtsi +10 -4
@@ -865,8 +865,11 @@ interrupts = <GIC_SPI 40 IRQ_TYPE_LEVEL_HIGH>; clocks = <&clk IMX8MM_CLK_USB1_CTRL_ROOT>; clock-names = "usb1_ctrl_root_clk"; - assigned-clocks = <&clk IMX8MM_CLK_USB_BUS>; - assigned-clock-parents = <&clk IMX8MM_SYS_PLL2_500M>; + assigned-clocks = <&clk IMX8MM_CLK_USB_BUS>, + <&clk IMX8MM_CLK_USB_CORE_REF>; + assigned-clock-parents = <&clk IMX8MM_SYS_PLL2_500M>, + <&clk IMX8MM_SYS_PLL1_100M>; + power-domains = <&pgc_otg1>; fsl,usbphy = <&usbphynop1>; fsl,usbmisc = <&usbmisc1 0>; status = "disabled";
@@ -884,8 +887,11 @@ interrupts = <GIC_SPI 41 IRQ_TYPE_LEVEL_HIGH>; clocks = <&clk IMX8MM_CLK_USB1_CTRL_ROOT>; clock-names = "usb1_ctrl_root_clk"; - assigned-clocks = <&clk IMX8MM_CLK_USB_BUS>; - assigned-clock-parents = <&clk IMX8MM_SYS_PLL2_500M>; + assigned-clocks = <&clk IMX8MM_CLK_USB_BUS>, + <&clk IMX8MM_CLK_USB_CORE_REF>; + assigned-clock-parents = <&clk IMX8MM_SYS_PLL2_500M>, + <&clk IMX8MM_SYS_PLL1_100M>; + power-domains = <&pgc_otg2>; fsl,usbphy = <&usbphynop2>; fsl,usbmisc = <&usbmisc2 0>; status = "disabled";
Signature · 1 line
2.20.1
PATCH v2 7/7 arm64: dts: imx8mm: Add PCIe support
In reply to Adam FordThe PCIE controller on the i.MX8M Mini appears to be the same as the i.MX8MQ but it is absent.
This patch uses the bindings from the i.MX8MQ and the clock information from the NXP Linux release and marks it as disabled so it can be configured and enabled on boards where needed.
---
V2: No Change
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 35 +++++++++++++++++++++++ 1 file changed, 35 insertions(+)
arch/arm64/boot/dts/freescale/imx8mm.dtsi +35 -0
@@ -5,6 +5,7 @@ #include <dt-bindings/clock/imx8mm-clock.h> #include <dt-bindings/power/imx8m-power.h> +#include <dt-bindings/reset/imx8mq-reset.h> #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> #include <dt-bindings/interrupt-controller/arm-gic.h>
@@ -934,6 +935,40 @@ status = "disabled"; }; + pcie0: pcie@33800000 { + compatible = "fsl,imx8mq-pcie"; + reg = <0x33800000 0x400000>, + <0x1ff00000 0x80000>; + reg-names = "dbi", "config"; + #address-cells = <3>; + #size-cells = <2>; + device_type = "pci"; + bus-range = <0x00 0xff>; + ranges = <0x81000000 0 0x00000000 0x1ff80000 0 0x00010000 /* downstream I/O 64KB */ + 0x82000000 0 0x18000000 0x18000000 0 0x07f00000>; /* non-prefetchable memory */ + num-lanes = <1>; + num-viewport = <4>; + interrupts = <GIC_SPI 122 IRQ_TYPE_LEVEL_HIGH>; + interrupt-names = "msi"; + #interrupt-cells = <1>; + interrupt-map-mask = <0 0 0 0x7>; + interrupt-map = <0 0 0 1 &gic GIC_SPI 125 IRQ_TYPE_LEVEL_HIGH>, + <0 0 0 2 &gic GIC_SPI 124 IRQ_TYPE_LEVEL_HIGH>, + <0 0 0 3 &gic GIC_SPI 123 IRQ_TYPE_LEVEL_HIGH>, + <0 0 0 4 &gic GIC_SPI 122 IRQ_TYPE_LEVEL_HIGH>; + fsl,max-link-speed = <2>; + power-domains = <&pgc_pcie>; + resets = <&src IMX8MQ_RESET_PCIEPHY>, + <&src IMX8MQ_RESET_PCIE_CTRL_APPS_EN>, + <&src IMX8MQ_RESET_PCIE_CTRL_APPS_TURNOFF>; + reset-names = "pciephy", "apps", "turnoff"; + clocks = <&clk IMX8MM_CLK_PCIE1_ROOT>, + <&clk IMX8MM_CLK_PCIE1_AUX>, + <&clk IMX8MM_CLK_PCIE1_PHY>; + clock-names = "pcie", "pcie_bus", "pcie_phy"; + status = "disabled"; + }; + gic: interrupt-controller@38800000 { compatible = "arm,gic-v3"; reg = <0x38800000 0x10000>, /* GIC Dist */
Signature · 1 line
2.20.1
Quoted 8 lines · Adam Ford
The GPCv2 controller on the i.MX8M Mini is compatible with the driver used for the i.MX8MQ except for the register locations and names. The GPCv2 controller is used to enable additional periperals currently unavailable on the i.MX8M Mini. In order to make them function, the GPCv2 needs to be adapted so the drivers can associate their power domain to the GPCv2 to enable them.
Quoted 8 lines
This series makes one include file slightly more generic, adds the iMX8M Mini entries, updates the bindings, adds them to the device tree, then associates the new power domain to both the OTG and PCIe controllers.
Some peripherals may need additional power domain drivers in the future due to limitations of the GPC driver, but the drivers for VPU and others are not available yet.
Before I do a V3 to address Rob's comments, I am thinking I'll drop the items on the GPC that Jacky suggested would not work, and we don't have drivers for those other peripherals (GPU, VPU, etc.) anyway. My main goal here was to try and get the USB OTG ports working, so I'd like to enabled enough of the items on the GPC that are similar to the i.MX8MQ and leave the more challenging items until we have either a better driver available and/or actual peripheral support coming. I haven't seen LCDIF or DSI drivers pushed upstream yet, so I doubt we'll see GPU or VPU yet until those are done.
Does anyone from the NXP team have any other comments/concerns?
adam
Quoted 21 lines
Adam Ford (7):
soc: imx: gpcv2: Renameimx8mq-power.htoimx8m-power.h
soc: imx: gpcv2: Updateimx8m-power.hto include iMX8M Mini
soc: imx: gpcv2: add support for i.MX8M Mini SoC
dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
arm64: dts: imx8mm: add GPC power domains
ARM64: dts: imx8mm: Fix clocks and power domain for USB OTG
arm64: dts: imx8mm: Add PCIe support.../bindings/power/fsl,imx-gpcv2.txt | 6 +- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 127 ++++++++- arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +- drivers/soc/imx/gpcv2.c | 246 +++++++++++++++++- .../power/{imx8mq-power.h => imx8m-power.h} | 14 + 5 files changed, 387 insertions(+), 8 deletions(-) rename include/dt-bindings/power/{imx8mq-power.h => imx8m-power.h} (57%)--
2.20.1
Quoted 42 lines
-----Original Message-----
From: Adam Ford <[email protected]>
Sent: Saturday, December 21, 2019 11:07 PM
To: arm-soc <[email protected]>
Cc: Peng Fan <[email protected]>; Jacky Bai <[email protected]>; Rob Herring <[email protected]>; Mark Rutland <[email protected]>; Shawn Guo <[email protected]>; Sascha Hauer <[email protected]>; Pengutronix Kernel Team <[email protected]>; Fabio Estevam <[email protected]>; dl-linux-imx <[email protected]>; devicetree <[email protected]>; Linux Kernel Mailing List <[email protected]>; Leonard Crestez <[email protected]>
Subject: Re: [PATCH V2 0/7] soc: imx: Enable additional functionality of i.MX8M MiniQuoted 8 lines · Adam Ford
The GPCv2 controller on the i.MX8M Mini is compatible with the driver used for the i.MX8MQ except for the register locations and names. The GPCv2 controller is used to enable additional periperals currently unavailable on the i.MX8M Mini. In order to make them function, the GPCv2 needs to be adapted so the drivers can associate their power domain to the GPCv2 to enable them.
Quoted 8 lines
This series makes one include file slightly more generic, adds the iMX8M Mini entries, updates the bindings, adds them to the device tree, then associates the new power domain to both the OTG and PCIe controllers.
Some peripherals may need additional power domain drivers in the future due to limitations of the GPC driver, but the drivers for VPU and others are not available yet.
Before I do a V3 to address Rob's comments, I am thinking I'll drop the items on the GPC that Jacky suggested would not work, and we don't have drivers for those other peripherals (GPU, VPU, etc.) anyway. My main goal here was to try and get the USB OTG ports working, so I'd like to enabled enough of the items on the GPC that are similar to the i.MX8MQ and leave the more challenging items until we have either a better driver available and/or actual peripheral support coming. I haven't seen LCDIF or DSI drivers pushed upstream yet, so I doubt we'll see GPU or VPU yet until those are done.
Quoted 2 lines
Does anyone from the NXP team have any other comments/concerns?
If you look into NXP's release code, you will find that it is not easy to handle the power domain more generically in GPCv2 driver for imx8mm. That's the reason why we use SIP service to handle all the power domain in TF-A. we tried to upstream the SIP version power domain that can be reused for all i.MX8M, but rejected by ARM guys. they think we need to use SCMI to implement it. as there is no SCMI over SMC available, upstream is on the way, so the power domain for i.MX8MM/MN is pending.
Actually, I am confused why we can't use SIP service, even if the SCMI over SMC is ready in the future, It seems the SMCC function ID still need to choose from SIP service function id bank.
Another concern for adding power domain support in GPCv2 is that, each time a new SOC is added, we need to add hundred lines of code in GPCv2 driver. it is not a best way to keep driver reuse. The GPCv2 driver is originally used for i.MX7D, then reused by i.MX8MQ, as i.MX8MQ has very simple power domain design as i.MX7D. But for i.MX8MM, it is not the case.
There is another concern, we don't want to export GPC module to rich OS side, it is not a must.
BR
Jacky Bai
Quoted 24 lines
adam
Quoted 11 lines
Adam Ford (7):
soc: imx: gpcv2: Renameimx8mq-power.htoimx8m-power.h
soc: imx: gpcv2: Updateimx8m-power.hto include iMX8M Mini
soc: imx: gpcv2: add support for i.MX8M Mini SoC
dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
arm64: dts: imx8mm: add GPC power domains
ARM64: dts: imx8mm: Fix clocks and power domain for USB OTG
arm64: dts: imx8mm: Add PCIe supportQuoted 4 lines
.../bindings/power/fsl,imx-gpcv2.txt | 6 +- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 127 ++++++++- arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +- drivers/soc/imx/gpcv2.c | 246+++++++++++++++++-
Quoted 7 lines
.../power/{imx8mq-power.h => imx8m-power.h} | 14 + 5 files changed, 387 insertions(+), 8 deletions(-) rename
include/dt-bindings/power/{imx8mq-power.h=>imx8m-power.h} (57%)--
2.20.1
Quoted 46 lines · Jacky Bai
Quoted 43 lines
-----Original Message-----
From: Adam Ford <[email protected]>
Sent: Saturday, December 21, 2019 11:07 PM
To: arm-soc <[email protected]>
Cc: Peng Fan <[email protected]>; Jacky Bai <[email protected]>; Rob Herring <[email protected]>; Mark Rutland <[email protected]>; Shawn Guo <[email protected]>; Sascha Hauer <[email protected]>; Pengutronix Kernel Team <[email protected]>; Fabio Estevam <[email protected]>; dl-linux-imx <[email protected]>; devicetree <[email protected]>; Linux Kernel Mailing List <[email protected]>; Leonard Crestez <[email protected]>
Subject: Re: [PATCH V2 0/7] soc: imx: Enable additional functionality of i.MX8M MiniQuoted 8 lines · Adam Ford
The GPCv2 controller on the i.MX8M Mini is compatible with the driver used for the i.MX8MQ except for the register locations and names. The GPCv2 controller is used to enable additional periperals currently unavailable on the i.MX8M Mini. In order to make them function, the GPCv2 needs to be adapted so the drivers can associate their power domain to the GPCv2 to enable them.
Quoted 8 lines
This series makes one include file slightly more generic, adds the iMX8M Mini entries, updates the bindings, adds them to the device tree, then associates the new power domain to both the OTG and PCIe controllers.
Some peripherals may need additional power domain drivers in the future due to limitations of the GPC driver, but the drivers for VPU and others are not available yet.
Before I do a V3 to address Rob's comments, I am thinking I'll drop the items on the GPC that Jacky suggested would not work, and we don't have drivers for those other peripherals (GPU, VPU, etc.) anyway. My main goal here was to try and get the USB OTG ports working, so I'd like to enabled enough of the items on the GPC that are similar to the i.MX8MQ and leave the more challenging items until we have either a better driver available and/or actual peripheral support coming. I haven't seen LCDIF or DSI drivers pushed upstream yet, so I doubt we'll see GPU or VPU yet until those are done.
Quoted 2 lines
Does anyone from the NXP team have any other comments/concerns?
Quoted 7 lines
If you look into NXP's release code, you will find that it is not easy to handle the power domain more generically in GPCv2 driver for imx8mm. That's the reason why we use SIP service to handle all the power domain in TF-A. we tried to upstream the SIP version power domain that can be reused for all i.MX8M, but rejected by ARM guys. they think we need to use SCMI to implement it. as there is no SCMI over SMC available, upstream is on the way, so the power domain for i.MX8MM/MN is pending.
Thank you for the background. I appreciate it.
Quoted 8 lines
Actually, I am confused why we can't use SIP service, even if the SCMI over SMC is ready in the future, It seems the SMCC function ID still need to choose from SIP service function id bank.
Another concern for adding power domain support in GPCv2 is that, each time a new SOC is added, we need to add hundred lines of code in GPCv2 driver. it is not a best way to keep driver reuse. The GPCv2 driver is originally used for i.MX7D, then reused by i.MX8MQ, as i.MX8MQ has very simple power domain design as i.MX7D. But for i.MX8MM, it is not the case.
There are some entries on the 8MM which can be used the same way as the 8MM. I have been able to get USB OTG working using the 8MQ's GPC table.
Until sometime better is available, would you entertain a limited use of the 8MQ's GPC where the device tree nodes only contain a limited number of entries (like USB OTG) where we can re-use the similar functions 8MQ without expanding the driver functions? I know its not ideal, but it would be a temporary solution unless you think the upstream power domain support is coming quickly. I looked through the mailing list history and it looked like there were some attempts about 6 months ago, then it appeared to stop.
Once the newer driver is available upstream, we could then remove GPC references from the 8MM device tree and point it to the new driver.
It would increase some limited functionality for the short term. I know Leonard has been working on the DDRC modifications and power reduction. I have been trying to use them, but unsuccessful so far.
Quoted 2 lines
There is another concern, we don't want to export GPC module to rich OS side, it is not a must.
What about doing it in the U-Boot stage if Linux isn't an option and ATF isn't accepting them?
adam
Quoted 28 lines
BR
Jacky BaiQuoted 24 lines
adam
Quoted 11 lines
Adam Ford (7):
soc: imx: gpcv2: Renameimx8mq-power.htoimx8m-power.h
soc: imx: gpcv2: Updateimx8m-power.hto include iMX8M Mini
soc: imx: gpcv2: add support for i.MX8M Mini SoC
dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
arm64: dts: imx8mm: add GPC power domains
ARM64: dts: imx8mm: Fix clocks and power domain for USB OTG
arm64: dts: imx8mm: Add PCIe supportQuoted 4 lines
.../bindings/power/fsl,imx-gpcv2.txt | 6 +- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 127 ++++++++- arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +- drivers/soc/imx/gpcv2.c | 246+++++++++++++++++-
Quoted 7 lines
.../power/{imx8mq-power.h => imx8m-power.h} | 14 + 5 files changed, 387 insertions(+), 8 deletions(-) rename
include/dt-bindings/power/{imx8mq-power.h=>imx8m-power.h} (57%)--
2.20.1
Quoted 109 lines
-----Original Message-----
From: Adam Ford <[email protected]>
Sent: Sunday, December 22, 2019 10:58 PM
To: Jacky Bai <[email protected]>
Cc: arm-soc <[email protected]>; Peng Fan <[email protected]>; Rob Herring <[email protected]>; Mark Rutland <[email protected]>; Shawn Guo <[email protected]>; Sascha Hauer <[email protected]>; Pengutronix Kernel Team <[email protected]>; Fabio Estevam <[email protected]>; dl-linux-imx <[email protected]>; devicetree <[email protected]>; Linux Kernel Mailing List <[email protected]>; Leonard Crestez <[email protected]>
Subject: Re: [PATCH V2 0/7] soc: imx: Enable additional functionality of i.MX8M MiniQuoted 18 lines · Jacky Bai
Quoted 18 lines
-----Original Message-----
From: Adam Ford <[email protected]>
Sent: Saturday, December 21, 2019 11:07 PM
To: arm-soc <[email protected]>
Cc: Peng Fan <[email protected]>; Jacky Bai <[email protected]>; Rob Herring <[email protected]>; Mark Rutland <[email protected]>; Shawn Guo <[email protected]>; Sascha Hauer <[email protected]>; Pengutronix Kernel Team <[email protected]>; Fabio Estevam <[email protected]>; dl-linux-imx <[email protected]>; devicetree <[email protected]>; Linux Kernel Mailing List <[email protected]>; Leonard Crestez <[email protected]>
Subject: Re: [PATCH V2 0/7] soc: imx: Enable additional functionality of i.MX8M MiniOn Fri, Dec 13, 2019 at 10:05 AM Adam Ford <[email protected]>
Quoted 3 lines · wrote:
Quoted 3 lines
Quoted 3 lines
The GPCv2 controller on the i.MX8M Mini is compatible with the driver used for the i.MX8MQ except for the register locations and
names.
Quoted 15 lines
Quoted 15 lines
Quoted 14 lines
The GPCv2 controller is used to enable additional periperals currently unavailable on the i.MX8M Mini. In order to make them function, the
GPCv2 needs to be adapted so the drivers can associate their power domain to the GPCv2 to enable them.This series makes one include file slightly more generic, adds the iMX8M Mini entries, updates the bindings, adds them to the device tree, then associates the new power domain to both the OTG and PCIe controllers.
Some peripherals may need additional power domain drivers in the future due to limitations of the GPC driver, but the drivers for VPU and others are not available yet.
Quoted 8 lines
Quoted 8 lines
Before I do a V3 to address Rob's comments, I am thinking I'll drop the items on the GPC that Jacky suggested would not work, and we don't have drivers for those other peripherals (GPU, VPU, etc.) anyway. My main goal here was to try and get the USB OTG ports working, so I'd like to enabled enough of the items on the GPC that are similar to the i.MX8MQ and leave the more challenging items until we have either a better driver available and/or actual peripheral support coming. I haven't seen LCDIF or DSI drivers pushed
upstream yet, so I doubt we'll see GPU or VPU yet until those are done.
Quoted 10 lines
Quoted 3 lines
Does anyone from the NXP team have any other comments/concerns?
If you look into NXP's release code, you will find that it is not easy to handle the power domain more generically in GPCv2 driver for imx8mm. That's the reason why we use SIP service to handle all the power domain in TF-A. we tried to upstream the SIP version power domain that can be reused for all i.MX8M, but rejected by ARM guys. they think we need to use SCMI to implement it. as there is no SCMI over
SMC available, upstream is on the way, so the power domain for i.MX8MM/MN is pending.
Quoted 1 line
Thank you for the background. I appreciate it.
Quoted 2 lines
Actually, I am confused why we can't use SIP service, even if the SCMI over SMC is ready in the future, It seems the SMCC function ID still need to
choose from SIP service function id bank.
Quoted 6 lines
Another concern for adding power domain support in GPCv2 is that, each time a new SOC is added, we need to add hundred lines of code in GPCv2 driver. it is not a best way to keep driver reuse. The GPCv2 driver is originally used for i.MX7D, then reused by i.MX8MQ, as i.MX8MQ has very simple power domain design as i.MX7D. But for i.MX8MM, it is not the
case.
There are some entries on the 8MM which can be used the same way as the 8MM. I have been able to get USB OTG working using the 8MQ's GPC table.
Until sometime better is available, would you entertain a limited use of the 8MQ's GPC where the device tree nodes only contain a limited number of entries (like USB OTG) where we can re-use the similar functions 8MQ without expanding the driver functions? I know its not ideal, but it would be a temporary solution unless you think the upstream power domain support is coming quickly. I looked through the mailing list history and it looked like there were some attempts about
6 months ago, then it appeared to stop.Once the newer driver is available upstream, we could then remove GPC references from the 8MM device tree and point it to the new driver.
It would increase some limited functionality for the short term. I know Leonard has been working on the DDRC modifications and power reduction. I have been trying to use them, but unsuccessful so far.
Quoted 1 line
Quoted 5 lines
Quoted 1 line
There is another concern, we don't want to export GPC module to rich OS
side, it is not a must.
What about doing it in the U-Boot stage if Linux isn't an option and ATF isn't accepting them?
I have enabled the USB/PCIE power domain by default early before, if using the community ATF, I think USB can work well.
BR
Jacky Bai
Quoted 30 lines
adam
Quoted 28 lines
BR
Jacky BaiQuoted 24 lines
adam
Quoted 11 lines
Adam Ford (7):
soc: imx: gpcv2: Renameimx8mq-power.htoimx8m-power.h
soc: imx: gpcv2: Updateimx8m-power.hto include iMX8M Mini
soc: imx: gpcv2: add support for i.MX8M Mini SoC
dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
arm64: dts: imx8mm: add GPC power domains
ARM64: dts: imx8mm: Fix clocks and power domain for USB OTG
arm64: dts: imx8mm: Add PCIe supportQuoted 4 lines
.../bindings/power/fsl,imx-gpcv2.txt | 6 +- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 127 ++++++++- arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +- drivers/soc/imx/gpcv2.c | 246+++++++++++++++++-
Quoted 7 lines
.../power/{imx8mq-power.h => imx8m-power.h} | 14 + 5 files changed, 387 insertions(+), 8 deletions(-) rename
include/dt-bindings/power/{imx8mq-power.h=>imx8m-power.h} (57%)--
2.20.1
Quoted 111 lines · Jacky Bai
Quoted 111 lines
-----Original Message-----
From: Adam Ford <[email protected]>
Sent: Sunday, December 22, 2019 10:58 PM
To: Jacky Bai <[email protected]>
Cc: arm-soc <[email protected]>; Peng Fan <[email protected]>; Rob Herring <[email protected]>; Mark Rutland <[email protected]>; Shawn Guo <[email protected]>; Sascha Hauer <[email protected]>; Pengutronix Kernel Team <[email protected]>; Fabio Estevam <[email protected]>; dl-linux-imx <[email protected]>; devicetree <[email protected]>; Linux Kernel Mailing List <[email protected]>; Leonard Crestez <[email protected]>
Subject: Re: [PATCH V2 0/7] soc: imx: Enable additional functionality of i.MX8M MiniQuoted 18 lines · Jacky Bai
Quoted 18 lines
-----Original Message-----
From: Adam Ford <[email protected]>
Sent: Saturday, December 21, 2019 11:07 PM
To: arm-soc <[email protected]>
Cc: Peng Fan <[email protected]>; Jacky Bai <[email protected]>; Rob Herring <[email protected]>; Mark Rutland <[email protected]>; Shawn Guo <[email protected]>; Sascha Hauer <[email protected]>; Pengutronix Kernel Team <[email protected]>; Fabio Estevam <[email protected]>; dl-linux-imx <[email protected]>; devicetree <[email protected]>; Linux Kernel Mailing List <[email protected]>; Leonard Crestez <[email protected]>
Subject: Re: [PATCH V2 0/7] soc: imx: Enable additional functionality of i.MX8M MiniOn Fri, Dec 13, 2019 at 10:05 AM Adam Ford <[email protected]>
Quoted 3 lines · wrote:
Quoted 3 lines
Quoted 3 lines
The GPCv2 controller on the i.MX8M Mini is compatible with the driver used for the i.MX8MQ except for the register locations and
names.
Quoted 15 lines
Quoted 15 lines
Quoted 14 lines
The GPCv2 controller is used to enable additional periperals currently unavailable on the i.MX8M Mini. In order to make them function, the
GPCv2 needs to be adapted so the drivers can associate their power domain to the GPCv2 to enable them.This series makes one include file slightly more generic, adds the iMX8M Mini entries, updates the bindings, adds them to the device tree, then associates the new power domain to both the OTG and PCIe controllers.
Some peripherals may need additional power domain drivers in the future due to limitations of the GPC driver, but the drivers for VPU and others are not available yet.
Quoted 8 lines
Quoted 8 lines
Before I do a V3 to address Rob's comments, I am thinking I'll drop the items on the GPC that Jacky suggested would not work, and we don't have drivers for those other peripherals (GPU, VPU, etc.) anyway. My main goal here was to try and get the USB OTG ports working, so I'd like to enabled enough of the items on the GPC that are similar to the i.MX8MQ and leave the more challenging items until we have either a better driver available and/or actual peripheral support coming. I haven't seen LCDIF or DSI drivers pushed
upstream yet, so I doubt we'll see GPU or VPU yet until those are done.
Quoted 10 lines
Quoted 3 lines
Does anyone from the NXP team have any other comments/concerns?
If you look into NXP's release code, you will find that it is not easy to handle the power domain more generically in GPCv2 driver for imx8mm. That's the reason why we use SIP service to handle all the power domain in TF-A. we tried to upstream the SIP version power domain that can be reused for all i.MX8M, but rejected by ARM guys. they think we need to use SCMI to implement it. as there is no SCMI over
SMC available, upstream is on the way, so the power domain for i.MX8MM/MN is pending.
Quoted 1 line
Thank you for the background. I appreciate it.
Quoted 2 lines
Actually, I am confused why we can't use SIP service, even if the SCMI over SMC is ready in the future, It seems the SMCC function ID still need to
choose from SIP service function id bank.
Quoted 6 lines
Another concern for adding power domain support in GPCv2 is that, each time a new SOC is added, we need to add hundred lines of code in GPCv2 driver. it is not a best way to keep driver reuse. The GPCv2 driver is originally used for i.MX7D, then reused by i.MX8MQ, as i.MX8MQ has very simple power domain design as i.MX7D. But for i.MX8MM, it is not the
case.
There are some entries on the 8MM which can be used the same way as the 8MM. I have been able to get USB OTG working using the 8MQ's GPC table.
Until sometime better is available, would you entertain a limited use of the 8MQ's GPC where the device tree nodes only contain a limited number of entries (like USB OTG) where we can re-use the similar functions 8MQ without expanding the driver functions? I know its not ideal, but it would be a temporary solution unless you think the upstream power domain support is coming quickly. I looked through the mailing list history and it looked like there were some attempts about
6 months ago, then it appeared to stop.Once the newer driver is available upstream, we could then remove GPC references from the 8MM device tree and point it to the new driver.
It would increase some limited functionality for the short term. I know Leonard has been working on the DDRC modifications and power reduction. I have been trying to use them, but unsuccessful so far.
Quoted 2 lines
There is another concern, we don't want to export GPC module to rich OS
Quoted 8 lines
Quoted 4 lines
side, it is not a must.
What about doing it in the U-Boot stage if Linux isn't an option and ATF isn't accepting them?
I have enabled the USB/PCIE power domain by default early before, if using the community ATF, I think USB can work well.
Can you point me to which repo you're using? When I use a stock U-Boot from their repo with the ATF referenced from there, the board hangs when USB is initialized. Ideally, I'd like to get USB working on the mainline Linux with mainline U-Boot.
adam
Quoted 34 lines
BR
Jacky BaiQuoted 30 lines
adam
Quoted 28 lines
BR
Jacky BaiQuoted 24 lines
adam
Quoted 11 lines
Adam Ford (7):
soc: imx: gpcv2: Renameimx8mq-power.htoimx8m-power.h
soc: imx: gpcv2: Updateimx8m-power.hto include iMX8M Mini
soc: imx: gpcv2: add support for i.MX8M Mini SoC
dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
arm64: dts: imx8mm: add GPC power domains
ARM64: dts: imx8mm: Fix clocks and power domain for USB OTG
arm64: dts: imx8mm: Add PCIe supportQuoted 4 lines
.../bindings/power/fsl,imx-gpcv2.txt | 6 +- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 127 ++++++++- arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +- drivers/soc/imx/gpcv2.c | 246+++++++++++++++++-
Quoted 7 lines
.../power/{imx8mq-power.h => imx8m-power.h} | 14 + 5 files changed, 387 insertions(+), 8 deletions(-) rename
include/dt-bindings/power/{imx8mq-power.h=>imx8m-power.h} (57%)--
2.20.1
Hi Jacky,
Quoted 44 lines · Jacky Bai
Quoted 41 lines
-----Original Message-----
From: Adam Ford <[email protected]>
Sent: Saturday, December 21, 2019 11:07 PM
To: arm-soc <[email protected]>
Cc: Peng Fan <[email protected]>; Jacky Bai <[email protected]>; Rob Herring <[email protected]>; Mark Rutland <[email protected]>; Shawn Guo <[email protected]>; Sascha Hauer <[email protected]>; Pengutronix Kernel Team <[email protected]>; Fabio Estevam <[email protected]>; dl-linux-imx <[email protected]>; devicetree <[email protected]>; Linux Kernel Mailing List <[email protected]>; Leonard Crestez <[email protected]>
Subject: Re: [PATCH V2 0/7] soc: imx: Enable additional functionality of i.MX8M MiniQuoted 7 lines · Adam Ford
The GPCv2 controller on the i.MX8M Mini is compatible with the driver used for the i.MX8MQ except for the register locations and names. The GPCv2 controller is used to enable additional periperals currently unavailable on the i.MX8M Mini. In order to make them function, the GPCv2 needs to be adapted so the drivers can associate their power domain to the GPCv2 to enable them.
Quoted 8 lines
This series makes one include file slightly more generic, adds the iMX8M Mini entries, updates the bindings, adds them to the device tree, then associates the new power domain to both the OTG and PCIe controllers.
Some peripherals may need additional power domain drivers in the future due to limitations of the GPC driver, but the drivers for VPU and others are not available yet.
Before I do a V3 to address Rob's comments, I am thinking I'll drop the items on the GPC that Jacky suggested would not work, and we don't have drivers for those other peripherals (GPU, VPU, etc.) anyway. My main goal here was to try and get the USB OTG ports working, so I'd like to enabled enough of the items on the GPC that are similar to the i.MX8MQ and leave the more challenging items until we have either a better driver available and/or actual peripheral support coming. I haven't seen LCDIF or DSI drivers pushed upstream yet, so I doubt we'll see GPU or VPU yet until those are done.
Quoted 2 lines
Does anyone from the NXP team have any other comments/concerns?
Quoted 6 lines
If you look into NXP's release code, you will find that it is not easy to handle the power domain more generically in GPCv2 driver for imx8mm. That's the reason why we use SIP service to handle all the power domain in TF-A. we tried to upstream the SIP version power domain that can be reused for all i.MX8M, but rejected by ARM guys. they think we need to use SCMI to implement it. as there is no SCMI over SMC available, upstream is on the way, so the power domain for i.MX8MM/MN is pending.
Adding power domain support for i.MX8MM/MN to the GPCv2 driver does not prevent a SCMI solution to be used when available. I don't see why we should block this.
Quoted 6 lines
Actually, I am confused why we can't use SIP service, even if the SCMI over SMC is ready in the future, It seems the SMCC function ID still need to choose from SIP service function id bank.
Another concern for adding power domain support in GPCv2 is that, each time a new SOC is added, we need to add hundred lines of code in GPCv2 driver. it is not a best way to keep driver reuse.
This is how all hardware specific stuff is handled in the driver. I see your use-case of having a single TF-A based driver for applications where you have more than on OS running on the system. For the very common case of only a single rich OS running on the system the code reuse doesn't really matter and in fact it's easier to fix any bugs by just updating the Linux kernel.
Quoted 3 lines
The GPCv2 driver is originally used for i.MX7D, then reused by i.MX8MQ,
as i.MX8MQ has very simple power domain design as i.MX7D. But for i.MX8MM, it is not the case.
I would be very interested in the details here. What is the big difference in the i.MX8MM that would make it hard to support it in the GPCv2 driver in the same way as we did with i.MX8MQ?
Quoted 2 lines
There is another concern, we don't want to export GPC module to rich OS side, it is not a must.
You are still free to remove the GPC DT node, as soon as the SCMI replacement is ready.
But if you decide to handle the GPC stuff in TF-A, are you also going to handle the external supplies to the GPC domains in the TF-A? What about synchronous reset clocks that need to be running while the domain is powered up? Are you going to add a SCMI based replacement for the clock controller, which is currently also handled in the rich OS?
Regards,
Lucas
Quoted 26 lines
BR
Jacky BaiQuoted 22 lines
adam
Quoted 9 lines
Adam Ford (7):
soc: imx: gpcv2: Renameimx8mq-power.htoimx8m-power.h
soc: imx: gpcv2: Updateimx8m-power.hto include iMX8M Mini
soc: imx: gpcv2: add support for i.MX8M Mini SoC
dt-bindings: imx-gpcv2: Update bindings to support i.MX8M Mini
arm64: dts: imx8mm: add GPC power domains
ARM64: dts: imx8mm: Fix clocks and power domain for USB OTG
arm64: dts: imx8mm: Add PCIe supportQuoted 4 lines
.../bindings/power/fsl,imx-gpcv2.txt | 6 +- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 127 ++++++++- arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +- drivers/soc/imx/gpcv2.c | 246+++++++++++++++++-
Quoted 7 lines
.../power/{imx8mq-power.h => imx8m-power.h} | 14 + 5 files changed, 387 insertions(+), 8 deletions(-) rename
include/dt-bindings/power/{imx8mq-power.h=>imx8m-power.h} (57%)--
2.20.1