diff options
| author | Simon Glass <sjg@chromium.org> | 2020-12-04 02:55:17 +0300 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2020-12-13 18:00:25 +0300 |
| commit | 41575d8e4c334df148c4cdd7c40cc825dc0fcaa1 (patch) | |
| tree | c27d9450fb5e72372be8483fc15079467b588169 /doc/driver-model/usb-info.rst | |
| parent | 78128d52dfca9fff53770c7aed2e4673070c5978 (diff) | |
| download | u-boot-41575d8e4c334df148c4cdd7c40cc825dc0fcaa1.tar.xz | |
dm: treewide: Rename auto_alloc_size members to be shorter
This construct is quite long-winded. In earlier days it made some sense
since auto-allocation was a strange concept. But with driver model now
used pretty universally, we can shorten this to 'auto'. This reduces
verbosity and makes it easier to read.
Coincidentally it also ensures that every declaration is on one line,
thus making dtoc's job easier.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/driver-model/usb-info.rst')
| -rw-r--r-- | doc/driver-model/usb-info.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/driver-model/usb-info.rst b/doc/driver-model/usb-info.rst index 1817df420f..5f7cbfce09 100644 --- a/doc/driver-model/usb-info.rst +++ b/doc/driver-model/usb-info.rst @@ -43,8 +43,8 @@ as drivers in the USB uclass. For example: .probe = tegra_ehci_usb_probe, .remove = tegra_ehci_usb_remove, .ops = &ehci_usb_ops, - .platdata_auto_alloc_size = sizeof(struct usb_platdata), - .priv_auto_alloc_size = sizeof(struct fdt_usb), + .platdata_auto = sizeof(struct usb_platdata), + .priv_auto = sizeof(struct fdt_usb), .flags = DM_FLAG_ALLOC_PRIV_DMA, }; @@ -58,7 +58,7 @@ The ops here are ehci_usb_ops. All EHCI drivers will use these same ops in most cases, since they are all EHCI-compatible. For EHCI there are also some special operations that can be overridden when calling ehci_register(). -The driver can use priv_auto_alloc_size to set the size of its private data. +The driver can use priv_auto to set the size of its private data. This can hold run-time information needed by the driver for operation. It exists when the device is probed (not when it is bound) and is removed when the driver is removed. |