leandrof/u-boot
1
0
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: dm: describe end of life of plat_auto

Browse Source 
Describe when plat_auto is freed.

Fix a typo.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Heinrich Schuchardt 2021-01-31 11:04:12 +01:00
parent 4038c6e848
commit 5489448cd7
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/driver-model/design.rst
View File

@ -725,7 +725,7 @@ The steps are:
2. If plat_auto is non-zero, then the platform data space 2. If plat_auto is non-zero, then the platform data space
is allocated. This is only useful for device tree operation, since is allocated. This is only useful for device tree operation, since
otherwise you would have to specific the platform data in the otherwise you would have to specify the platform data in the
U_BOOT_DRVINFO() declaration. The space is allocated for the device and U_BOOT_DRVINFO() declaration. The space is allocated for the device and
zeroed. It will be accessible as dev->plat. zeroed. It will be accessible as dev->plat.
@ -861,8 +861,8 @@ remove it. This performs the probe steps in reverse:
be dynamically allocated, and thus needs to be deallocated during the be dynamically allocated, and thus needs to be deallocated during the
remove() method, either: remove() method, either:
- if the plat_auto is non-zero, the deallocation - if the plat_auto is non-zero, the deallocation happens automatically
happens automatically within the driver model core; or within the driver model core in the unbind stage; or
- when plat_auto is 0, both the allocation (in probe() - when plat_auto is 0, both the allocation (in probe()
or preferably of_to_plat()) and the deallocation in remove() or preferably of_to_plat()) and the deallocation in remove()