summaryrefslogtreecommitdiffstats
path: root/sys/dev/fdt/sxitemp.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Run the sxitemp(4) at IPL_SOFTCLOCK instead of IPL_VM. Prevents "panic:dtucker2020-07-151-2/+2
| | | | | | | | | | | | | | | | | | | | mtx ...: locking against myself" on Orange Pi Zero. Analysis by patrick@: "The thermal sensor framework uses its own taskq with IPL_SOFTCLOCK. sxitemp(4) calls thermal_sensor_update() from interrupt context, and sxitemp(4) is using IPL_VM (memory allocation?!) for its interrupt. IPL_VM is obviously higher than IPL_SOFTCLOCK, so it ends up being able to interrupt the taskq. Even though we're in msleep_nsec, I think we have *not yet* given up the mutex, that we are holding while looking for more work, only releasing it while sleeping. Thus, the interrupt runs task_add(), which tries to grab the taskq's mutex, even though the taskq already holds it!" ok patrick@ kettenis@
* Make thermal framework support in sxitemp(4) interrupt driven such thatkettenis2020-01-231-11/+66
| | | | | | it works with future Linux device trees. ok patrick@
* Use information from nvmem (provided by sxisid(4)) to calibrate thekettenis2020-01-231-2/+30
| | | | | | temperature sensors. ok patrick@
* Register sxitemp(4) as a thermal sensor with the thermal zone support code.kettenis2019-09-211-1/+31
| | | | From Krystian Lewandowski.
* Add Allwinner A64 support.kettenis2018-05-271-2/+33
|
* Add support for the Allwinner H3 SoC.kettenis2018-05-271-19/+43
|
* Add Allwinner R40/V40 support.kettenis2017-12-311-6/+28
|
* Add sxitemp(4), a driver for the temperature sensors on the Allwinner H5 SoC.kettenis2017-12-311-0/+162