FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.4 2020-12-19T04:28:25Z 2020-12-19T04:28:25Z Ryan Libby rlibby@FreeBSD.org 2020-12-19T04:28:25Z urn:sha1:1e2ccfc6c290defe415d33bcdcc49ac62ea5de7e - Fix gcc build for superio(4) - Change string mapping of SUPERIO_DEV_NONE to distinguish from SUPERIO_DEV_MAX Reviewed by: imp Discussed with: avg, imp, jhb Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D20880 2020-06-11T05:28:08Z Andriy Gapon avg@FreeBSD.org 2020-06-11T05:28:08Z urn:sha1:a5ab79a340192ee25b6631c6e80d4fda8e58f743 That assumption should be true when superio(4) uses the hardware exlusively. But it turns out to not hold on some real systems. So, err on the side of correctness rather than performance. Clear current_ldn in sio_conf_exit. 2019-11-04T09:49:58Z Andriy Gapon avg@FreeBSD.org 2019-11-04T09:49:58Z urn:sha1:914b4006a44cd0315b1190e2fca6fde761a50ab2 The goal of this driver is consolidate information about SuperIO chips and to provide for peaceful coexistence of drivers that need to access SuperIO configuration registers. While SuperIO chips can host various functions most of them are discoverable and accessible without any knowledge of the SuperIO. Examples are: keyboard and mouse controllers, UARTs, floppy disk controllers. SuperIO-s also provide non-standard functions such as GPIO, watchdog timers and hardware monitoring. Such functions do require drivers with a knowledge of a specific SuperIO. At this time the driver supports a number of ITE and Nuvoton (fka Winbond) SuperIO chips. There is a single driver for all devices. So, I have not done the usual split between the hardware driver and the bus functionality. Although, superio does act as a bus for devices that represent known non-standard functions of a SuperIO chip. The bus provides enumeration of child devices based on the hardcoded knowledge of such functions. The knowledge as extracted from datasheets and other drivers. As there is a single driver, I have not defined a kobj interface for it. So, its interface is currently made of simple functions. I think that we can the flexibility (and complications) when we actually need it.