summaryrefslogtreecommitdiff
path: root/board/v38b/v38b.c
diff options
context:
space:
mode:
authorPeng Fan <van.freenix@gmail.com>2016-06-15 02:53:02 (GMT)
committerYork Sun <york.sun@nxp.com>2016-06-28 19:08:53 (GMT)
commit1483151e84161449c3f652a751a04e06b0723bff (patch)
treee51ba2518e0dfb3e457e1f1029870bf37d78429f /board/v38b/v38b.c
parent84ecdf6da9eb102b2de87d5912d1554f44d33237 (diff)
downloadu-boot-1483151e84161449c3f652a751a04e06b0723bff.tar.xz
mmc: fsl: introduce wp_enable
Introudce wp_enable. To check WPSPL, wp_enable needs to be set to 1 in board code. Take i.MX6UL for example, for some boards, they do not use WP singal, so they does not configure USDHC1_WP_SELECT_INPUT, and its default value is 0(GPIO1_IO02). However GPIO1_IO02 is muxed for i2c usage and SION bit set. So USDHC controller can always get wp signal and WPSPL shows write protect and blocks driver continuing. This is not what we want to see, so add wp_enable, and if set to 0, just omit the WPSPL checking and this does not effect normal working of usdhc controller. If wp-gpios is provided in dts, wp_enable is set to 1, otherwise 0. Signed-off-by: Peng Fan <van.freenix@gmail.com> Cc: Pantelis Antoniou <panto@antoniou-consulting.com> Cc: York Sun <york.sun@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Tested-by: Fabio Estevam <fabio.estevam@nxp.com> Reviewed-by: York Sun <york.sun@nxp.com>
Diffstat (limited to 'board/v38b/v38b.c')
0 files changed, 0 insertions, 0 deletions