summaryrefslogtreecommitdiff
path: root/include/sha256.h
diff options
context:
space:
mode:
authorRobin Gong <b38343@freescale.com>2013-08-27 14:27:52 +0800
committerRobin Gong <b38343@freescale.com>2013-09-02 10:10:20 +0800
commit14a0649a9611f01a6c8494c38b5d74e867baecc5 (patch)
tree50fc1f72d10649efc709df1ce1a2a132c98575f4 /include/sha256.h
parentc3ea0d8a355a4a5b721e8f20a0e85a36d61f741e (diff)
downloadu-boot-imx-14a0649a9611f01a6c8494c38b5d74e867baecc5.zip
u-boot-imx-14a0649a9611f01a6c8494c38b5d74e867baecc5.tar.gz
u-boot-imx-14a0649a9611f01a6c8494c38b5d74e867baecc5.tar.bz2
ENGR00276023-2: board: freescale: mx6q: add ldo bypass interface on boards
There are three types of board for ldo bypass feature: 1.The board support ldo bypass feature, because of pmic exist. Then implement the full function in the board file. such as mx6qsabresd/mx6slevk 2.The board can't support ldo bypass feature, although pmic still be here. For example: WDOG reset pin and RESET key are not connected with PWRON of pfuze on Sabreauto board, hence at worst case chip can't boot again(reboot failed while system run on 400Mhz, because ROM boot on 800Mhz and the external pmic voltage still be kept @400Mhz). On these board we only implement 1.2G check and increase VDDARM/VDDSOC automatically. Force to ldo-enable mode always. 3.There is no PMIC on the board, hence LDO bypass feature cannot be supported. In this case, ldo_mode_set() is an empty function. Signed-off-by: Robin Gong <b38343@freescale.com>
Diffstat (limited to 'include/sha256.h')
0 files changed, 0 insertions, 0 deletions