summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2014-10-13 23:41:51 -0600
committerSimon Glass <sjg@chromium.org>2014-10-22 10:36:46 -0600
commit547cea19b875ce83cc7c14ae750eca4973dab555 (patch)
treee4d9c7acf5ba6f26ba7a81ad024e4af00fd25756 /doc
parentaccd4b19b39bde7398aa8d1a8eeb66f3a14dde5b (diff)
downloadu-boot-imx-547cea19b875ce83cc7c14ae750eca4973dab555.zip
u-boot-imx-547cea19b875ce83cc7c14ae750eca4973dab555.tar.gz
u-boot-imx-547cea19b875ce83cc7c14ae750eca4973dab555.tar.bz2
dm: core: Add a clarifying comment on struct udevice's seq member
The sequence number is unique within the uclass, so state this clearly. Signed-off-by: Simon Glass <sjg@chromium.org> Acked-by: Jagannadha Sutradharudu Teki <jagannadh.teki@gmail.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/driver-model/README.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/driver-model/README.txt b/doc/driver-model/README.txt
index c435cdc..8dfcf75 100644
--- a/doc/driver-model/README.txt
+++ b/doc/driver-model/README.txt
@@ -359,7 +359,9 @@ Device Sequence Numbers
U-Boot numbers devices from 0 in many situations, such as in the command
line for I2C and SPI buses, and the device names for serial ports (serial0,
serial1, ...). Driver model supports this numbering and permits devices
-to be locating by their 'sequence'.
+to be locating by their 'sequence'. This numbering unique identifies a
+device in its uclass, so no two devices within a particular uclass can have
+the same sequence number.
Sequence numbers start from 0 but gaps are permitted. For example, a board
may have I2C buses 0, 1, 4, 5 but no 2 or 3. The choice of how devices are