From: Jean Delvare <jdelvare@suse.de>
To: Goffredo Baroncelli <kreijack@gmail.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
LKML <linux-kernel@vger.kernel.org>,
Goffredo Baroncelli <kreijack@inwind.it>
Subject: Re: [PATCH 3/5] Add the "verbose" module option.
Date: Thu, 07 Aug 2014 10:52:35 +0200 [thread overview]
Message-ID: <1407401555.4314.14.camel@chaos.site> (raw)
In-Reply-To: <1407359103-6012-4-git-send-email-kreijack@inwind.it>
Le Wednesday 06 August 2014 à 21:05 +0000, Goffredo Baroncelli a écrit :
> Add a "verbose" option to control the message in the kernel log
> verbose = 0 no message
> verbose = 1 log only the fan speed changes
> verbose = 2 log the fan speed changes and the temperature changes
>
> Signed-off-by: Goffredo Baroncelli <kreijack@inwind.it>
> ---
> drivers/macintosh/therm_windtunnel.c | 39 +++++++++++++++++++++++-------------
> 1 file changed, 25 insertions(+), 14 deletions(-)
Looks overall good, minor comments inline below.
> diff --git a/drivers/macintosh/therm_windtunnel.c b/drivers/macintosh/therm_windtunnel.c
> index 1e50455..7c512db 100644
> --- a/drivers/macintosh/therm_windtunnel.c
> +++ b/drivers/macintosh/therm_windtunnel.c
> @@ -44,7 +44,9 @@
> #include <asm/sections.h>
> #include <asm/macio.h>
>
> -#define LOG_TEMP 0 /* continuously log temperature */
> +static int verbose = 1;
> +module_param(verbose, int, 0644);
> +MODULE_PARM_DESC(verbose, "Verbosity level: 0=silent, 1=log the fan tuning, 2=log the temperature");
>
> static struct {
> volatile int running;
> @@ -157,10 +159,6 @@ tune_fan( int fan_setting )
> /* write_reg( x.fan, 0x24, val, 1 ); */
> write_reg( x.fan, 0x25, val, 1 );
> write_reg( x.fan, 0x20, 0, 1 );
> - print_temp("CPU-temp: ", x.temp );
> - if( x.casetemp )
> - print_temp(", Case: ", x.casetemp );
> - printk(", Fan: %d (tuned %+d)\n", 11-fan_setting, x.fan_level-fan_setting );
>
> x.fan_level = fan_setting;
> }
> @@ -168,7 +166,7 @@ tune_fan( int fan_setting )
> static void
> poll_temp( void )
> {
> - int temp, i, level, casetemp;
> + int temp, i, level, casetemp, tempchanged;
>
> temp = read_reg( x.thermostat, 0, 2 );
>
> @@ -179,14 +177,6 @@ poll_temp( void )
> casetemp = read_reg(x.fan, 0x0b, 1) << 8;
> casetemp |= (read_reg(x.fan, 0x06, 1) & 0x7) << 5;
>
> - if( LOG_TEMP && x.temp != temp ) {
> - print_temp("CPU-temp: ", temp );
> - print_temp(", Case: ", casetemp );
> - printk(", Fan: %d\n", 11-x.fan_level );
> - }
> - x.temp = temp;
> - x.casetemp = casetemp;
> -
> level = -1;
> for( i=0; (temp & 0xffff) > fan_table[i].temp ; i++ )
> ;
> @@ -200,6 +190,27 @@ poll_temp( void )
> level = fan_table[i].fan_up_setting;
> x.upind = i;
>
> + /*
> + * if verbose >0 log each fan tuning
> + * if verbose >1 log each cpu temperature change
Maybe this is just me but I think "verbose >= 1" and "verbose >= 2"
would be easier to understand. Same in the code below.
> + */
> + tempchanged = x.temp != temp || x.casetemp != casetemp;
> + if ((verbose > 1 && tempchanged) ||
> + (verbose > 0 && level >= 0)) {
> + printk(KERN_INFO);
> + print_temp("CPU-temp: ", temp);
This can be written more efficiently as a single statement:
print_temp(KERN_INFO "CPU-temp: ", temp);
> + if (casetemp)
> + print_temp(", Case: ", casetemp);
> + if (level >= 0)
> + printk(", Fan: %d (tuned %+d)\n", 11-level,
> + x.fan_level-level);
> + else
> + printk(", Fan: %d\n", 11-x.fan_level);
> + }
> +
> + x.temp = temp;
> + x.casetemp = casetemp;
> +
> if( level >= 0 )
> tune_fan( level );
> }
Reviewed-by: Jean Delvare <jdelvare@suse.de>
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2014-08-07 8:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 21:04 [PATCH][v3] therm_windtunnel doesn't work properly on PowerMac G4 Goffredo Baroncelli
2014-08-06 21:04 ` [PATCH 1/5] Update drivers names to the ones invoked by i2c-powermac Goffredo Baroncelli
2014-08-06 21:05 ` [PATCH 2/5] Remove attach_method because un-used Goffredo Baroncelli
2014-08-07 8:39 ` Jean Delvare
2014-08-06 21:05 ` [PATCH 3/5] Add the "verbose" module option Goffredo Baroncelli
2014-08-07 8:52 ` Jean Delvare [this message]
2014-08-07 16:29 ` Goffredo Baroncelli
2014-08-07 16:43 ` Jean Delvare
2014-08-07 16:52 ` Goffredo Baroncelli
2014-08-06 21:05 ` [PATCH 4/5] Return the fan speed via sysfs Goffredo Baroncelli
2014-08-06 21:05 ` [PATCH 5/5] Export the temperatures via hwmon Goffredo Baroncelli
2014-08-06 23:18 ` Guenter Roeck
2014-08-07 6:03 ` Goffredo Baroncelli
2014-08-07 6:20 ` Guenter Roeck
2014-08-07 6:52 ` Jean Delvare
2014-08-07 7:36 ` Guenter Roeck
2014-08-07 8:35 ` Jean Delvare
2014-08-07 14:19 ` Guenter Roeck
2014-08-07 17:50 ` Goffredo Baroncelli
2014-08-07 18:16 ` Guenter Roeck
2014-08-07 19:27 ` Goffredo Baroncelli
2014-08-07 21:19 ` Matt Helsley
2014-08-08 14:54 ` Goffredo Baroncelli
2014-08-08 16:30 ` Guenter Roeck
2014-08-08 16:58 ` Goffredo Baroncelli
2014-08-07 19:08 [PATCH][v4] therm_windtunnel does not work properly on PowerMac G4 Goffredo Baroncelli
2014-08-07 19:08 ` [PATCH 3/5] Add the "verbose" module option Goffredo Baroncelli
2014-08-09 6:49 [PATCH][v5] therm_windtunnel does not work properly on PowerMac G4 Goffredo Baroncelli
2014-08-09 6:50 ` [PATCH 3/5] Add the "verbose" module option Goffredo Baroncelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1407401555.4314.14.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kreijack@gmail.com \
--cc=kreijack@inwind.it \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®