sunxi: extend R528/T113-s3/D1(s) DRAM initialisation
PATCH 1/1 sunxi: extend R528/T113-s3/D1(s) DRAM initialisation
Extend the DRAM initialisation code to add support for the T113-S4 aka T113M4020DC0 by checking the SoC's CHIPID.
--- drivers/ram/sunxi/dram_sun20i_d1.c | 13 ++++++++++++- drivers/ram/sunxi/dram_sun20i_d1.h | 7 +++++++ 2 files changed, 19 insertions(+), 1 deletion(-)
drivers/ram/sunxi/dram_sun20i_d1.c +12 -1
@@ -54,6 +54,11 @@ static void sid_read_ldoB_cal(const dram_para_t *para)clrsetbits_le32 (0x3000150 ,0xff00 , reg <<8 ); } +static u32 sid_read_soc_chipid (void ) +{ +return readl (SUNXI_SID_BASE +0x00 ) &0xffff ; +} +static void dram_voltage_set (const dram_para_t *para) {int vol;
@@ -663,6 +668,7 @@ static void mctl_phy_ac_remapping(const dram_para_t *para, fuse = (readl (SUNXI_SID_BASE +0x28 ) &0xf00 ) >>8 ;debug ("DDR efuse: 0x%x\n" , fuse); +debug ("SoC Chip ID: 0x%08x\n" ,sid_read_soc_chipid ());if (para->dram_type ==SUNXI_DRAM_TYPE_DDR2 ) {if (fuse ==15 )
@@ -675,7 +681,12 @@ static void mctl_phy_ac_remapping(const dram_para_t *para,switch (fuse) {case 8 : cfg = ac_remapping_tables[2 ];break ;case 9 : cfg = ac_remapping_tables[3 ];break ; -case 10 : cfg = ac_remapping_tables[5 ];break ; +case 10 : +if (sid_read_soc_chipid () ==SUNXI_CHIPID_T113M4020DC0 ) + cfg = ac_remapping_tables[0 ]; +else + cfg = ac_remapping_tables[5 ]; +break ;case 11 : cfg = ac_remapping_tables[4 ];break ;default :case 12 : cfg = ac_remapping_tables[1 ];break ;
drivers/ram/sunxi/dram_sun20i_d1.h +7 -0
@@ -19,6 +19,13 @@ enum sunxi_dram_type { SUNXI_DRAM_TYPE_LPDDR3 = 7, }; +enum sunxi_soc_chipid { +SUNXI_CHIPID_F133A =0x5C00 , +SUNXI_CHIPID_D1S =0x5E00 , +SUNXI_CHIPID_T113S3 =0x6000 , +SUNXI_CHIPID_T113M4020DC0 =0x7200 , +}; +/* * This structure contains a mixture of fixed configuration settings, * variables that are used at runtime to communicate settings between
Signature · 1 line
2.39.5
On Sun, 14 Sep 2025 16:44:11 +0200
Lukas Schmid <[email protected]> wrote:
Hi Lukas,
thanks for the patch!
CC:ing the sunxi list and András, who I think has some T113-s4 device as well.
It would be good to see some Tested-by: tags, but otherwise the patch looks good, I'd say.
Also I hear that awboot uses 0x6800 as the chip ID for the -s4, can someone shed some light on this?
Cheers,
Andre
Quoted 65 lines
Extend the DRAM initialisation code to add support for the T113-S4 aka T113M4020DC0 by checking the SoC's CHIPID.
Signed-off-by Lukas Schmid <[email protected]>--- drivers/ram/sunxi/dram_sun20i_d1.c | 13 ++++++++++++- drivers/ram/sunxi/dram_sun20i_d1.h | 7 +++++++ 2 files changed, 19 insertions(+), 1 deletion(-)drivers/ram/sunxi/dram_sun20i_d1.c +12
-1@@ -54,6 +54,11 @@ static void sid_read_ldoB_cal(const dram_para_t *para)clrsetbits_le32 (0x3000150 ,0xff00 , reg <<8 ); } +static u32 sid_read_soc_chipid (void ) +{ +return readl (SUNXI_SID_BASE +0x00 ) &0xffff ; +} +static void dram_voltage_set (const dram_para_t *para) {int vol;@@ -663,6 +668,7 @@ static void mctl_phy_ac_remapping(const dram_para_t *para, fuse = (readl (SUNXI_SID_BASE +0x28 ) &0xf00 ) >>8 ;debug ("DDR efuse: 0x%x\n" , fuse); +debug ("SoC Chip ID: 0x%08x\n" ,sid_read_soc_chipid ());if (para->dram_type ==SUNXI_DRAM_TYPE_DDR2 ) {if (fuse ==15 )@@ -675,7 +681,12 @@ static void mctl_phy_ac_remapping(const dram_para_t *para,switch (fuse) {case 8 : cfg = ac_remapping_tables[2 ];break ;case 9 : cfg = ac_remapping_tables[3 ];break ; -case 10 : cfg = ac_remapping_tables[5 ];break ; +case 10 : +if (sid_read_soc_chipid () ==SUNXI_CHIPID_T113M4020DC0 ) + cfg = ac_remapping_tables[0 ]; +else + cfg = ac_remapping_tables[5 ]; +break ;case 11 : cfg = ac_remapping_tables[4 ];break ;default :case 12 : cfg = ac_remapping_tables[1 ];break ;drivers/ram/sunxi/dram_sun20i_d1.h +7
-0@@ -19,6 +19,13 @@ enum sunxi_dram_type { SUNXI_DRAM_TYPE_LPDDR3 = 7, }; +enum sunxi_soc_chipid { +SUNXI_CHIPID_F133A =0x5C00 , +SUNXI_CHIPID_D1S =0x5E00 , +SUNXI_CHIPID_T113S3 =0x6000 , +SUNXI_CHIPID_T113M4020DC0 =0x7200 , +}; +/* * This structure contains a mixture of fixed configuration settings, * variables that are used at runtime to communicate settings between
Dne ponedeljek, 15. september 2025 ob 17:36:37 Srednjeevropski poletni čas je Andre Przywara napisal(a):
Quoted 50 lines
On Sun, 14 Sep 2025 16:44:11 +0200
Lukas Schmid <[email protected]> wrote:Hi Lukas,
thanks for the patch!
CC:ing the sunxi list and András, who I think has some T113-s4 device as well.
It would be good to see some Tested-by: tags, but otherwise the patch looks good, I'd say.
Also I hear that awboot uses
0x6800as the chip ID for the -s4, can someone shed some light on this?Cheers,
AndreQuoted 31 lines
Extend the DRAM initialisation code to add support for the T113-S4 aka T113M4020DC0 by checking the SoC's CHIPID.
Signed-off-by Lukas Schmid <[email protected]>--- drivers/ram/sunxi/dram_sun20i_d1.c | 13 ++++++++++++- drivers/ram/sunxi/dram_sun20i_d1.h | 7 +++++++ 2 files changed, 19 insertions(+), 1 deletion(-)drivers/ram/sunxi/dram_sun20i_d1.c +6
-0@@ -54,6 +54,11 @@ static void sid_read_ldoB_cal(const dram_para_t *para)clrsetbits_le32 (0x3000150 ,0xff00 , reg <<8 ); } +static u32 sid_read_soc_chipid (void ) +{ +return readl (SUNXI_SID_BASE +0x00 ) &0xffff ; +} +static void dram_voltage_set (const dram_para_t *para) {int vol;@@ -663,6 +668,7 @@ static void mctl_phy_ac_remapping(const dram_para_t *para, fuse = (readl (SUNXI_SID_BASE +0x28 ) &0xf00 ) >>8 ;debug ("DDR efuse: 0x%x\n" , fuse); +debug ("SoC Chip ID: 0x%08x\n" ,sid_read_soc_chipid ());
Quoted 13 lines
drivers/ram/sunxi/dram_sun20i_d1.c static void mctl_phy_ac_remapping(const dram_para_t *para, · line 689
Quoted 13 lines
drivers/ram/sunxi/dram_sun20i_d1.c +6
-1if (para->dram_type ==SUNXI_DRAM_TYPE_DDR2 ) {if (fuse ==15 )@@ -675,7 +681,12 @@ static void mctl_phy_ac_remapping(const dram_para_t *para,switch (fuse) {case 8 : cfg = ac_remapping_tables[2 ];break ;case 9 : cfg = ac_remapping_tables[3 ];break ; -case 10 : cfg = ac_remapping_tables[5 ];break ; +case 10 : +if (sid_read_soc_chipid () ==SUNXI_CHIPID_T113M4020DC0 ) + cfg = ac_remapping_tables[0 ]; +else + cfg = ac_remapping_tables[5 ]; +break ;
This is similar thing to what has been done in H616 DRAM driver, so FWIW:
Best regards,
Jernej
Quoted 24 lines
Quoted 21 lines
drivers/ram/sunxi/dram_sun20i_d1.c +0
-0case 11 : cfg = ac_remapping_tables[4 ];break ;default :case 12 : cfg = ac_remapping_tables[1 ];break ;drivers/ram/sunxi/dram_sun20i_d1.h +7
-0@@ -19,6 +19,13 @@ enum sunxi_dram_type { SUNXI_DRAM_TYPE_LPDDR3 = 7, }; +enum sunxi_soc_chipid { +SUNXI_CHIPID_F133A =0x5C00 , +SUNXI_CHIPID_D1S =0x5E00 , +SUNXI_CHIPID_T113S3 =0x6000 , +SUNXI_CHIPID_T113M4020DC0 =0x7200 , +}; +/* * This structure contains a mixture of fixed configuration settings, * variables that are used at runtime to communicate settings between
Quoted 7 lines · Andre Przywara
On Sun, 14 Sep 2025 16:44:11 +0200
Lukas Schmid <[email protected]> wrote:
Quoted 7 lines
Hi Lukas,
thanks for the patch!
CC:ing the sunxi list and András, who I think has some T113-s4 device as well.
Thanks, but unfortunately I don’t have a board with T113-S4. So awboot was not tested with this SoC, at least by me.
Quoted 75 lines
It would be good to see some Tested-by: tags, but otherwise the patch looks good, I'd say.
Also I hear that awboot uses
0x6800as the chip ID for the -s4, can someone shed some light on this?Cheers,
AndreQuoted 65 lines
Extend the DRAM initialisation code to add support for the T113-S4 aka T113M4020DC0 by checking the SoC's CHIPID.
Signed-off-by Lukas Schmid <[email protected]>---
drivers/ram/sunxi/dram_sun20i_d1.c| 13 ++++++++++++-drivers/ram/sunxi/dram_sun20i_d1.h| 7 +++++++2 files changed, 19 insertions(+), 1 deletion(-)drivers/ram/sunxi/dram_sun20i_d1.c +12
-1@@ -54,6 +54,11 @@ static void sid_read_ldoB_cal(const dram_para_t *para)clrsetbits_le32 (0x3000150 ,0xff00 , reg <<8 ); } +static u32 sid_read_soc_chipid (void ) +{ +return readl (SUNXI_SID_BASE +0x00 ) &0xffff ; +} +static void dram_voltage_set (const dram_para_t *para) {int vol;@@ -663,6 +668,7 @@ static void mctl_phy_ac_remapping(const dram_para_t *para, fuse = (readl (SUNXI_SID_BASE +0x28 ) &0xf00 ) >>8 ;debug ("DDR efuse: 0x%x\n" , fuse); +debug ("SoC Chip ID: 0x%08x\n" ,sid_read_soc_chipid ());if (para->dram_type ==SUNXI_DRAM_TYPE_DDR2 ) {if (fuse ==15 )@@ -675,7 +681,12 @@ static void mctl_phy_ac_remapping(const dram_para_t *para,switch (fuse) {case 8 : cfg = ac_remapping_tables[2 ];break ;case 9 : cfg = ac_remapping_tables[3 ];break ; -case 10 : cfg = ac_remapping_tables[5 ];break ; +case 10 : +if (sid_read_soc_chipid () ==SUNXI_CHIPID_T113M4020DC0 ) + cfg = ac_remapping_tables[0 ]; +else + cfg = ac_remapping_tables[5 ]; +break ;case 11 : cfg = ac_remapping_tables[4 ];break ;default:
case 12: cfg = ac_remapping_tables[1]; break;drivers/ram/sunxi/dram_sun20i_d1.h +7
-0@@ -19,6 +19,13 @@ enum sunxi_dram_type { SUNXI_DRAM_TYPE_LPDDR3 = 7, }; +enum sunxi_soc_chipid { +SUNXI_CHIPID_F133A =0x5C00 , +SUNXI_CHIPID_D1S =0x5E00 , +SUNXI_CHIPID_T113S3 =0x6000 , +SUNXI_CHIPID_T113M4020DC0 =0x7200 , +}; +/* * This structure contains a mixture of fixed configuration settings, * variables that are used at runtime to communicate settings between
On Tue, 16 Sep 2025 15:35:42 +0200
András Szemző <[email protected]> wrote:
Hi András,
many thanks for the reply!
Quoted 7 lines
Quoted 7 lines · Andre Przywara
On Sun, 14 Sep 2025 16:44:11 +0200
Lukas Schmid <[email protected]> wrote:Hi Lukas,
Quoted 8 lines
Quoted 5 lines
thanks for the patch!
CC:ing the sunxi list and András, who I think has some T113-s4 device as well.
Thanks, but unfortunately I don’t have a board with T113-S4. So awboot was not tested with this SoC, at least by me.
Ah, I see, thanks for the confirmation anyway!
I guess we will stick to the chip ID we have seen for now, and wait till people complain.
Thanks,
Andre
Quoted 76 lines
Quoted 75 lines
It would be good to see some Tested-by: tags, but otherwise the patch looks good, I'd say.
Also I hear that awboot uses
0x6800as the chip ID for the -s4, can someone shed some light on this?Cheers,
AndreQuoted 65 lines
Extend the DRAM initialisation code to add support for the T113-S4 aka T113M4020DC0 by checking the SoC's CHIPID.
Signed-off-by Lukas Schmid <[email protected]>---
drivers/ram/sunxi/dram_sun20i_d1.c| 13 ++++++++++++-drivers/ram/sunxi/dram_sun20i_d1.h| 7 +++++++2 files changed, 19 insertions(+), 1 deletion(-)drivers/ram/sunxi/dram_sun20i_d1.c +12
-1@@ -54,6 +54,11 @@ static void sid_read_ldoB_cal(const dram_para_t *para)clrsetbits_le32 (0x3000150 ,0xff00 , reg <<8 ); } +static u32 sid_read_soc_chipid (void ) +{ +return readl (SUNXI_SID_BASE +0x00 ) &0xffff ; +} +static void dram_voltage_set (const dram_para_t *para) {int vol;@@ -663,6 +668,7 @@ static void mctl_phy_ac_remapping(const dram_para_t *para, fuse = (readl (SUNXI_SID_BASE +0x28 ) &0xf00 ) >>8 ;debug ("DDR efuse: 0x%x\n" , fuse); +debug ("SoC Chip ID: 0x%08x\n" ,sid_read_soc_chipid ());if (para->dram_type ==SUNXI_DRAM_TYPE_DDR2 ) {if (fuse ==15 )@@ -675,7 +681,12 @@ static void mctl_phy_ac_remapping(const dram_para_t *para,switch (fuse) {case 8 : cfg = ac_remapping_tables[2 ];break ;case 9 : cfg = ac_remapping_tables[3 ];break ; -case 10 : cfg = ac_remapping_tables[5 ];break ; +case 10 : +if (sid_read_soc_chipid () ==SUNXI_CHIPID_T113M4020DC0 ) + cfg = ac_remapping_tables[0 ]; +else + cfg = ac_remapping_tables[5 ]; +break ;case 11 : cfg = ac_remapping_tables[4 ];break ;default:
case 12: cfg = ac_remapping_tables[1]; break;drivers/ram/sunxi/dram_sun20i_d1.h +7
-0@@ -19,6 +19,13 @@ enum sunxi_dram_type { SUNXI_DRAM_TYPE_LPDDR3 = 7, }; +enum sunxi_soc_chipid { +SUNXI_CHIPID_F133A =0x5C00 , +SUNXI_CHIPID_D1S =0x5E00 , +SUNXI_CHIPID_T113S3 =0x6000 , +SUNXI_CHIPID_T113M4020DC0 =0x7200 , +}; +/* * This structure contains a mixture of fixed configuration settings, * variables that are used at runtime to communicate settings between
Quoted 2 lines · Lukas Schmid
Extend the DRAM initialisation code to add support for the T113-S4 aka T113M4020DC0 by checking the SoC's CHIPID.
Hi there, I've tested this patch and confirm that it is required to boot my T113-S4 from an EmbedSky dev kit. Here is the product:
http://wiki.armbbs.net/tqwiki/public/docs/TQT113_CORE
I can confirm this board does not boot without this patch.
Here's a Tested-by and Reviewed-By:
That said there are some things I would like to see improved in this patch.
Quoted 12 lines
Signed-off-by Lukas Schmid <[email protected]>--- drivers/ram/sunxi/dram_sun20i_d1.c | 13 ++++++++++++- drivers/ram/sunxi/dram_sun20i_d1.h | 7 +++++++ 2 files changed, 19 insertions(+), 1 deletion(-)drivers/ram/sunxi/dram_sun20i_d1.c +0
-0
drivers/ram/sunxi/dram_sun20i_d1.c static void sid_read_ldoB_cal(const dram_para_t *para) · line 61
Quoted 8 lines
drivers/ram/sunxi/dram_sun20i_d1.c +5
-0@@ -54,6 +54,11 @@ static void sid_read_ldoB_cal(const dram_para_t *para)clrsetbits_le32 (0x3000150 ,0xff00 , reg <<8 ); } +static u32 sid_read_soc_chipid (void ) +{ +return readl (SUNXI_SID_BASE +0x00 ) &0xffff ; +} +
mctl_phy_ac_remapping uses readl to read a fuse and labels that as uint32_t, maybe this should be uint32_t too?
The other question I have is how did you figure out this register and mask? Is it documented somewhere? I would love to see a comment or note in the Git commit saying where these values came from, even if it's just 'taken from sunxi-fel' or 'heard from apritzel'. Having notes like that can really help when troubleshooting old code, which hopefully this will be one day.
I found something that seems to agree from the Tina device tree:
sid@3006000 {
compatible = "allwinner,sun20iw1p1-sid", "allwinner,sunxi-sid";
reg = <0x0 0x03006000 0 0x1000>;
#address-cells = <1>;
#size-cells = <1>;
chipid {
reg = <0x0 0>;
offset = <0x200>;
size = <0x10>;
};Quoted 30 lines
drivers/ram/sunxi/dram_sun20i_d1.c +7
-1static void dram_voltage_set (const dram_para_t *para) {int vol;@@ -663,6 +668,7 @@ static void mctl_phy_ac_remapping(const dram_para_t *para, fuse = (readl (SUNXI_SID_BASE +0x28 ) &0xf00 ) >>8 ;debug ("DDR efuse: 0x%x\n" , fuse); +debug ("SoC Chip ID: 0x%08x\n" ,sid_read_soc_chipid ());if (para->dram_type ==SUNXI_DRAM_TYPE_DDR2 ) {if (fuse ==15 )@@ -675,7 +681,12 @@ static void mctl_phy_ac_remapping(const dram_para_t *para,switch (fuse) {case 8 : cfg = ac_remapping_tables[2 ];break ;case 9 : cfg = ac_remapping_tables[3 ];break ; -case 10 : cfg = ac_remapping_tables[5 ];break ; +case 10 : +if (sid_read_soc_chipid () ==SUNXI_CHIPID_T113M4020DC0 ) + cfg = ac_remapping_tables[0 ]; +else + cfg = ac_remapping_tables[5 ]; +break ;case 11 : cfg = ac_remapping_tables[4 ];break ;default :case 12 : cfg = ac_remapping_tables[1 ];break ;drivers/ram/sunxi/dram_sun20i_d1.h +0
-0
drivers/ram/sunxi/dram_sun20i_d1.h enum sunxi_dram_type { · line 28
Quoted 10 lines
drivers/ram/sunxi/dram_sun20i_d1.h +7
-0@@ -19,6 +19,13 @@ enum sunxi_dram_type { SUNXI_DRAM_TYPE_LPDDR3 = 7, }; +enum sunxi_soc_chipid { +SUNXI_CHIPID_F133A =0x5C00 , +SUNXI_CHIPID_D1S =0x5E00 , +SUNXI_CHIPID_T113S3 =0x6000 , +SUNXI_CHIPID_T113M4020DC0 =0x7200 , +}; +
Same question as previous: Where do these values come from? Could this be documented? I can't find these values anywhere else. Noting this down would help if someone wants to use them as reference to if they turn out to be wrong. Speaking of...
awboot seems to believe the T113S4 chip ID is 0x6800:
https://github.com/szemzoa/awboot/blob/main/arch/arm32/mach-t113s4/dram.c#L726
if(chipid == 0x6800){ // 0x6800 is T113-S4 no remap
cfg = ac_remapping_tables[0];
} else {
cfg = ac_remapping_tables[5];
}Perhaps theirs is for the M4030DC0 or something?
Quoted 7 lines
drivers/ram/sunxi/dram_sun20i_d1.h +0
-0/* * This structure contains a mixture of fixed configuration settings, * variables that are used at runtime to communicate settings between Signature · 1 line
2.39.5
John.
On Tue, 16 Sep 2025 02:22:05 +1000
John Watts <[email protected]> wrote:
Hi John,
just one part that wasn't commented on yet:
Quoted 102 lines · Lukas Schmid
Quoted 2 lines
Extend the DRAM initialisation code to add support for the T113-S4 aka T113M4020DC0 by checking the SoC's CHIPID.
Hi there, I've tested this patch and confirm that it is required to boot my T113-S4 from an EmbedSky dev kit. Here is the product:
http://wiki.armbbs.net/tqwiki/public/docs/TQT113_CORE
I can confirm this board does not boot without this patch.Here's a Tested-by and Reviewed-By:
Tested-by John Watts <[email protected]>Reviewed-by John Watts <[email protected]>Quoted 12 lines
Signed-off-by Lukas Schmid <[email protected]>--- drivers/ram/sunxi/dram_sun20i_d1.c | 13 ++++++++++++- drivers/ram/sunxi/dram_sun20i_d1.h | 7 +++++++ 2 files changed, 19 insertions(+), 1 deletion(-)drivers/ram/sunxi/dram_sun20i_d1.c +0
-0drivers/ram/sunxi/dram_sun20i_d1.c static void sid_read_ldoB_cal(const dram_para_t *para) · line 61
Quoted 8 lines
drivers/ram/sunxi/dram_sun20i_d1.c +5
-0@@ -54,6 +54,11 @@ static void sid_read_ldoB_cal(const dram_para_t *para)clrsetbits_le32 (0x3000150 ,0xff00 , reg <<8 ); } +static u32 sid_read_soc_chipid (void ) +{ +return readl (SUNXI_SID_BASE +0x00 ) &0xffff ; +} +
mctl_phy_ac_remappinguses readl to read a fuse and labels that asuint32_t, maybe this should beuint32_ttoo?
The other question I have is how did you figure out this register and mask? it documented somewhere? I would love to see a comment or note in the Git commit saying where these values came from, even if it's just 'taken from sunxi-fel' or 'heard from apritzel'. Having notes like that can really help when troubleshooting old code, which hopefully this will be one day.I found something that seems to agree from the Tina device tree:
sid@3006000 { compatible = "allwinner,sun20iw1p1-sid", "allwinner,sunxi-sid"; reg = <0x0 0x03006000 0 0x1000>; #address-cells = <1>; #size-cells = <1>; chipid { reg = <0x0 0>; offset = <0x200>; size = <0x10>; };Quoted 30 lines
drivers/ram/sunxi/dram_sun20i_d1.c +7
-1static void dram_voltage_set (const dram_para_t *para) {int vol;@@ -663,6 +668,7 @@ static void mctl_phy_ac_remapping(const dram_para_t *para, fuse = (readl (SUNXI_SID_BASE +0x28 ) &0xf00 ) >>8 ;debug ("DDR efuse: 0x%x\n" , fuse); +debug ("SoC Chip ID: 0x%08x\n" ,sid_read_soc_chipid ());if (para->dram_type ==SUNXI_DRAM_TYPE_DDR2 ) {if (fuse ==15 )@@ -675,7 +681,12 @@ static void mctl_phy_ac_remapping(const dram_para_t *para,switch (fuse) {case 8 : cfg = ac_remapping_tables[2 ];break ;case 9 : cfg = ac_remapping_tables[3 ];break ; -case 10 : cfg = ac_remapping_tables[5 ];break ; +case 10 : +if (sid_read_soc_chipid () ==SUNXI_CHIPID_T113M4020DC0 ) + cfg = ac_remapping_tables[0 ]; +else + cfg = ac_remapping_tables[5 ]; +break ;case 11 : cfg = ac_remapping_tables[4 ];break ;default :case 12 : cfg = ac_remapping_tables[1 ];break ;drivers/ram/sunxi/dram_sun20i_d1.h +0
-0drivers/ram/sunxi/dram_sun20i_d1.h enum sunxi_dram_type { · line 28
Quoted 10 lines
drivers/ram/sunxi/dram_sun20i_d1.h +7
-0@@ -19,6 +19,13 @@ enum sunxi_dram_type { SUNXI_DRAM_TYPE_LPDDR3 = 7, }; +enum sunxi_soc_chipid { +SUNXI_CHIPID_F133A =0x5C00 , +SUNXI_CHIPID_D1S =0x5E00 , +SUNXI_CHIPID_T113S3 =0x6000 , +SUNXI_CHIPID_T113M4020DC0 =0x7200 , +}; +Same question as previous: Where do these values come from? Could this be documented? I can't find these values anywhere else. Noting this down would help if someone wants to use them as reference to if they turn out to be wrong. Speaking of...
Quoted 4 lines
awboot seems to believe the T113S4 chip ID is
0x6800:
https://github.com/szemzoa/awboot/blob/main/arch/arm32/mach-t113s4/dram.c#L726if(chipid == 0x6800){ // 0x6800 is T113-S4 no remap
As András mentioned in another email, he did not test the T113-S4 with awboot. So far I have seen two confirmations that 0x7200 works, and no negative complaints, so I would like to go with 0x7200. If people run into problems with their board later, I am more than happy to add any other number to that check.
Cheers,
Andre
Quoted 16 lines
cfg = ac_remapping_tables[0]; } else { cfg = ac_remapping_tables[5]; }Perhaps theirs is for the M4030DC0 or something?
Quoted 7 lines
drivers/ram/sunxi/dram_sun20i_d1.h +0
-0/* * This structure contains a mixture of fixed configuration settings, * variables that are used at runtime to communicate settings between Signature · 1 line
2.39.5John.