Replace calls to bus_generic_attach with bus_attach_childrenReviewed by: impDifferential Revision: https://reviews.freebsd.org/D47675
Check for errors when detaching children first, not lastThese detach routines in these drivers all ended with 'return(bus_generic_detach())' meaning that if any child device failed todetach, the
Check for errors when detaching children first, not lastThese detach routines in these drivers all ended with 'return(bus_generic_detach())' meaning that if any child device failed todetach, the parent driver was left in a mostly destroyed state, butstill marked attached. Instead, bus drivers should detach childdrivers first and return errors before destroying driver state in theparent.Reviewed by: impDifferential Revision: https://reviews.freebsd.org/D47387
show more ...
clk: Move clock code in dev/clkWe've removed kernel option EXT_RESOURCES almost two years ago.While it was ok to have some code under a common 'extres' subdirectoryat first, we now have a lot of
clk: Move clock code in dev/clkWe've removed kernel option EXT_RESOURCES almost two years ago.While it was ok to have some code under a common 'extres' subdirectoryat first, we now have a lot of consumer of it and we made it mandatoryso no need to have it under a cryptic name.Reviewed by: mhorneSponsored by: Beckhoff Automation GmbH & Co. KGDifferential Revision: https://reviews.freebsd.org/D43191
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSDThe SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catchup to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSDThe SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catchup to that fact and revert to their recommended match of BSD-2-Clause.Discussed with: pfgMFC After: 3 daysSponsored by: Netflix
dwwdt: Remove unused devclass argument to DRIVER_MODULE.
dwwdt: make it actually usefulFlip dwwdt_prevent_restart to false. What's the use of a watchdog if itdoes not restart a hung system?Add a knob for panic-ing on the first timeout, resetting on t
dwwdt: make it actually usefulFlip dwwdt_prevent_restart to false. What's the use of a watchdog if itdoes not restart a hung system?Add a knob for panic-ing on the first timeout, resetting on the secondone. This can be useful if interrupts can still work, otherwise a resetrecovers a system without any aid for debugging the hang.The change also doubles the timeout that's programmed into the hardware.The previous version of the code always had the interrupt on the firsttimeout enabled, but it took no action on it. Only the second timeoutcould be configured to reset the system. So, the hardware timeout wasset to a half of the user requested timeout. But now,we can take acorrective action on the first timeout, so we use the user requestedtimeout.While here, define boolean sysctl-s as such.Reviewed by: manuMFC after: 3 weeksDifferential Revision: https://reviews.freebsd.org/D33534
dwwdt: Add PNP info for the driver
Add driver for Synopsys Designware Watchdog timer.This driver supports some arm and arm64 boards equipped with"snps,dw-wdt"-compatible watchdog device.Tested on RK3399-based board (RockPro64).On
Add driver for Synopsys Designware Watchdog timer.This driver supports some arm and arm64 boards equipped with"snps,dw-wdt"-compatible watchdog device.Tested on RK3399-based board (RockPro64).Once started watchdog device cannot be stopped.Interrupt handler has mode to kick watchdog even when software does not do itproperly.This can be controlled via sysctl: dev.dwwdt.prevent_restart.Also - driver handles system shutdown and prevents from restart when systemis asked to reboot.Submitted by: kjopek@gmail.comDifferential Revision: https://reviews.freebsd.org/D26761