Lines Matching full:hs400

497 	 * while HS400 tuning is in progress we end up with mismatched driver  in amd_select_drive_strength()
498 * strengths between the controller and the card. HS400 tuning requires in amd_select_drive_strength()
499 * switching from HS400->DDR52->HS->HS200->HS400. So the driver mismatch in amd_select_drive_strength()
507 * card's timing to HS200 or HS400. The card will use the default driver in amd_select_drive_strength()
528 * The initialization sequence for HS400 is:
529 * HS->HS200->Perform Tuning->HS->HS400
532 * HS400->DDR52->HS->HS200->Perform Tuning->HS->HS400
534 * The AMD eMMC Controller can only use the tuned clock while in HS200 and HS400
537 * HS400, we can re-enable the tuned clock.
562 /* DLL is only required for HS400 */ in amd_set_ios()
632 * b) The HS200 and HS400 driver strengths don't match. in sdhci_acpi_emmc_amd_probe_slot()
634 * A, but the (internal) HS400 preset register has a driver in sdhci_acpi_emmc_amd_probe_slot()
635 * strength of B. As part of initializing HS400, HS200 tuning in sdhci_acpi_emmc_amd_probe_slot()
642 * HS400 preset driver strengths match. in sdhci_acpi_emmc_amd_probe_slot()
644 * Enabling presets for HS400 doesn't work for the following reasons: in sdhci_acpi_emmc_amd_probe_slot()
648 * read out HS400 presets. The AMD controller doesn't support this in sdhci_acpi_emmc_amd_probe_slot()
649 * non-standard register. In fact, it doesn't expose the HS400 in sdhci_acpi_emmc_amd_probe_slot()
653 * Since HS400 and HS200 presets must be identical, we could in sdhci_acpi_emmc_amd_probe_slot()