summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/README.x862
-rw-r--r--doc/device-tree-bindings/misc/intel,baytrail-fsp.txt31
2 files changed, 31 insertions, 2 deletions
diff --git a/doc/README.x86 b/doc/README.x86
index 36aaef0..6d9cb10 100644
--- a/doc/README.x86
+++ b/doc/README.x86
@@ -706,7 +706,7 @@ the board, then you can use post_code() calls from C or assembler to monitor
boot progress. This can be good for debugging.
If not, you can try to get serial working as early as possible. The early
-debug serial port may be useful here. See setup_early_uart() for an example.
+debug serial port may be useful here. See setup_internal_uart() for an example.
During the U-Boot porting, one of the important steps is to write correct PIRQ
routing information in the board device tree. Without it, device drivers in the
diff --git a/doc/device-tree-bindings/misc/intel,baytrail-fsp.txt b/doc/device-tree-bindings/misc/intel,baytrail-fsp.txt
index b44b5b5..07fa46e 100644
--- a/doc/device-tree-bindings/misc/intel,baytrail-fsp.txt
+++ b/doc/device-tree-bindings/misc/intel,baytrail-fsp.txt
@@ -74,12 +74,41 @@ discovered by the FSP and used to setup main memory.
# Integer properties:
- - fsp,dram-speed
+ - fsp,dram-speed:
+ 0x0: "800 MHz"
+ 0x1: "1066 MHz"
+ 0x2: "1333 MHz"
+ 0x3: "1600 MHz"
+
- fsp,dram-type
+ 0x0: "DDR3"
+ 0x1: "DDR3L"
+ 0x2: "DDR3U"
+ 0x4: "LPDDR2"
+ 0x5: "LPDDR3"
+ 0x6: "DDR4"
+
- fsp,dimm-width
+ 0x0: "x8"
+ 0x1: "x16"
+ 0x2: "x32"
+
- fsp,dimm-density
+ 0x0: "1 Gbit"
+ 0x1: "2 Gbit"
+ 0x2: "4 Gbit"
+ 0x3: "8 Gbit"
+
- fsp,dimm-bus-width
+ 0x0: "8 bits"
+ 0x1: "16 bits"
+ 0x2: "32 bits"
+ 0x3: "64 bits"
+
- fsp,dimm-sides
+ 0x0: "1 rank"
+ 0x1: "2 ranks"
+
- fsp,dimm-tcl
- fsp,dimm-trpt-rcd
- fsp,dimm-twr