linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linus Walleij <linus.walleij@linaro.org>,
	Jonas Gorski <jonas.gorski@gmail.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] pinctrl: bcm: bcm6362: fix warning
Date: Tue, 30 Mar 2021 15:41:00 +0200	[thread overview]
Message-ID: <63f54c37-757d-7eff-f2e5-77ce374185e9@gmail.com> (raw)
In-Reply-To: <CAHp75VdCLuS-0YL6+_vz5GqJC9N0AOiuYazkB1VNvbsPD78NAA@mail.gmail.com>

Hi Andy,

El 30/03/2021 a las 12:55, Andy Shevchenko escribió:
> On Tue, Mar 30, 2021 at 1:33 PM Álvaro Fernández Rojas
> <noltari@gmail.com> wrote:
>>
>> The current implementation of bcm6362_set_gpio() produces the following
>> warning on x86_64:
>> drivers/pinctrl/bcm/pinctrl-bcm6362.c: In function 'bcm6362_set_gpio':
>> drivers/pinctrl/bcm/pinctrl-bcm6362.c:503:8: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
>>    503 |        (uint32_t) desc->drv_data, 0);
>>        |        ^
>>
>> Modify the code to make it similar to bcm63268_set_gpio() in order to fix
>> the warning.
> 
> Seems good to me, thanks!
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> 
>> Fixes: 705791e23ecd ("pinctrl: add a pincontrol driver for BCM6362")
>> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
>> ---
> 
> Missed changelog here.

Yes, sorry about that but I added it to v1 patch by mistake... ;D
  v2: use uintptr_t, remove unneeded space and modify put
  regmap_update_bits() call on a single line.

> 
>>   drivers/pinctrl/bcm/pinctrl-bcm6362.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/pinctrl/bcm/pinctrl-bcm6362.c b/drivers/pinctrl/bcm/pinctrl-bcm6362.c
>> index eb7ec80353e9..40ef495b6301 100644
>> --- a/drivers/pinctrl/bcm/pinctrl-bcm6362.c
>> +++ b/drivers/pinctrl/bcm/pinctrl-bcm6362.c
>> @@ -496,11 +496,11 @@ static int bcm6362_pinctrl_get_groups(struct pinctrl_dev *pctldev,
>>   static void bcm6362_set_gpio(struct bcm63xx_pinctrl *pc, unsigned pin)
>>   {
>>          const struct pinctrl_pin_desc *desc = &bcm6362_pins[pin];
>> +       unsigned int basemode = (uintptr_t)desc->drv_data;
>>          unsigned int mask = bcm63xx_bank_pin(pin);
>>
>> -       if (desc->drv_data)
>> -               regmap_update_bits(pc->regs, BCM6362_BASEMODE_REG,
>> -                                  (uint32_t) desc->drv_data, 0);
>> +       if (basemode)
>> +               regmap_update_bits(pc->regs, BCM6362_BASEMODE_REG, basemode, 0);
>>
>>          if (pin < BCM63XX_BANK_GPIOS) {
>>                  /* base mode 0 => gpio 1 => mux function */
>> --
>> 2.20.1
>>
> 
> 

Best regards,
Álvaro.

  reply	other threads:[~2021-03-30 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 10:32 [PATCH v2] pinctrl: bcm: bcm6362: fix warning Álvaro Fernández Rojas
2021-03-30 10:55 ` Andy Shevchenko
2021-03-30 13:41   ` Álvaro Fernández Rojas [this message]
2021-03-31 12:34 ` Linus Walleij

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=63f54c37-757d-7eff-f2e5-77ce374185e9@gmail.com \
    --to=noltari@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=jonas.gorski@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).