tools/dtoc/test/dtoc_test_scan_drivers.cxx

/* Aliases must be in driver files */
U_BOOT_DRIVER(sandbox_gpio) {
};

DM_DRIVER_ALIAS(sandbox_gpio, sandbox_gpio_alias2)
dtoc: Process driver aliases along with drivers Instead of using a separate step for this processing, handle it while scanning its associated driver. This allows us to drop the code coverage exception in this case. Note that only files containing drivers are scanned by dtoc, so aliases declared in a file that doesn't hold a driver will not be noticed. It would be confusing to put them anywhere other than in the driver that they relate to, but update the documentation to say this explicitly, just in case. Signed-off-by: Simon Glass <sjg@chromium.org> 2021-02-03 06:01:05 -07:00			`/* Aliases must be in driver files */`
			`U_BOOT_DRIVER(sandbox_gpio) {`
			`};`

dm: Rename U_BOOT_DRIVER_ALIAS to DM_DRIVER_ALIAS We use the U_BOOT_ prefix (i.e. U_BOOT_DRIVER) to declare a driver but in every other case we just use DM_. Update the alias macros to use the DM_ prefix. We could perhaps rename U_BOOT_DRIVER() to DM_DRIVER(), but this macro is widely used and there is at least some benefit to indicating it us a U-Boot driver, particularly for code ported from Linux. So for now, let's keep that name. Signed-off-by: Simon Glass <sjg@chromium.org> 2020-12-28 20:34:57 -07:00			`DM_DRIVER_ALIAS(sandbox_gpio, sandbox_gpio_alias2)`