dm: core: Add a clarifying comment on struct udevice's seq member

[karo-tx-uboot.git] / doc / driver-model / README.txt

diff --git a/doc/driver-model/README.txt b/doc/driver-model/README.txt
index c435cdc6db10c9888a231a26d6806375186c141b..8dfcf75c3d369219b8cbc15782723013b94b0129 100644 (file)
--- 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