summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2009-01-27 16:12:21 -0500
committerWolfgang Denk <wd@denx.de>2009-01-27 23:42:39 +0100
commitcf7e399fb35b3aea90a27d1df72f45f5d6156204 (patch)
tree63add98351b9cef8c16b0a8f6d293ca3b3db3fdd /include
parent50970839712dda35399e2fa83fe818df9354d618 (diff)
downloadu-boot-imx-cf7e399fb35b3aea90a27d1df72f45f5d6156204.zip
u-boot-imx-cf7e399fb35b3aea90a27d1df72f45f5d6156204.tar.gz
u-boot-imx-cf7e399fb35b3aea90a27d1df72f45f5d6156204.tar.bz2
SATA: do not auto-initialize during boot
Rather than have the board code initialize SATA automatically during boot, make the user manually run "sata init". This brings the SATA subsystem in line with common U-Boot policy. Rather than having a dedicated weak function "is_sata_supported", people can override sata_initialize() to do their weird board stuff. Then they can call the actual __sata_initialize(). Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Diffstat (limited to 'include')
-rw-r--r--include/sata.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/sata.h b/include/sata.h
index 57ee9ac..37573cf 100644
--- a/include/sata.h
+++ b/include/sata.h
@@ -7,5 +7,6 @@ ulong sata_read(int dev, ulong blknr, ulong blkcnt, void *buffer);
ulong sata_write(int dev, ulong blknr, ulong blkcnt, const void *buffer);
int sata_initialize(void);
+int __sata_initialize(void);
#endif