| commit | eea4eb14a0f74f806e7a458f174f880744a68bdd | |
| author | Martin Peres <martin.peres@labri.fr> | |
| Tue, 5 Mar 2013 09:35:20 +0000 (5 10:35 +0100) | ||
| committer | Ben Skeggs <bskeggs@redhat.com> | |
| Mon, 18 Mar 2013 01:15:26 +0000 (18 11:15 +1000) | ||
| tree | 4f72a66b5c44493c39483be1592ad11ce338bafc | treesnapshot (tar.gz zip) |
| parent | 7ae9712c60698ae2870fd115cb3ef4449a615509 | commitdiff |
drm/nv40/therm: increase the sensor's settling delay to 20ms
Based on my experience, 10ms wasn't always enough. Let's bump that
to a little more.
If this turns out to be insufficient-enough again, then an approach
based on letting the sensor settle for several seconds before starting
polling on the temperature would be better suited. This way, boot time
wouldn't be impacted by those waits too much.
Signed-off-by: Martin Peres <martin.peres@labri.fr>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Based on my experience, 10ms wasn't always enough. Let's bump that
to a little more.
If this turns out to be insufficient-enough again, then an approach
based on letting the sensor settle for several seconds before starting
polling on the temperature would be better suited. This way, boot time
wouldn't be impacted by those waits too much.
Signed-off-by: Martin Peres <martin.peres@labri.fr>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
| drivers/gpu/drm/nouveau/core/subdev/therm/nv40.c | diffblobblamehistory |