diff options
| author | Tom Rini <[email protected]> | 2025-03-30 09:10:57 -0600 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2025-03-30 09:11:07 -0600 |
| commit | f1895bc1e71c18fb872e2fec40ff2310d6b4a0bb (patch) | |
| tree | d1a588eb9f90acb777eff6be184f8dca36d504b2 /drivers | |
| parent | 5ca70325b64f760bf4190f206a0e88dda495e3d2 (diff) | |
| parent | 44450434ea9f0f2e0d8ddfd853f4990c1719b4aa (diff) | |
Merge patch series "Clarify DM_FLAG_PROBE_AFTER_BIND behaviour"
Caleb Connolly <[email protected]> says:
In Simon's series reworking autoprobe, a discussion came up about
DM_FLAG_PROBE_AFTER_BIND, specifically that it wasn't very clear where
this flag should be used.
This series implements my suggestions made there to clarify the use of
this flag, and fixup the two driver which erroneously apply it to their
driver struct (this does nothing).
Link: https://lore.kernel.org/u-boot/[email protected]/
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/mailbox/zynqmp-ipi.c | 1 | ||||
| -rw-r--r-- | drivers/watchdog/da9063-wdt.c | 1 |
2 files changed, 0 insertions, 2 deletions
diff --git a/drivers/mailbox/zynqmp-ipi.c b/drivers/mailbox/zynqmp-ipi.c index 713d93a200c..851aa737c03 100644 --- a/drivers/mailbox/zynqmp-ipi.c +++ b/drivers/mailbox/zynqmp-ipi.c @@ -270,5 +270,4 @@ U_BOOT_DRIVER(zynqmp_ipi) = { .id = UCLASS_NOP, .of_match = zynqmp_ipi_ids, .probe = zynqmp_ipi_probe, - .flags = DM_FLAG_PROBE_AFTER_BIND, }; diff --git a/drivers/watchdog/da9063-wdt.c b/drivers/watchdog/da9063-wdt.c index b7216b57863..ec9bc033011 100644 --- a/drivers/watchdog/da9063-wdt.c +++ b/drivers/watchdog/da9063-wdt.c @@ -145,5 +145,4 @@ U_BOOT_DRIVER(da9063_wdt) = { .id = UCLASS_WDT, .of_match = da9063_wdt_ids, .ops = &da9063_wdt_ops, - .flags = DM_FLAG_PROBE_AFTER_BIND, }; |