search for: pwm1_min

https://bugs.freedesktop.org/show_bug.cgi?id=79820 Priority: medium Bug ID: 79820 Assignee: nouveau at lists.freedesktop.org Summary: Strange readout on fan1_input when pwm1_min < 33 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: freedesk.apriori at spamgourmet.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified...

https://bugs.freedesktop.org/show_bug.cgi?id=66022 Priority: medium Bug ID: 66022 Assignee: nouveau at lists.freedesktop.org Summary: pwm1[_enable] faults after hibernate/restore related to automatic (or otherwise) fan management QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

...SENSOR_DEVICE_ATTR(temp1_auto_point1_temp_hyst, S_IRUGO | S_IWUSR, > +static SENSOR_DEVICE_ATTR(temp1_auto_point1_temp_hyst, 0644, > nouveau_hwmon_temp1_auto_point1_temp_hyst, > nouveau_hwmon_set_temp1_auto_point1_temp_hyst, 0); > > @@ -255,7 +255,7 @@ nouveau_hwmon_set_pwm1_min(struct device *d, struct device_attribute *a, > return count; > } > > -static SENSOR_DEVICE_ATTR(pwm1_min, S_IRUGO | S_IWUSR, > +static SENSOR_DEVICE_ATTR(pwm1_min, 0644, > nouveau_hwmon_get_pwm1_min, > nouveau_hwmon_set_pwm1_min, 0); > > @@ -295,7 +295...

...return count; } -static SENSOR_DEVICE_ATTR(temp1_auto_point1_temp_hyst, S_IRUGO | S_IWUSR, +static SENSOR_DEVICE_ATTR(temp1_auto_point1_temp_hyst, 0644, nouveau_hwmon_temp1_auto_point1_temp_hyst, nouveau_hwmon_set_temp1_auto_point1_temp_hyst, 0); @@ -313,7 +313,7 @@ nouveau_hwmon_set_pwm1_min(struct device return count; } -static SENSOR_DEVICE_ATTR(pwm1_min, S_IRUGO | S_IWUSR, +static SENSOR_DEVICE_ATTR(pwm1_min, 0644, nouveau_hwmon_get_pwm1_min, nouveau_hwmon_set_pwm1_min, 0); @@ -353,7 +353,7 @@ nouveau_hwmon_set_pwm1_max(struct device return count; } -static S...

...return count; } -static SENSOR_DEVICE_ATTR(temp1_auto_point1_temp_hyst, S_IRUGO | S_IWUSR, +static SENSOR_DEVICE_ATTR(temp1_auto_point1_temp_hyst, 0644, nouveau_hwmon_temp1_auto_point1_temp_hyst, nouveau_hwmon_set_temp1_auto_point1_temp_hyst, 0); @@ -255,7 +255,7 @@ nouveau_hwmon_set_pwm1_min(struct device *d, struct device_attribute *a, return count; } -static SENSOR_DEVICE_ATTR(pwm1_min, S_IRUGO | S_IWUSR, +static SENSOR_DEVICE_ATTR(pwm1_min, 0644, nouveau_hwmon_get_pwm1_min, nouveau_hwmon_set_pwm1_min, 0); @@ -295,7 +295,7 @@ nouveau_hwmon_set_pwm1_max(struct devic...

...erature > > After all, there is no requirement that pwm must exactly match the configured > value; the above only means that the chip uses those values to calculate > the necessary fan speed. In addition to that, you could still have some > of the other attributes as needed, such as pwm1_min, pwm1_max, and so on. This was my initial plan, roughly, but I like the first solution more at this point. > Hope this helps, > Guenter Definitely. Thank you. Regards, Gianni

Hello guys, For a patch to this nouveau bug [1] I'm trying to implement the sysfs interface for two properties (linear_min and linear_max) nouveau uses internally to decide when to raise the fan speed. The initial idea was to have them as custom sysfs attributes, but I was advised to try to fit them into the hwmon sysfs interface. And this is when I hit a little roadblock. If my

https://bugs.freedesktop.org/show_bug.cgi?id=87885 Bug ID: 87885 Summary: Fan speed of Nvidia GeForce 9600GT (G94) constantly too high Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

...31,7 +431,7 @@ nouveau_hwmon_set_pwm1(struct device *d, struct device_attribute *a, return count; } -static SENSOR_DEVICE_ATTR(pwm1, S_IRUGO | S_IWUSR, +static SENSOR_DEVICE_ATTR(pwm1, 0644, nouveau_hwmon_get_pwm1, nouveau_hwmon_set_pwm1, 0); @@ -471,7 +471,7 @@ nouveau_hwmon_set_pwm1_min(struct device *d, struct device_attribute *a, return count; } -static SENSOR_DEVICE_ATTR(pwm1_min, S_IRUGO | S_IWUSR, +static SENSOR_DEVICE_ATTR(pwm1_min, 0644, nouveau_hwmon_get_pwm1_min, nouveau_hwmon_set_pwm1_min, 0); @@ -511,7 +511,7 @@ nouveau_hwmon_set_pwm1_max(struct devic...

...IRUGO, amdgpu_hwmon_show_temp_thresh, NULL, 1); -static SENSOR_DEVICE_ATTR(pwm1, S_IRUGO | S_IWUSR, amdgpu_hwmon_get_pwm1, amdgpu_hwmon_set_pwm1, 0); -static SENSOR_DEVICE_ATTR(pwm1_enable, S_IRUGO | S_IWUSR, amdgpu_hwmon_get_pwm1_enable, amdgpu_hwmon_set_pwm1_enable, 0); -static SENSOR_DEVICE_ATTR(pwm1_min, S_IRUGO, amdgpu_hwmon_get_pwm1_min, NULL, 0); -static SENSOR_DEVICE_ATTR(pwm1_max, S_IRUGO, amdgpu_hwmon_get_pwm1_max, NULL, 0); -static SENSOR_DEVICE_ATTR(fan1_input, S_IRUGO, amdgpu_hwmon_get_fan1_input, NULL, 0); -static SENSOR_DEVICE_ATTR(in0_input, S_IRUGO, amdgpu_hwmon_show_vddgfx, NULL, 0);...

...wmon_show_temp_thresh, NULL, 1); > -static SENSOR_DEVICE_ATTR(pwm1, S_IRUGO | S_IWUSR, amdgpu_hwmon_get_pwm1, amdgpu_hwmon_set_pwm1, 0); > -static SENSOR_DEVICE_ATTR(pwm1_enable, S_IRUGO | S_IWUSR, amdgpu_hwmon_get_pwm1_enable, amdgpu_hwmon_set_pwm1_enable, 0); > -static SENSOR_DEVICE_ATTR(pwm1_min, S_IRUGO, amdgpu_hwmon_get_pwm1_min, NULL, 0); > -static SENSOR_DEVICE_ATTR(pwm1_max, S_IRUGO, amdgpu_hwmon_get_pwm1_max, NULL, 0); > -static SENSOR_DEVICE_ATTR(fan1_input, S_IRUGO, amdgpu_hwmon_get_fan1_input, NULL, 0); > -static SENSOR_DEVICE_ATTR(in0_input, S_IRUGO, amdgpu_hwmon_show_vd...

...t;> After all, there is no requirement that pwm must exactly match the configured >> value; the above only means that the chip uses those values to calculate >> the necessary fan speed. In addition to that, you could still have some >> of the other attributes as needed, such as pwm1_min, pwm1_max, and so on. > > This was my initial plan, roughly, but I like the first solution more at > this point. > >> Hope this helps, >> Guenter > > Definitely. Thank you. > > Regards, > Gianni > >

...uto_point2_temp high temperature After all, there is no requirement that pwm must exactly match the configured value; the above only means that the chip uses those values to calculate the necessary fan speed. In addition to that, you could still have some of the other attributes as needed, such as pwm1_min, pwm1_max, and so on. Hope this helps, Guenter

...Hardware: Other Status: NEW Version: unspecified Component: Driver/nouveau Product: xorg When I have done the following: echo 1 > /sys/class/hwmon/hwmon0/pwm1_enable echo 30 > /sys/class/hwmon/hwmon0/pwm1 pwm1=30 pwm1_enable=1 pwm1_max=100 pwm1_min=0 temp1_auto_point1_pwm=100 temp1_auto_point1_temp=90000 temp1_auto_point1_temp_hyst=3000 temp1_crit=115000 temp1_crit_hyst=2000 temp1_emergency=135000 temp1_emergency_hyst=5000 temp1_input=41000 temp1_max=95000 temp1_max_hyst=3000 update_rate=1000 and then do hibernate/restore, I get this: pwm1=...

...st = +5.0?C) ... When I follow Documentation/thermal/nouveau_thermal and the speed to 100%, nouveau reports "fan1: 6840 RPM" while the highest reported RPM by Windows (both Gigabyte tools and CPU-Z) is 3390 or 3420 RPM. Similar to when I set the lowest speed (I have modified bios and my pwm1_min is 30) nouveau reports "fan1: 3180 RPM" while Windows shows 1560 or 1590 RPM. Could that be because the card has two physical fans? Reporting the speed of single fan would make more sense IMHO. -- You are receiving this mail because: You are the assignee for the bug. -------------- next...

This v6 fixes some comments pointed out by Martin Peres. Versions: v1 -> v2: * Keep temp attrs as read only v2 -> v3: * Code fix-ups: struct and string as const and add return within switch due to fallthrough * Add Signed-off-by to all commits v3 -> v4: * Rever const to struct attribute. Kbuild complains. v4 -> v5: * Drops a check for

...gs for this issue are same as in Bug 78106) 1a) When I finish booting, nouveau selects AUTO mode (pwm1_enable: 2) and set's the fan power to 55% (pwm1: 55). 1b) Enable manual mode, set pwm1 to 100, enable auto mode. In both cases I would expect from the AUTO mode to lower PWM to go as low as pwm1_min if the temperature is low enough. My card temperature is 31-33 ?C but pwm1 is never lowered in AUTO mode (neither from 55 or 100). 2) On Windows pwm goes as low as pwm1_min (which is 40 by default for GTX 560 Ti but it also works with my modded value of 30). I thought that Nvidia card can manage i...

This v5 drops a check for attr_set. Versions: v1 -> v2: * Keep temp attrs as read only v2 -> v3: * Code fix-ups: struct and string as const and add return within switch due to fallthrough * Add Signed-off-by to all commits v3 -> v4: * Rever const to struct attribute. Kbuild complains. v4 -> v5: * Drops a check for attr_set in

This v8 fixes removes dummy functions which only had a return and moves the code into the switch statements. Versions: v1 -> v2: * Keep temp attrs as read only v2 -> v3: * Code fix-ups: struct and string as const and add return within switch due to fallthrough * Add Signed-off-by to all commits v3 -> v4: * Rever const to struct attribute. Kbuild

This v7 fixes removes dummy functions which only had a return and moves the code into the switch statements. Versions: v1 -> v2: * Keep temp attrs as read only v2 -> v3: * Code fix-ups: struct and string as const and add return within switch due to fallthrough * Add Signed-off-by to all commits v3 -> v4: * Rever const to struct attribute. Kbuild