1. 30 Aug, 2018 4 commits
  2. 22 Aug, 2018 1 commit
  3. 15 Aug, 2018 1 commit
  4. 13 Aug, 2018 1 commit
  5. 10 Aug, 2018 8 commits
  6. 03 Aug, 2018 3 commits
  7. 02 Aug, 2018 1 commit
  8. 30 Jul, 2018 1 commit
  9. 26 Jul, 2018 1 commit
  10. 24 Jul, 2018 6 commits
  11. 19 Jul, 2018 1 commit
    • Roberto Vargas's avatar
      cci: Wait before reading status register · ae551a13
      Roberto Vargas authored
      
      
      The functions cci_enable_snoop_dvm_reqs and cci_disable_snoop_dvm_reqs write
      in the SNOOP_CTRL_REGISTER of the slave interface and it polls the status
      register to be sure that the operation is finished before leaving the
      functions. If the write in SNOOP_CTRL_REGISTER is reordered after the first
      read in the status register then these functions can finish before
      enabling/disabling snoops and DVM messages.
      
      The CCI500 TRM specifies:
      
      	Wait for the completion of the write to the Snoop Control Register
      	before testing the change_pending bit.
      
      Change-Id: Idc7685963f412be1c16bcd3c6e3cca826e2fdf38
      Signed-off-by: default avatarRoberto Vargas <roberto.vargas@arm.com>
      ae551a13
  12. 18 Jul, 2018 7 commits
  13. 03 Jul, 2018 1 commit
    • Yann Gautier's avatar
      Add MMC framework · ad71d45e
      Yann Gautier authored
      
      
      This change is largely based on existing eMMC framework by Haojian Zhuang
      (@hzhuang1).
      
      The MMC framework supports both eMMC and SD card devices. It was
      written as a new framework since breaking few eMMC framework APIs.
      
      At card probe and after the reset to idle command (CMD0), a Send
      Interface Condition Command is sent (CMD8) to distinguish between
      eMMC and SD card devices. eMMC devices go through the same
      sequence as in the former eMMC framework. Else the framework
      uses commands dedicated to SD-cards for init or frequency switch.
      
      A structure is created to share info with the driver. It stores:
      - the MMC type (eMMC, SD or SD HC)
      - the device size
      - the max frequency supported by the device
      - the block size: 512 for eMMC and SD-HC and read from CSD
       structure for older SD-cards
      
      Restriction to align buffers on block size has been removed.
      Cache maintenance was removed and is expected to be done in the platform
      or device driver.
      
      The MMC framework includes some MISRA compliance coding style
      maybe not yet ported in the existing eMMC framework.
      
      Fixes ARM-software/tf-issues#597
      Signed-off-by: default avatarYann Gautier <yann.gautier@st.com>
      ad71d45e
  14. 02 Jul, 2018 1 commit
  15. 18 Jun, 2018 1 commit
  16. 14 Jun, 2018 1 commit
    • Roberto Vargas's avatar
      Make TF UUID RFC 4122 compliant · 03364865
      Roberto Vargas authored
      
      
      RFC4122 defines that fields are stored in network order (big endian),
      but TF-A stores them in machine order (little endian by default in TF-A).
      We cannot change the future UUIDs that are already generated, but we can store
      all the bytes using arrays and modify fiptool to generate the UUIDs with
      the correct byte order.
      
      Change-Id: I97be2d3168d91f4dee7ccfafc533ea55ff33e46f
      Signed-off-by: default avatarRoberto Vargas <roberto.vargas@arm.com>
      03364865
  17. 12 Jun, 2018 1 commit
    • Daniel Boulby's avatar
      Fix MISRA Rule 5.3 Part 2 · 896a5902
      Daniel Boulby authored
      
      
      Use a _ prefix for Macro arguments to prevent that argument from
      hiding variables of the same name in the outer scope
      
      Rule 5.3: An identifier declared in an inner scope shall not
                hide an identifier declared in an outer scope
      
      Fixed For:
          make LOG_LEVEL=50 PLAT=fvp
      
      Change-Id: I67b6b05cbad4aeca65ce52981b4679b340604708
      Signed-off-by: default avatarDaniel Boulby <daniel.boulby@arm.com>
      896a5902