diff options
| author | Simon Glass <sjg@chromium.org> | 2020-12-17 07:20:07 +0300 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2020-12-19 06:32:21 +0300 |
| commit | 8b85dfc675f12de8d04126c07f3c796965b990c2 (patch) | |
| tree | 9b8d6df956b02734a1b910b0a4c072e1e80b672a /include/pci.h | |
| parent | 0b2fa98aa5e5dbdac4f5e2b2f67a34cc34dcc6b8 (diff) | |
| download | u-boot-8b85dfc675f12de8d04126c07f3c796965b990c2.tar.xz | |
dm: Avoid accessing seq directly
At present various drivers etc. access the device's 'seq' member directly.
This makes it harder to change the meaning of that member. Change access
to go through a function instead.
The drivers/i2c/lpc32xx_i2c.c file is left unchanged for now.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'include/pci.h')
| -rw-r--r-- | include/pci.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/pci.h b/include/pci.h index d5b42cee83..5f36537b72 100644 --- a/include/pci.h +++ b/include/pci.h @@ -934,7 +934,7 @@ struct dm_pci_ops { * PCI buses must support reading and writing configuration values * so that the bus can be scanned and its devices configured. * - * Normally PCI_BUS(@bdf) is the same as @bus->seq, but not always. + * Normally PCI_BUS(@bdf) is the same as @dev_seq(bus), but not always. * If bridges exist it is possible to use the top-level bus to * access a sub-bus. In that case @bus will be the top-level bus * and PCI_BUS(bdf) will be a different (higher) value |