similar to: [Bug 80900] New: [NVCF] PWM fan speed too high under kernel 3.15

https://bugs.freedesktop.org/show_bug.cgi?id=80901 Priority: medium Bug ID: 80901 Assignee: nouveau at lists.freedesktop.org Summary: [NVCF] PWM fan speed too high under kernel 3.15 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: gianni at rootcube.net Hardware: x86-64 (AMD64)

https://bugs.freedesktop.org/show_bug.cgi?id=83587 Priority: medium Bug ID: 83587 Assignee: nouveau at lists.freedesktop.org Summary: 3.14.18: FAN control: none / external -- 3.16.2: FAN control: PWM QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

From: Martin Peres <martin.peres at labri.fr> Signed-off-by: Martin Peres <martin.peres at free.fr> --- drm/Kbuild | 1 + drm/core/subdev/therm/gm107.c | 1 + nvkm/engine/device/gm100.c | 4 +- nvkm/include/subdev/therm.h | 1 + nvkm/subdev/therm/Makefile.am | 3 +- nvkm/subdev/therm/fan.c | 9 ++++- nvkm/subdev/therm/gm107.c | 93

https://bugs.freedesktop.org/show_bug.cgi?id=60704 Priority: medium Bug ID: 60704 Assignee: nouveau at lists.freedesktop.org Summary: [nouveau, git regression] - I2C PWM fan control broken on nv50 adt7475 on kernels 3.3.x+ QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified

Signed-off-by: Martin Peres <martin.peres at free.fr> Tested-by: SaveTheRobots <john.rowley08 at gmail.com> --- drivers/gpu/drm/nouveau/core/subdev/therm/nvd0.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/nouveau/core/subdev/therm/nvd0.c b/drivers/gpu/drm/nouveau/core/subdev/therm/nvd0.c index 43fec17..bbf117b 100644 ---

Hello, We recently reverse engineered PWM-based voltage management but found an odity in the input clock frequency for the PWM controller. It seems like RM is assuming an input clock of 27.648 MHz instead of the actual 27MHz crystal found on the board. I thus have the following questions: - Is it a fixed value hardcoded in RM? (Current way it is done in Nouveau) - Should we use

I am using ST micro's STM32F103 chip with their AN2812 development code. It uses a PWM output, resulting in low-quality sound. Can I just use a scaled version of the PWM to drive a DAC? (i.e. is the output linear, or is there shaping to make the PWM output work?) Any feedback, links or pointers would be greatly appreciated. David. -------------- next part -------------- An HTML attachment

I saw a Help e-mail related to MLE. Does R have a probability weighted method (PWM) estimator function? I can't seem to find anything on PWM, unless my eyes are playing trick on me. [[alternative HTML version deleted]]

Hi, I have just setup CentOS4 on a system and want to get "fancontrol" working.. I am able to get lm_sensors configured but when I run pwmconfig I am told there are no modules loaded.. What module needs to be loaded for pwmconfig and fancontrol to work? (Board does support PWM in the fans because fancontrol worked on this pc with Ubuntu) TIA

On 18/09/15 23:30, Andy Ritger wrote: > Thanks, Martin. I'll try to follow up on this next week and get you an answer. What GPUs have you observed this on? > Thanks Andy, As far as I can tell, it is the case for all GPUs using the PWM-based voltage management. To be more specific, we have seen this behaviour on a GK106 (mobile), a GM117 and a GM204.

A NV34 GPU was seeing temp and pwm entries in hwmon, which would error out when read. These should not have been visible, but also the whole hwmon object should just not have been registered in the first place. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/nouveau_hwmon.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git

https://bugs.freedesktop.org/show_bug.cgi?id=66177 Priority: medium Bug ID: 66177 Assignee: nouveau at lists.freedesktop.org Summary: pwm1 value not restored during hibernate/restore cycle in the event of manual fan management mode QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

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

Hi Guenter, > For automatic fan control we don't really have a well defined ABI. > Part of the problem is that the mechanisms used by various chips are > quite different. > > Please have a look into Documentation/hwmon/nct6775. It is by far > the driver with the most comprehensive fan control mechanisms and > attributes. Would any of the attributes or atribute groups in

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

As of kernel 5.1.9, on resume from suspend, my NV50 fan runs at full speed. Not sure if it has to do with this new config option (NOUVEAU_LEGACY_CTX_SUPPORT)? This issue is not present using kernel 5.0.21. Years ago I filed a similar issue: 60704 – [nouveau, git regression] - I2C PWM fan control broken on nv50 adt7475 on kernels 3.3.x+ Thanks. | | | | 60704 – [nouveau, git regression] -

On 07/16/2014 11:29 PM, Gianni Vialetto wrote: > Hi Guenter, > >> For automatic fan control we don't really have a well defined ABI. >> Part of the problem is that the mechanisms used by various chips are >> quite different. >> >> Please have a look into Documentation/hwmon/nct6775. It is by far >> the driver with the most comprehensive fan control

On Mon, Jul 14, 2014 at 06:47:28PM +0200, Gianni Vialetto wrote: > 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

I don't really see anything between v5.0..v5.1 which would account for this. Could have been a subtle change to the i2c logic somewhere. The fastest way to identify the problem would be to do a bisect on the kernel to identify the commit that caused this. There are many guides for this online. On Sat, Jun 15, 2019 at 12:17 PM Mar Mel <marmel6942 at yahoo.com> wrote: > Unfortunately,

Mar - can you provide the output of lspci -nn -d 10de: On Sat, Jun 22, 2019 at 2:17 PM Lyude Paul <lyude at redhat.com> wrote: > Hi, is this actually an nv50 GPU, or some other model? I can try to take a > closer look at this > > On Sun, 2019-06-16 at 10:28 -0400, Ilia Mirkin wrote: > > I don't really see anything between v5.0..v5.1 which would account for > this.