1. 07 11月, 2017 1 次提交
    • B
      mmc: fsl_esdhc: Fix PIO timeout · bcfb3653
      Benoît Thébaudeau 提交于
      The following error has been observed on i.MX25 with a high-speed SDSC
      card:
          Data Write Failed in PIO Mode.
      
      It was caused by the timeout set on PRSSTAT.BWEN, which was triggered
      because this bit takes 15 ms to be set after writing the first block to
      DATPORT with this card. Without this timeout, all the blocks are
      properly written.
      
      This timeout was implemented by decrementing a variable, so it was
      depending on the CPU frequency. Fix this issue by setting this timeout
      to a long enough absolute duration (500 ms).
      Signed-off-by: NBenoît Thébaudeau <benoit.thebaudeau.dev@gmail.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Fabio Estevam <fabio.estevam@nxp.com>
      Cc: Jaehoon Chung <jh80.chung@samsung.com>
      Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
      Reviewed-by: NJagan Teki <jagan@openedev.com>
      bcfb3653
  2. 06 11月, 2017 3 次提交
  3. 03 11月, 2017 1 次提交
  4. 01 11月, 2017 1 次提交
  5. 31 10月, 2017 1 次提交
    • F
      net: fec_mxc: Change "error frame" message to debug level · 41b93679
      Fabio Estevam 提交于
      As reported by Jonathan Gray:
      
      "After the recent changes to add SimpleNetworkProtocol to efi_loader
      when booting off mmc via an efi payload that doesn't use
      SimpleNetworkProtocol U-Boot's fec_mxc driver will now display
      various "error frame" messages.
      ....
      MMC Device 1 not found
      MMC Device 2 not found
      MMC Device 3 not found
      Scanning disks on sata...
      Found 6 disks
      reading efi/boot/bootarm.efi
      67372 bytes read in 32 ms (2 MiB/s)
      ## Starting EFI application at 12000000 ...
      >> OpenBSD/armv7 BOOTARM 1.0
      error frame: 0x8f57ec40 0x00003d74
      error frame: 0x8f57ec40 0x00007079
      error frame: 0x8f57ec40 0x00006964
      error frame: 0x8f57ec40 0x00006f6f
      error frame: 0x8f57ec40 0x0000726f
      error frame: 0x8f57ec40 0x00002074
      error frame: 0x8f57ec40 0x00006f6f"
      
      Heinrich Schuchardt explains:
      
      "A receive FIFO overrun can be expected if network packages are not
      processed.
      With the network patches we check if a package is available quite often."
      
      Move the "error frame" messages to debug level so that a clean output
      log can be seen.
      Reported-by: NJonathan Gray <jsg@jsg.id.au>
      Suggested-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
      Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
      41b93679
  6. 29 10月, 2017 2 次提交
  7. 27 10月, 2017 8 次提交
  8. 26 10月, 2017 6 次提交
  9. 25 10月, 2017 1 次提交
  10. 24 10月, 2017 3 次提交
  11. 21 10月, 2017 2 次提交
  12. 17 10月, 2017 3 次提交
  13. 16 10月, 2017 6 次提交
  14. 15 10月, 2017 2 次提交