[roll] Roll fuchsia [mmc] Check status of HS timing switch using new timing

Previously MMC initialization had been changing the device timing,
issuing SDMMC_SEND_STATUS, then changing the host timing/frequency. This
makes sense for frequency increases, but may not work when decreasing
the frequency, as happens during HS400 initialization. Add special
handling for this case to ensure that the host and the device are using
the same timing.

Original-Bug: 83270
Test: fx test sdmmc-test
Test: Booted Atlas 100 times, didn't see any eMMC errors
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/604187
Original-Revision: 7cb21de184f74ab8ed6f63b873478b6fda71435f
GitOrigin-RevId: ccfe775f7be87cca0a87cf842db879dbdb4345fe
Change-Id: I6065fc0f97da6a0266f892c1dd6e8a34f52c0e56
1 file changed
tree: 1be48bbd7d1516801fe0a0c0aa1a3458ab440e94
  1. infra/
  2. third_party/
  3. firmware
  4. flower
  5. jiri.lock
  6. minimal
  7. prebuilts
  8. README.md
  9. stem
  10. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.