From: Ray Jui <rjui@broadcom.com>
To: Andrzej Hajda <a.hajda@samsung.com>,
Linus Walleij <linus.walleij@linaro.org>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"moderated list:BROADCOM IPROC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
open list <linux-kernel@vger.kernel.org>,
Yendapally Reddy Dhananjaya Reddy <yrdreddy@broadcom.com>
Subject: Re: [PATCH] pinctrl: nsp-gpio: fix type of iterator
Date: Wed, 23 Dec 2015 14:35:57 -0800 [thread overview]
Message-ID: <567B21CD.9090900@broadcom.com> (raw)
In-Reply-To: <1450867041-729-2-git-send-email-a.hajda@samsung.com>
+ Reddy
On 12/23/2015 2:37 AM, Andrzej Hajda wrote:
> Iterator i declared as unsigned is always non-negative so the
> loop will never end.
>
> The problem has been detected using proposed semantic patch
> scripts/coccinelle/tests/unsigned_lesser_than_zero.cocci [1].
>
> [1]: http://permalink.gmane.org/gmane.linux.kernel/2038576
>
> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
> ---
> drivers/pinctrl/bcm/pinctrl-nsp-gpio.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/bcm/pinctrl-nsp-gpio.c b/drivers/pinctrl/bcm/pinctrl-nsp-gpio.c
> index 34648f6..ad5b04c 100644
> --- a/drivers/pinctrl/bcm/pinctrl-nsp-gpio.c
> +++ b/drivers/pinctrl/bcm/pinctrl-nsp-gpio.c
> @@ -439,7 +439,8 @@ static int nsp_gpio_set_strength(struct nsp_gpio *chip, unsigned gpio,
> static int nsp_gpio_get_strength(struct nsp_gpio *chip, unsigned gpio,
> u16 *strength)
> {
> - unsigned int i, offset, shift;
> + unsigned int offset, shift;
> + int i;
> u32 val;
> unsigned long flags;
>
>
The fix is a valid fix. And at the same time it exposes other potential
issues in the driver. I just found the loop used in _set_strength and
_get_strength is inconsistent:
In _set_strength:
427 for (i = GPIO_DRV_STRENGTH_BITS; i > 0; i--) {
For i to start at GPIO_DRV_STRENGTH_BITS, it seems to be wrong.
428 val = readl(chip->io_ctrl + offset);
429 val &= ~BIT(shift);
430 val |= ((strength >> (i-1)) & 0x1) << shift;
431 writel(val, chip->io_ctrl + offset);
432 offset += 4;
433 }
In _get_strength:
451 for (i = (GPIO_DRV_STRENGTH_BITS - 1); i >= 0; i--) {
452 val = readl(chip->io_ctrl + offset) & BIT(shift);
453 val >>= shift;
454 *strength += (val << i);
455 offset += 4;
456 }
Reddy, could you please review and comment?
Thanks,
Ray
WARNING: multiple messages have this Message-ID (diff)
From: rjui@broadcom.com (Ray Jui)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: nsp-gpio: fix type of iterator
Date: Wed, 23 Dec 2015 14:35:57 -0800 [thread overview]
Message-ID: <567B21CD.9090900@broadcom.com> (raw)
In-Reply-To: <1450867041-729-2-git-send-email-a.hajda@samsung.com>
+ Reddy
On 12/23/2015 2:37 AM, Andrzej Hajda wrote:
> Iterator i declared as unsigned is always non-negative so the
> loop will never end.
>
> The problem has been detected using proposed semantic patch
> scripts/coccinelle/tests/unsigned_lesser_than_zero.cocci [1].
>
> [1]: http://permalink.gmane.org/gmane.linux.kernel/2038576
>
> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
> ---
> drivers/pinctrl/bcm/pinctrl-nsp-gpio.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/bcm/pinctrl-nsp-gpio.c b/drivers/pinctrl/bcm/pinctrl-nsp-gpio.c
> index 34648f6..ad5b04c 100644
> --- a/drivers/pinctrl/bcm/pinctrl-nsp-gpio.c
> +++ b/drivers/pinctrl/bcm/pinctrl-nsp-gpio.c
> @@ -439,7 +439,8 @@ static int nsp_gpio_set_strength(struct nsp_gpio *chip, unsigned gpio,
> static int nsp_gpio_get_strength(struct nsp_gpio *chip, unsigned gpio,
> u16 *strength)
> {
> - unsigned int i, offset, shift;
> + unsigned int offset, shift;
> + int i;
> u32 val;
> unsigned long flags;
>
>
The fix is a valid fix. And at the same time it exposes other potential
issues in the driver. I just found the loop used in _set_strength and
_get_strength is inconsistent:
In _set_strength:
427 for (i = GPIO_DRV_STRENGTH_BITS; i > 0; i--) {
For i to start at GPIO_DRV_STRENGTH_BITS, it seems to be wrong.
428 val = readl(chip->io_ctrl + offset);
429 val &= ~BIT(shift);
430 val |= ((strength >> (i-1)) & 0x1) << shift;
431 writel(val, chip->io_ctrl + offset);
432 offset += 4;
433 }
In _get_strength:
451 for (i = (GPIO_DRV_STRENGTH_BITS - 1); i >= 0; i--) {
452 val = readl(chip->io_ctrl + offset) & BIT(shift);
453 val >>= shift;
454 *strength += (val << i);
455 offset += 4;
456 }
Reddy, could you please review and comment?
Thanks,
Ray
next prev parent reply other threads:[~2015-12-23 22:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 10:37 [PATCH] cpufreq/scpi: fix handling return value of topology_physical_package_id Andrzej Hajda
2015-12-23 10:37 ` Andrzej Hajda
2015-12-23 10:37 ` Andrzej Hajda
2015-12-23 10:37 ` [PATCH] pinctrl: nsp-gpio: fix type of iterator Andrzej Hajda
2015-12-23 10:37 ` Andrzej Hajda
2015-12-23 10:37 ` Andrzej Hajda
2015-12-23 22:35 ` Ray Jui [this message]
2015-12-23 22:35 ` Ray Jui
2015-12-24 5:33 ` Yendapally Reddy Dhananjaya Reddy
2015-12-24 5:33 ` Yendapally Reddy Dhananjaya Reddy
2015-12-24 9:03 ` Linus Walleij
2015-12-24 9:03 ` Linus Walleij
2015-12-23 10:37 ` [PATCH] NFC: nci: fix handling return value of nci_hci_create_pipe Andrzej Hajda
2015-12-23 10:37 ` [PATCH] ASoC: rsnd: fix usrcnt decrementing bug Andrzej Hajda
2015-12-23 10:37 ` Andrzej Hajda
2015-12-24 0:04 ` Kuninori Morimoto
2015-12-24 5:56 ` Andrzej Hajda
2015-12-24 6:14 ` Kuninori Morimoto
2015-12-24 6:14 ` Kuninori Morimoto
2015-12-24 7:02 ` [PATCH v2] " Andrzej Hajda
2015-12-24 7:02 ` Andrzej Hajda
2015-12-24 7:38 ` Kuninori Morimoto
2015-12-30 17:12 ` Mark Brown
2015-12-30 17:12 ` Mark Brown
2015-12-30 18:05 ` Applied "ASoC: rsnd: fix usrcnt decrementing bug" to the asoc tree Mark Brown
2015-12-23 10:41 ` [PATCH] cpufreq/scpi: fix handling return value of topology_physical_package_id Viresh Kumar
2015-12-23 10:41 ` Viresh Kumar
2015-12-23 10:48 ` Sudeep Holla
2015-12-23 10:48 ` Sudeep Holla
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=567B21CD.9090900@broadcom.com \
--to=rjui@broadcom.com \
--cc=a.hajda@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jonmason@broadcom.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sbranden@broadcom.com \
--cc=yrdreddy@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.