diff options
author | Simon Glass <sjg@chromium.org> | 2023-04-25 10:54:30 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2023-04-27 13:51:06 -0400 |
commit | 80778f505c8c7ee18c24cfbcfe011f8a2abf7bcd (patch) | |
tree | b67a4b4918be432232506049b20f1b29f053fe3d /boot | |
parent | 00a79f21c1c178d312635b96035da6aa48eb5321 (diff) | |
download | u-boot-80778f505c8c7ee18c24cfbcfe011f8a2abf7bcd.tar.gz u-boot-80778f505c8c7ee18c24cfbcfe011f8a2abf7bcd.tar.bz2 u-boot-80778f505c8c7ee18c24cfbcfe011f8a2abf7bcd.zip |
ide: Move ide_init() into probing
At present the code does ide_init() as a separate operation, then calls
device_probe() to copy over the information. We can call ide_init() from
probe just as easily.
The only difference is that using 'ide init' twice will do nothing.
However it already fails to copy over the new data in that case, so the
effect is the same. For now, unbind the block devices and remove the IDE
device, which causes the bus to be probed again. Later patches will fix
this up fully, so that all blk_desc data is copied across.
Since ide_reset() is only called from ide_init(), there is no need to init
the ide_dev_desc[] array. This is already done at the end of ide_init() so
drop this code.
The call to uclass_first_device() is now within the probe() function of
the same device, so does nothing. Drop it.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'boot')
0 files changed, 0 insertions, 0 deletions