• State
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 59 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM623: eMMC configuration and initialization sequence

Tony Tang
Mastermind 30262 points

Part Number: AM623

I list eMMC dts from all SDK to below table. it was stable/not changing untill SDK11.01.

  sdk8.3 sdk8.04 sdk8.05 sdk8.06 sdk9.0 sdk9.1 sdk9.2.1.9 sdk9.2.1.10 sdk10.00 sdk10.1 sdk11.00 sdk11.01 sdk11.02 sdk12.00
eMMC     sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0xfa10000 0x00 0x260>, <0x00 0xfa18000 0x00 0x134>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        assigned-clocks = <&k3_clks 57 6>;
        assigned-clock-parents = <&k3_clks 57 8>;
        mmc-ddr-1_8v;
        mmc-hs200-1_8v;
        ti,trm-icp = <0x2>;
        bus-width = <8>;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-ddr52 = <0x9>;
        ti,otap-del-sel-hs200 = <0x6>;
    };		         sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0xfa10000 0x00 0x260>, <0x00 0xfa18000 0x00 0x134>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        assigned-clocks = <&k3_clks 57 6>;
        assigned-clock-parents = <&k3_clks 57 8>;
        mmc-ddr-1_8v;
        mmc-hs200-1_8v;
        ti,trm-icp = <0x2>;
        bus-width = <8>;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-ddr52 = <0x5>;
        ti,otap-del-sel-hs200 = <0x5>;
        ti,itap-del-sel-legacy = <0xa>;
        ti,itap-del-sel-mmc-hs = <0x1>;
    };		         sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0x0fa10000 0x00 0x1000>, <0x00 0x0fa18000 0x00 0x400>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        assigned-clocks = <&k3_clks 57 6>;
        assigned-clock-parents = <&k3_clks 57 8>;
        bus-width = <8>;
        mmc-ddr-1_8v;
        mmc-hs200-1_8v;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-ddr52 = <0x5>;
        ti,otap-del-sel-hs200 = <0x5>;
        ti,itap-del-sel-legacy = <0xa>;
        ti,itap-del-sel-mmc-hs = <0x1>;
        status = "disabled";
    };		     sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0x0fa10000 0x00 0x1000>, <0x00 0x0fa18000 0x00 0x400>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        assigned-clocks = <&k3_clks 57 6>;
        assigned-clock-parents = <&k3_clks 57 8>;
        bus-width = <8>;
        mmc-ddr-1_8v;
        mmc-hs200-1_8v;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-ddr52 = <0x5>;
        ti,otap-del-sel-hs200 = <0x5>;
        ti,itap-del-sel-legacy = <0xa>;
        ti,itap-del-sel-mmc-hs = <0x1>;
        status = "disabled";
    };
    sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0x0fa10000 0x00 0x1000>, <0x00 0x0fa18000 0x00 0x400>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        assigned-clocks = <&k3_clks 57 6>;
        assigned-clock-parents = <&k3_clks 57 8>;
        bus-width = <8>;
        mmc-ddr-1_8v;
        mmc-hs200-1_8v;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-ddr52 = <0x5>;
        ti,otap-del-sel-hs200 = <0x5>;
        ti,itap-del-sel-legacy = <0xa>;
        ti,itap-del-sel-mmc-hs = <0x1>;
        status = "disabled";
    };		     sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0x0fa10000 0x00 0x1000>, <0x00 0x0fa18000 0x00 0x400>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        assigned-clocks = <&k3_clks 57 6>;
        assigned-clock-parents = <&k3_clks 57 8>;
        bus-width = <8>;
        mmc-ddr-1_8v;
        mmc-hs200-1_8v;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-hs200 = <0x6>;
        ti,itap-del-sel-legacy = <0x0>;
        ti,itap-del-sel-mmc-hs = <0x0>;
        status = "disabled";
    };		     sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0x0fa10000 0x00 0x1000>, <0x00 0x0fa18000 0x00 0x400>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        bus-width = <8>;
        mmc-ddr-1_8v;
        mmc-hs200-1_8v;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-hs200 = <0x6>;
        ti,itap-del-sel-legacy = <0x0>;
        ti,itap-del-sel-mmc-hs = <0x0>;
        status = "disabled";
    };		     sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0x0fa10000 0x00 0x1000>, <0x00 0x0fa18000 0x00 0x400>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        bus-width = <8>;
        mmc-hs200-1_8v;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-hs200 = <0x6>;
        ti,itap-del-sel-legacy = <0x0>;
        ti,itap-del-sel-mmc-hs = <0x0>;
        status = "disabled";
    };		     sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0x0fa10000 0x00 0x1000>, <0x00 0x0fa18000 0x00 0x400>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        bus-width = <8>;
        mmc-hs200-1_8v;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-hs200 = <0x6>;
        ti,itap-del-sel-legacy = <0x0>;
        ti,itap-del-sel-mmc-hs = <0x0>;
        status = "disabled";
    };		 sdhci0: mmc@fa10000 {
        compatible = "ti,am62-sdhci";
        reg = <0x00 0x0fa10000 0x00 0x1000>, <0x00 0x0fa18000 0x00 0x400>;
        interrupts = <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
        power-domains = <&k3_pds 57 TI_SCI_PD_EXCLUSIVE>;
        clocks = <&k3_clks 57 5>, <&k3_clks 57 6>;
        clock-names = "clk_ahb", "clk_xin";
        bus-width = <8>;
        mmc-hs200-1_8v;
        ti,clkbuf-sel = <0x7>;
        ti,otap-del-sel-legacy = <0x0>;
        ti,otap-del-sel-mmc-hs = <0x0>;
        ti,otap-del-sel-hs200 = <0x6>;
        ti,itap-del-sel-legacy = <0x0>;
        ti,itap-del-sel-mmc-hs = <0x0>;
        status = "disabled";
    };

Questions:

#1.  mmc-ddr-1_8v; is removed until SDK11.01, is it for DDR50 mode?

#2.  The clock items are removed after SDK10.1, what is the impacts as it exists in SDK9.2.

        assigned-clocks = <&k3_clks 57 6>;
        assigned-clock-parents = <&k3_clks 57 8>;

#3.    ti,otap-del-sel-ddr52 = <0x5>; is removed after SDK10.0.  will DDR52 mode be configured during initialization if it exist?

#4. When initialize eMMC, will the driver configure it from low to higher speed one by one according to otap/itap paramter items? or get the highest capability from eMMC, configure to the highest speed in one step?

If customer keeps on old SDK8.3 and SDK9.2, should they change the dts to that of SDK12 to remove mmc-ddr-1_8v, clock item, and  ti,otap-del-sel-ddr52 = <0x5>; will that work?

  • 0
    TI__Guru* 81941 points

    Hello,

    Tony Tang said:
    #1.  mmc-ddr-1_8v; is removed until SDK11.01, is it for DDR50 mode?

    Yes, as per the following commit.

    git.ti.com/.../

    Tony Tang said:
    #2.  The clock items are removed after SDK10.1, what is the impacts as it exists in SDK9.2.

    Please check if the commit message is sufficient

    git.ti.com/.../

    Tony Tang said:
    #3.    ti,otap-del-sel-ddr52 = <0x5>; is removed after SDK10.0.  will DDR52 mode be configured during initialization if it exist?

    No, if there is a higher speed mode available.

    Tony Tang said:
    #4. When initialize eMMC, will the driver configure it from low to higher speed one by one according to otap/itap paramter items? or get the highest capability from eMMC, configure to the highest speed in one step?

    It configures in the highest mode possible by checking the card capabilities and the DTS properties.

    Tony Tang said:
    If customer keeps on old SDK8.3 and SDK9.2, should they change the dts to that of SDK12 to remove mmc-ddr-1_8v, clock item, and  ti,otap-del-sel-ddr52 = <0x5>; will that work?

    I am not sure about the clock changes but removing the DDR50 related properties should not cause issues.

  • 0 in reply to Prashant Shivhare
    TI__Mastermind 30262 points
    Prashant Shivhare said:
    It configures in the highest mode possible by checking the card capabilities and the DTS properties.

    If the eMMC supports HS200, no matter mmc-ddr-1_8v and ti,otap-del-sel-ddr52 = <0x5>;exist or not, it won't matter. and won't have 50MHz eMMC_CLK stage before entering HS200 mode?

    BTW, what is the mode configured by ROM code stage? is it 25MHz legacy SDR mode?

  • 0 in reply to Tony Tang
    TI__Guru* 81941 points
    Tony Tang said:
    and won't have 50MHz eMMC_CLK stage before entering HS200 mode?

    The eMMC HS200 initialization sequence doesn't involve the DDR50 speed mode.

    Tony Tang said:
    BTW, what is the mode configured by ROM code stage? is it 25MHz legacy SDR mode?

    I will have to check.