Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Run the sxitemp(4) at IPL_SOFTCLOCK instead of IPL_VM. Prevents "panic: | 2020-07-15 | 1 | -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 that | 2020-01-23 | 1 | -11/+66 | |
| | | | | | | it works with future Linux device trees. ok patrick@ | ||||
* | Use information from nvmem (provided by sxisid(4)) to calibrate the | 2020-01-23 | 1 | -2/+30 | |
| | | | | | | temperature sensors. ok patrick@ | ||||
* | Register sxitemp(4) as a thermal sensor with the thermal zone support code. | 2019-09-21 | 1 | -1/+31 | |
| | | | | From Krystian Lewandowski. | ||||
* | Add Allwinner A64 support. | 2018-05-27 | 1 | -2/+33 | |
| | |||||
* | Add support for the Allwinner H3 SoC. | 2018-05-27 | 1 | -19/+43 | |
| | |||||
* | Add Allwinner R40/V40 support. | 2017-12-31 | 1 | -6/+28 | |
| | |||||
* | Add sxitemp(4), a driver for the temperature sensors on the Allwinner H5 SoC. | 2017-12-31 | 1 | -0/+162 | |