kbd drivers: use kbdd_* indirection for diag invocation
These invocations were directly calling enkbd_diag(), rather than indirection back through kbdd_diag/kbdsw. While they're functionally equivent, invoking kbdd_diag where feasible (i.e. not in a diag implementation) makes it easier to visually identify locking needs in these other drivers.
This commit is contained in:
parent
319bd32173
commit
4434de9643
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=355793
@ -717,7 +717,7 @@ pl050_kmi_attach(device_t dev)
|
||||
#endif
|
||||
|
||||
if (bootverbose) {
|
||||
genkbd_diag(kbd, bootverbose);
|
||||
kbdd_diag(kbd, bootverbose);
|
||||
}
|
||||
kmi_attached = 1;
|
||||
return (0);
|
||||
|
@ -432,7 +432,7 @@ gpiokeys_attach(device_t dev)
|
||||
#endif
|
||||
|
||||
if (bootverbose) {
|
||||
genkbd_diag(kbd, 1);
|
||||
kbdd_diag(kbd, 1);
|
||||
}
|
||||
|
||||
total_keys = 0;
|
||||
|
@ -535,7 +535,7 @@ hv_kbd_drv_attach(device_t dev)
|
||||
}
|
||||
#endif
|
||||
if (bootverbose) {
|
||||
genkbd_diag(kbd, bootverbose);
|
||||
kbdd_diag(kbd, bootverbose);
|
||||
}
|
||||
return (0);
|
||||
detach:
|
||||
|
@ -1369,7 +1369,7 @@ ukbd_attach(device_t dev)
|
||||
sc->sc_flags |= UKBD_FLAG_ATTACHED;
|
||||
|
||||
if (bootverbose) {
|
||||
genkbd_diag(kbd, bootverbose);
|
||||
kbdd_diag(kbd, bootverbose);
|
||||
}
|
||||
|
||||
#ifdef USB_DEBUG
|
||||
|
Loading…
Reference in New Issue
Block a user