PATCH: f71882fg-sensor_attr2.patch [1/2]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Jean Delvare wrote:
> Hi Hans,
> 
> On Mon, 20 Oct 2008 11:29:04 +0200, Hans de Goede wrote:
>> From: Mark van Doesburg <mark.vandoesburg at hetnet.nl>
>>
>> Hi Jean (and all),
>>
>> Add pwm support to the f71882fg driver. Changes made by me to the latest
>> revision submitted by Mark van Doesburg:
>> -Remove whitespace only changes from the patch (undo Lindent damage)
>> -Change pwm#_auto_point#_temp unit from degrees to milli degrees celcius
>> -Remove incomplete ability to turn of pwm (pwm#_enable = 0), as the hardware
>>   does not support this
>> -Made handling of out of range input to sysfs files more robust
>> -When we write a new setting to IC update our local cached copy of the register
>>   being written
> 
> This is hardly a valid patch description for git. We don't care much
> about the incremental patches there, what we want to know is what the
> final patch is doing, why and how. I'll try to come up with something
> myself this time...
> 

Well the final patch: "Adds pwm support to the f71882fg driver" I know that 
isn't much of a description for such a large patch, but that is basicly it.

>> Signed-off-by: Hans de Goede <hdegoede at redhat.com>
>> Reviewed-by: Hans de Goede <hdegoede at redhat.com>
>> CC: Mark van Doesburg <mark.vandoesburg at hetnet.nl>
> 
> Preliminary note: I've split 5 unrelated coding style cleanups to a
> separate patch, and cleaned up defines a bit (spaces -> tabs and
> missing parentheses.
> 

Thanks!

> I am not totally happy with this patch:
> 
>> +static int fan_mode[4] = { 0, 0, 0, 0 };
>> +module_param_array(fan_mode, int, NULL, 0644);
>> +MODULE_PARM_DESC(fan_mode, "List of fan control modes (f71882fg only)"
>> +		 "(0=don't change, 1=pwm, 2=rpm)\n"
>> +		 "Note: this needs a write to pwm#_enable to take effect");
> 
> I don't really like this. But... I see that this is a result of
> previous discussions on the lm-sensors list I didn't take part to, so
> it's probably too late for me to object. And probably all interested
> parties have better things to do than reworking and retesting such a
> large patch. So, I'll take the patch as is.

Thanks, note that I'm not entirely happy with this myself either, I added the
"Note: this needs a write to pwm#_enable to take effect" comment to make 
atleast that much clear. The only reason for this option really is to be able 
to test both code paths easily (without it we default to whatever the BIOS has 
programmed the chip in). I've considered putting "testing use only" in the 
parameter description but I didn't think that would do any good either, we 
could put the option code in #ifdef DEBUG or something like that, but that 
didn't feel right either (I don't want this to require a recompile). So I guess 
this is just the best we can do, this or remove the option completely (which is 
a simple patch to make).

Regards,

Hans





[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux