From: Hans de Goede <hdegoede@redhat.com>
To: David Laight <David.Laight@ACULAB.COM>,
'Ricardo Ribalda' <ribalda@chromium.org>,
Benoit Parrot <bparrot@ti.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andy Shevchenko <andy@kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>
Subject: Re: [PATCH 3/3] media: atomisp: Use max() macros
Date: Mon, 30 Sep 2024 10:27:51 +0200 [thread overview]
Message-ID: <8062d702-9426-408e-b3e5-3a33d81d2927@redhat.com> (raw)
In-Reply-To: <c183afe8986d444a8e777ae0b9bb9189@AcuMS.aculab.com>
Hi,
On 29-Sep-24 11:34 PM, David Laight wrote:
> From: Ricardo Ribalda
>> Sent: 27 September 2024 10:42
>>
>> The max() macro produce nicer code and also fixes the following cocci
>> errors:
>>
>> drivers/staging/media/atomisp/pci/sh_css_frac.h:40:17-18: WARNING opportunity for max()
>> drivers/staging/media/atomisp/pci/sh_css_frac.h:50:17-18: WARNING opportunity for max()
>>
>> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
>> ---
>> drivers/staging/media/atomisp/pci/sh_css_frac.h | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/staging/media/atomisp/pci/sh_css_frac.h
>> b/drivers/staging/media/atomisp/pci/sh_css_frac.h
>> index 8ba65161f7a9..9642506d2388 100644
>> --- a/drivers/staging/media/atomisp/pci/sh_css_frac.h
>> +++ b/drivers/staging/media/atomisp/pci/sh_css_frac.h
>> @@ -37,7 +37,7 @@ static inline int sDIGIT_FITTING(int v, int a, int b)
>> int fit_shift = sFRACTION_BITS_FITTING(a) - b;
>>
>> v >>= sSHIFT;
>
> IIRC right shifts of signed values are undefined.
> (C does not require a cpu to have a right shift that replicates the
> sign bit.)
>
>> - v >>= fit_shift > 0 ? fit_shift : 0;
>> + v >>= max(fit_shift, 0);
>
> If the shift isn't done the return value is garbage.
> So the code better not let it happen.
> In which case you might as well let the cpu generate a (different)
> random value - so delete the conditional.
Given the history of this code I would no be surprised if some
weird corner case actually relies on the check, so NACK for
dropping the conditional.
>
>>
>> return clamp_t(int, v, sISP_VAL_MIN, sISP_VAL_MAX);
>
> all three values seem to be 'int' - so no need for the _t variant
> and all the associated casts.
sDIGIT_FITTING() originally was a macro with a bunch of max() + min()
calls nested leading to it expanding to a lot of code after running it
through the pre-processor. When converting this to a static online to
choice was made to with clamp_t() to avoid the overhead of the extra
type checks in regular clamp().
Regards,
Hans
>
>> }
>> @@ -47,7 +47,7 @@ static inline unsigned int uDIGIT_FITTING(unsigned int v, int a, int b)
>> int fit_shift = uFRACTION_BITS_FITTING(a) - b;
>>
>> v >>= uSHIFT;
>> - v >>= fit_shift > 0 ? fit_shift : 0;
>> + v >>= max(fit_shift, 0);
>>
>> return clamp_t(unsigned int, v, uISP_VAL_MIN, uISP_VAL_MAX);
>
> as above, but it is just min(v, iISP_VAL_MAX)
>
> David
>
>> }
>>
>> --
>> 2.46.1.824.gd892dcdcdd-goog
>>
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
prev parent reply other threads:[~2024-09-30 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 9:42 [PATCH 0/3] media: static-analyzers: Fix 6.12-rc1 cocci warnings Ricardo Ribalda
2024-09-27 9:42 ` [PATCH 1/3] media: ti: cal: Use str_up_down() Ricardo Ribalda
2024-09-27 9:56 ` Andy Shevchenko
2024-09-27 9:42 ` [PATCH 2/3] staging: media: ipu3:Use str_down_up() Ricardo Ribalda
2024-09-27 9:55 ` Andy Shevchenko
2024-09-27 9:42 ` [PATCH 3/3] media: atomisp: Use max() macros Ricardo Ribalda
2024-09-27 9:54 ` Andy Shevchenko
2024-09-27 10:00 ` Hans Verkuil
2024-09-29 21:34 ` David Laight
2024-09-30 8:27 ` Hans de Goede [this message]
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=8062d702-9426-408e-b3e5-3a33d81d2927@redhat.com \
--to=hdegoede@redhat.com \
--cc=David.Laight@ACULAB.COM \
--cc=andy@kernel.org \
--cc=bingbu.cao@intel.com \
--cc=bparrot@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@intel.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
all inboxes | Powered by JetHome®