linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: linux-arch@vger.kernel.org, linux-gpio@vger.kernel.org,
	yamada.masahiro@socionext.com, linus.walleij@linaro.org,
	linux-pm@vger.kernel.org, linux@rasmusvillemoes.dk,
	linux-kernel@vger.kernel.org, morten.tiljeset@prevas.dk,
	sean.nyekjaer@prevas.dk, bgolaszewski@baylibre.com,
	lukas@wunner.de, geert@linux-m68k.org, akpm@linux-foundation.org,
	preid@electromag.com.au, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v16 11/14] thermal: intel: intel_soc_dts_iosf: Utilize for_each_set_clump8 macro
Date: Mon, 7 Oct 2019 11:44:29 +0300	[thread overview]
Message-ID: <20191007084429.GN32742@smile.fi.intel.com> (raw)
In-Reply-To: <8e85aa4ccead5c330d7abdbda292f32a0c48902e.1570374078.git.vilhelm.gray@gmail.com>

On Sun, Oct 06, 2019 at 11:11:08AM -0400, William Breathitt Gray wrote:
> Utilize for_each_set_clump8 macro, and the bitmap_set_value8 and
> bitmap_get_value8 functions, where appropriate. In addition, remove the
> now unnecessary temp_mask and temp_shift members of the
> intel_soc_dts_sensor_entry structure.

Since it perhaps will be next version, I have few style comments here
(ignore them if you are not going to send a new version by some other reasons).

>  	int status;
>  	u32 temp_out;

> +	unsigned long update_ptps;

I think it's better to put it one line below.

>  	u32 out;
>  	u32 store_ptps;
>  	u32 store_ptmc;

> -	out = (store_ptps & ~(0xFF << (thres_index * 8)));
> -	out |= (temp_out & 0xFF) << (thres_index * 8);
> +	update_ptps = store_ptps;
> +	bitmap_set_value8(&update_ptps, temp_out & 0xFF, thres_index * 8);
> +	out = update_ptps;

+ blank line?

After this change it seems we may drop temp_out and use out instead.

> -	out = (out & dts->temp_mask) >> dts->temp_shift;
> +	temp_raw = out;
> +	out = bitmap_get_value8(&temp_raw, dts->id * 8);

>  	out -= SOC_DTS_TJMAX_ENCODING;
>  	*temp = sensors->tj_max - out * 1000;

We may also join these together, though it's up to you.

>  	char name[10];
>  	int trip_count = 0;

> +	int writable_trip_count = 0;

Perhaps move it after next line, or before previous one.

>  	int trip_mask = 0;
>  	u32 store_ptps;
>  	int ret;

> -	int i;
> +	unsigned long i;

We may skip this change, but if we go with it, better to place before
'int ret;' line.

> +	unsigned long trip;
> +	unsigned long ptps;

I would group each of these with relative group of definitions above.

>  	if (notification_support) {
>  		trip_count = min(SOC_MAX_DTS_TRIPS, trip_cnt);
> +		writable_trip_count = trip_count - read_only_trip_cnt;

Maybe writable_trip_count -> writable_trip_cnt? (in align with r/o one).

> +		trip_mask = GENMASK(writable_trip_count - 1, 0);
>  	}

-- 
With Best Regards,
Andy Shevchenko



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-10-07  8:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 15:10 [PATCH v16 00/14] Introduce the for_each_set_clump8 macro William Breathitt Gray
2019-10-06 15:10 ` [PATCH v16 01/14] bitops: " William Breathitt Gray
2019-10-07  8:21   ` Andy Shevchenko
2019-10-07 15:18     ` William Breathitt Gray
2019-10-06 15:10 ` [PATCH v16 02/14] lib/test_bitmap.c: Add for_each_set_clump8 test cases William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 03/14] gpio: 104-dio-48e: Utilize for_each_set_clump8 macro William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 04/14] gpio: 104-idi-48: " William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 05/14] gpio: gpio-mm: " William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 06/14] gpio: ws16c48: " William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 07/14] gpio: pci-idio-16: " William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 08/14] gpio: pcie-idio-24: " William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 09/14] gpio: uniphier: " William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 10/14] gpio: 74x164: Utilize the " William Breathitt Gray
2019-10-07  8:24   ` Andy Shevchenko
2019-10-06 15:11 ` [PATCH v16 11/14] thermal: intel: intel_soc_dts_iosf: Utilize " William Breathitt Gray
2019-10-07  8:44   ` Andy Shevchenko [this message]
2019-10-06 15:11 ` [PATCH v16 12/14] gpio: pisosr: Utilize the " William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 13/14] gpio: max3191x: " William Breathitt Gray
2019-10-06 15:11 ` [PATCH v16 14/14] gpio: pca953x: " William Breathitt Gray
2019-10-07  8:45   ` Andy Shevchenko

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=20191007084429.GN32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=geert@linux-m68k.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=lukas@wunner.de \
    --cc=morten.tiljeset@prevas.dk \
    --cc=preid@electromag.com.au \
    --cc=sean.nyekjaer@prevas.dk \
    --cc=vilhelm.gray@gmail.com \
    --cc=yamada.masahiro@socionext.com \
    /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;
as well as URLs for NNTP newsgroup(s).