All of lore.kernel.org
 help / color / mirror / Atom feed
From: Syed Nayyar Waris <syednwaris@gmail.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Michal Simek <michals@xilinx.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	William Breathitt Gray <vilhelm.gray@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Robert Richter <rrichter@marvell.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Amit Kucheria <amit.kucheria@verdurent.com>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	linux-gpio <linux-gpio@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	arm-soc <linux-arm-kernel@lists.infradead.org>,
	linux-pm <linux-pm@vger.kernel.org>,
	Srinivas Goud <sgoud@xilinx.com>,
	Srinivas Neeli <sneeli@xilinx.com>
Subject: Re: [PATCH v3 3/3] gpio: xilinx: Utilize generic bitmap_get_value and _set_value
Date: Thu, 1 Apr 2021 16:45:52 +0530	[thread overview]
Message-ID: <CACG_h5q6P5NiNByttQ-NZvq8x3GCTKfSU=Yyywk7PcO6_=i2Mw@mail.gmail.com> (raw)
In-Reply-To: <DM6PR02MB53863852A28F782B0942ECD8AF7C9@DM6PR02MB5386.namprd02.prod.outlook.com>

On Wed, Mar 31, 2021 at 8:56 PM Srinivas Neeli <sneeli@xilinx.com> wrote:
>
> Hi,
>
> > -----Original Message-----
> > From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > Sent: Friday, March 26, 2021 10:58 PM
> > To: Michal Simek <michals@xilinx.com>
> > Cc: Syed Nayyar Waris <syednwaris@gmail.com>; Srinivas Neeli
> > <sneeli@xilinx.com>; Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com>; William Breathitt Gray
> > <vilhelm.gray@gmail.com>; Arnd Bergmann <arnd@arndb.de>; Robert
> > Richter <rrichter@marvell.com>; Linus Walleij <linus.walleij@linaro.org>;
> > Masahiro Yamada <yamada.masahiro@socionext.com>; Andrew Morton
> > <akpm@linux-foundation.org>; Zhang Rui <rui.zhang@intel.com>; Daniel
> > Lezcano <daniel.lezcano@linaro.org>; Amit Kucheria
> > <amit.kucheria@verdurent.com>; Linux-Arch <linux-arch@vger.kernel.org>;
> > linux-gpio <linux-gpio@vger.kernel.org>; LKML <linux-
> > kernel@vger.kernel.org>; arm-soc <linux-arm-kernel@lists.infradead.org>;
> > linux-pm <linux-pm@vger.kernel.org>; Srinivas Goud <sgoud@xilinx.com>
> > Subject: Re: [PATCH v3 3/3] gpio: xilinx: Utilize generic bitmap_get_value and
> > _set_value
> >
> > On Mon, Mar 8, 2021 at 8:13 AM Michal Simek <michal.simek@xilinx.com>
> > wrote:
> > >
> > >
> > >
> > > On 3/6/21 3:06 PM, Syed Nayyar Waris wrote:
> > > > This patch reimplements the xgpio_set_multiple() function in
> > > > drivers/gpio/gpio-xilinx.c to use the new generic functions:
> > > > bitmap_get_value() and bitmap_set_value(). The code is now simpler
> > > > to read and understand. Moreover, instead of looping for each bit in
> > > > xgpio_set_multiple() function, now we can check each channel at a
> > > > time and save cycles.
> > > >
> > > > Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > > > Cc: Michal Simek <michal.simek@xilinx.com>
> > > > Signed-off-by: Syed Nayyar Waris <syednwaris@gmail.com>
> > > > Acked-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> > > > ---
> > > >  drivers/gpio/gpio-xilinx.c | 63
> > > > +++++++++++++++++++-------------------
> > > >  1 file changed, 32 insertions(+), 31 deletions(-)
> > > >
> > > > diff --git a/drivers/gpio/gpio-xilinx.c b/drivers/gpio/gpio-xilinx.c
> > > > index be539381fd82..8445e69cf37b 100644
> > > > --- a/drivers/gpio/gpio-xilinx.c
> > > > +++ b/drivers/gpio/gpio-xilinx.c
> > > > @@ -15,6 +15,7 @@
> > > >  #include <linux/of_device.h>
> > > >  #include <linux/of_platform.h>
> > > >  #include <linux/slab.h>
> > > > +#include "gpiolib.h"
> > > >
> > > >  /* Register Offset Definitions */
> > > >  #define XGPIO_DATA_OFFSET   (0x0)    /* Data register  */
> > > > @@ -141,37 +142,37 @@ static void xgpio_set_multiple(struct
> > > > gpio_chip *gc, unsigned long *mask,  {
> > > >       unsigned long flags;
> > > >       struct xgpio_instance *chip = gpiochip_get_data(gc);
> > > > -     int index = xgpio_index(chip, 0);
> > > > -     int offset, i;
> > > > -
> > > > -     spin_lock_irqsave(&chip->gpio_lock[index], flags);
> > > > -
> > > > -     /* Write to GPIO signals */
> > > > -     for (i = 0; i < gc->ngpio; i++) {
> > > > -             if (*mask == 0)
> > > > -                     break;
> > > > -             /* Once finished with an index write it out to the register */
> > > > -             if (index !=  xgpio_index(chip, i)) {
> > > > -                     xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET +
> > > > -                                    index * XGPIO_CHANNEL_OFFSET,
> > > > -                                    chip->gpio_state[index]);
> > > > -                     spin_unlock_irqrestore(&chip->gpio_lock[index], flags);
> > > > -                     index =  xgpio_index(chip, i);
> > > > -                     spin_lock_irqsave(&chip->gpio_lock[index], flags);
> > > > -             }
> > > > -             if (__test_and_clear_bit(i, mask)) {
> > > > -                     offset =  xgpio_offset(chip, i);
> > > > -                     if (test_bit(i, bits))
> > > > -                             chip->gpio_state[index] |= BIT(offset);
> > > > -                     else
> > > > -                             chip->gpio_state[index] &= ~BIT(offset);
> > > > -             }
> > > > -     }
> > > > -
> > > > -     xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET +
> > > > -                    index * XGPIO_CHANNEL_OFFSET, chip->gpio_state[index]);
> > > > -
> > > > -     spin_unlock_irqrestore(&chip->gpio_lock[index], flags);
> > > > +     u32 *const state = chip->gpio_state;
> > > > +     unsigned int *const width = chip->gpio_width;
> > > > +
> > > > +     DECLARE_BITMAP(old, 64);
> > > > +     DECLARE_BITMAP(new, 64);
> > > > +     DECLARE_BITMAP(changed, 64);
> > > > +
> > > > +     spin_lock_irqsave(&chip->gpio_lock[0], flags);
> > > > +     spin_lock(&chip->gpio_lock[1]);
> > > > +
> > > > +     bitmap_set_value(old, 64, state[0], width[0], 0);
> > > > +     bitmap_set_value(old, 64, state[1], width[1], width[0]);
> > > > +     bitmap_replace(new, old, bits, mask, gc->ngpio);
> > > > +
> > > > +     bitmap_set_value(old, 64, state[0], 32, 0);
> > > > +     bitmap_set_value(old, 64, state[1], 32, 32);
> > > > +     state[0] = bitmap_get_value(new, 0, width[0]);
> > > > +     state[1] = bitmap_get_value(new, width[0], width[1]);
> > > > +     bitmap_set_value(new, 64, state[0], 32, 0);
> > > > +     bitmap_set_value(new, 64, state[1], 32, 32);
> > > > +     bitmap_xor(changed, old, new, 64);
> > > > +
> > > > +     if (((u32 *)changed)[0])
> > > > +             xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET,
> > > > +                             state[0]);
> > > > +     if (((u32 *)changed)[1])
> > > > +             xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET +
> > > > +                             XGPIO_CHANNEL_OFFSET, state[1]);
> > > > +
> > > > +     spin_unlock(&chip->gpio_lock[1]);
> > > > +     spin_unlock_irqrestore(&chip->gpio_lock[0], flags);
> > > >  }
> > > >
> > > >  /**
> > > >
> > >
> > > Srinivas N: Can you please test this code?
> > >
> > > Thanks,
> > > Michal
> >
> > Hey, any chance of getting that Tested-by?
> I tested patches with few modifications in code (spin_lock handling and merge conflict).
> functionality wise it's working fine.
>
> >
> > Bart

Hi Bartosz,

May I please know the URL of the tree that you are using. I had been
using the tree below for submitting this patchset on GPIO to you.
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git

I think I am using the wrong tree. On which tree should I base my
patches on for my next  (v4) submission? Should I use the tree below?
:
https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git

Regards
Syed Nayyar Waris

WARNING: multiple messages have this Message-ID (diff)
From: Syed Nayyar Waris <syednwaris@gmail.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Michal Simek <michals@xilinx.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	 William Breathitt Gray <vilhelm.gray@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Robert Richter <rrichter@marvell.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Zhang Rui <rui.zhang@intel.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	 Amit Kucheria <amit.kucheria@verdurent.com>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	 linux-gpio <linux-gpio@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	 arm-soc <linux-arm-kernel@lists.infradead.org>,
	linux-pm <linux-pm@vger.kernel.org>,
	 Srinivas Goud <sgoud@xilinx.com>,
	Srinivas Neeli <sneeli@xilinx.com>
Subject: Re: [PATCH v3 3/3] gpio: xilinx: Utilize generic bitmap_get_value and _set_value
Date: Thu, 1 Apr 2021 16:45:52 +0530	[thread overview]
Message-ID: <CACG_h5q6P5NiNByttQ-NZvq8x3GCTKfSU=Yyywk7PcO6_=i2Mw@mail.gmail.com> (raw)
In-Reply-To: <DM6PR02MB53863852A28F782B0942ECD8AF7C9@DM6PR02MB5386.namprd02.prod.outlook.com>

On Wed, Mar 31, 2021 at 8:56 PM Srinivas Neeli <sneeli@xilinx.com> wrote:
>
> Hi,
>
> > -----Original Message-----
> > From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > Sent: Friday, March 26, 2021 10:58 PM
> > To: Michal Simek <michals@xilinx.com>
> > Cc: Syed Nayyar Waris <syednwaris@gmail.com>; Srinivas Neeli
> > <sneeli@xilinx.com>; Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com>; William Breathitt Gray
> > <vilhelm.gray@gmail.com>; Arnd Bergmann <arnd@arndb.de>; Robert
> > Richter <rrichter@marvell.com>; Linus Walleij <linus.walleij@linaro.org>;
> > Masahiro Yamada <yamada.masahiro@socionext.com>; Andrew Morton
> > <akpm@linux-foundation.org>; Zhang Rui <rui.zhang@intel.com>; Daniel
> > Lezcano <daniel.lezcano@linaro.org>; Amit Kucheria
> > <amit.kucheria@verdurent.com>; Linux-Arch <linux-arch@vger.kernel.org>;
> > linux-gpio <linux-gpio@vger.kernel.org>; LKML <linux-
> > kernel@vger.kernel.org>; arm-soc <linux-arm-kernel@lists.infradead.org>;
> > linux-pm <linux-pm@vger.kernel.org>; Srinivas Goud <sgoud@xilinx.com>
> > Subject: Re: [PATCH v3 3/3] gpio: xilinx: Utilize generic bitmap_get_value and
> > _set_value
> >
> > On Mon, Mar 8, 2021 at 8:13 AM Michal Simek <michal.simek@xilinx.com>
> > wrote:
> > >
> > >
> > >
> > > On 3/6/21 3:06 PM, Syed Nayyar Waris wrote:
> > > > This patch reimplements the xgpio_set_multiple() function in
> > > > drivers/gpio/gpio-xilinx.c to use the new generic functions:
> > > > bitmap_get_value() and bitmap_set_value(). The code is now simpler
> > > > to read and understand. Moreover, instead of looping for each bit in
> > > > xgpio_set_multiple() function, now we can check each channel at a
> > > > time and save cycles.
> > > >
> > > > Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > > > Cc: Michal Simek <michal.simek@xilinx.com>
> > > > Signed-off-by: Syed Nayyar Waris <syednwaris@gmail.com>
> > > > Acked-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> > > > ---
> > > >  drivers/gpio/gpio-xilinx.c | 63
> > > > +++++++++++++++++++-------------------
> > > >  1 file changed, 32 insertions(+), 31 deletions(-)
> > > >
> > > > diff --git a/drivers/gpio/gpio-xilinx.c b/drivers/gpio/gpio-xilinx.c
> > > > index be539381fd82..8445e69cf37b 100644
> > > > --- a/drivers/gpio/gpio-xilinx.c
> > > > +++ b/drivers/gpio/gpio-xilinx.c
> > > > @@ -15,6 +15,7 @@
> > > >  #include <linux/of_device.h>
> > > >  #include <linux/of_platform.h>
> > > >  #include <linux/slab.h>
> > > > +#include "gpiolib.h"
> > > >
> > > >  /* Register Offset Definitions */
> > > >  #define XGPIO_DATA_OFFSET   (0x0)    /* Data register  */
> > > > @@ -141,37 +142,37 @@ static void xgpio_set_multiple(struct
> > > > gpio_chip *gc, unsigned long *mask,  {
> > > >       unsigned long flags;
> > > >       struct xgpio_instance *chip = gpiochip_get_data(gc);
> > > > -     int index = xgpio_index(chip, 0);
> > > > -     int offset, i;
> > > > -
> > > > -     spin_lock_irqsave(&chip->gpio_lock[index], flags);
> > > > -
> > > > -     /* Write to GPIO signals */
> > > > -     for (i = 0; i < gc->ngpio; i++) {
> > > > -             if (*mask == 0)
> > > > -                     break;
> > > > -             /* Once finished with an index write it out to the register */
> > > > -             if (index !=  xgpio_index(chip, i)) {
> > > > -                     xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET +
> > > > -                                    index * XGPIO_CHANNEL_OFFSET,
> > > > -                                    chip->gpio_state[index]);
> > > > -                     spin_unlock_irqrestore(&chip->gpio_lock[index], flags);
> > > > -                     index =  xgpio_index(chip, i);
> > > > -                     spin_lock_irqsave(&chip->gpio_lock[index], flags);
> > > > -             }
> > > > -             if (__test_and_clear_bit(i, mask)) {
> > > > -                     offset =  xgpio_offset(chip, i);
> > > > -                     if (test_bit(i, bits))
> > > > -                             chip->gpio_state[index] |= BIT(offset);
> > > > -                     else
> > > > -                             chip->gpio_state[index] &= ~BIT(offset);
> > > > -             }
> > > > -     }
> > > > -
> > > > -     xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET +
> > > > -                    index * XGPIO_CHANNEL_OFFSET, chip->gpio_state[index]);
> > > > -
> > > > -     spin_unlock_irqrestore(&chip->gpio_lock[index], flags);
> > > > +     u32 *const state = chip->gpio_state;
> > > > +     unsigned int *const width = chip->gpio_width;
> > > > +
> > > > +     DECLARE_BITMAP(old, 64);
> > > > +     DECLARE_BITMAP(new, 64);
> > > > +     DECLARE_BITMAP(changed, 64);
> > > > +
> > > > +     spin_lock_irqsave(&chip->gpio_lock[0], flags);
> > > > +     spin_lock(&chip->gpio_lock[1]);
> > > > +
> > > > +     bitmap_set_value(old, 64, state[0], width[0], 0);
> > > > +     bitmap_set_value(old, 64, state[1], width[1], width[0]);
> > > > +     bitmap_replace(new, old, bits, mask, gc->ngpio);
> > > > +
> > > > +     bitmap_set_value(old, 64, state[0], 32, 0);
> > > > +     bitmap_set_value(old, 64, state[1], 32, 32);
> > > > +     state[0] = bitmap_get_value(new, 0, width[0]);
> > > > +     state[1] = bitmap_get_value(new, width[0], width[1]);
> > > > +     bitmap_set_value(new, 64, state[0], 32, 0);
> > > > +     bitmap_set_value(new, 64, state[1], 32, 32);
> > > > +     bitmap_xor(changed, old, new, 64);
> > > > +
> > > > +     if (((u32 *)changed)[0])
> > > > +             xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET,
> > > > +                             state[0]);
> > > > +     if (((u32 *)changed)[1])
> > > > +             xgpio_writereg(chip->regs + XGPIO_DATA_OFFSET +
> > > > +                             XGPIO_CHANNEL_OFFSET, state[1]);
> > > > +
> > > > +     spin_unlock(&chip->gpio_lock[1]);
> > > > +     spin_unlock_irqrestore(&chip->gpio_lock[0], flags);
> > > >  }
> > > >
> > > >  /**
> > > >
> > >
> > > Srinivas N: Can you please test this code?
> > >
> > > Thanks,
> > > Michal
> >
> > Hey, any chance of getting that Tested-by?
> I tested patches with few modifications in code (spin_lock handling and merge conflict).
> functionality wise it's working fine.
>
> >
> > Bart

Hi Bartosz,

May I please know the URL of the tree that you are using. I had been
using the tree below for submitting this patchset on GPIO to you.
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git

I think I am using the wrong tree. On which tree should I base my
patches on for my next  (v4) submission? Should I use the tree below?
:
https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git

Regards
Syed Nayyar Waris

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

  reply	other threads:[~2021-04-01 17:55 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 14:01 [PATCH v3 0/3] Introduce the for_each_set_nbits macro Syed Nayyar Waris
2021-03-06 14:01 ` Syed Nayyar Waris
2021-03-06 14:03 ` [PATCH v3 1/3] gpiolib: " Syed Nayyar Waris
2021-03-06 14:03   ` Syed Nayyar Waris
2021-03-06 14:05 ` [PATCH v3 2/3] gpio: thunderx: Utilize " Syed Nayyar Waris
2021-03-06 14:05   ` Syed Nayyar Waris
2021-03-06 14:06 ` [PATCH v3 3/3] gpio: xilinx: Utilize generic bitmap_get_value and _set_value Syed Nayyar Waris
2021-03-06 14:06   ` Syed Nayyar Waris
2021-03-08  7:13   ` Michal Simek
2021-03-08  7:13     ` Michal Simek
2021-03-26 17:27     ` Bartosz Golaszewski
2021-03-26 17:27       ` Bartosz Golaszewski
2021-03-31 15:26       ` Srinivas Neeli
2021-03-31 15:26         ` Srinivas Neeli
2021-04-01 11:15         ` Syed Nayyar Waris [this message]
2021-04-01 11:15           ` Syed Nayyar Waris
2021-04-01 12:51           ` Bartosz Golaszewski
2021-04-01 12:51             ` Bartosz Golaszewski
2021-03-26 17:57   ` Andy Shevchenko
2021-03-26 17:57     ` Andy Shevchenko
2021-04-02  9:40     ` Syed Nayyar Waris
2021-04-02  9:40       ` Syed Nayyar Waris
2021-03-26 18:02   ` Andy Shevchenko
2021-03-26 18:02     ` Andy Shevchenko
2021-03-26 22:12     ` Syed Nayyar Waris
2021-03-26 22:12       ` Syed Nayyar Waris
     [not found]       ` <CAHp75VfDZbJjCOEGdHc=-D6W8_7m2=CinXj-itwn6hvoVqdWYQ@mail.gmail.com>
2021-03-27 12:02         ` William Breathitt Gray
2021-03-27 12:02           ` William Breathitt Gray
2021-03-27 16:35           ` Andy Shevchenko
2021-03-27 16:35             ` Andy Shevchenko
2021-04-01 17:50             ` Syed Nayyar Waris
2021-04-01 17:50               ` Syed Nayyar Waris
2021-03-29 15:24   ` Andy Shevchenko
2021-03-29 15:24     ` Andy Shevchenko
2021-04-01 17:47     ` Syed Nayyar Waris
2021-04-01 17:47       ` Syed Nayyar Waris
2021-04-02 10:07     ` Syed Nayyar Waris
2021-04-02 10:07       ` Syed Nayyar Waris

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='CACG_h5q6P5NiNByttQ-NZvq8x3GCTKfSU=Yyywk7PcO6_=i2Mw@mail.gmail.com' \
    --to=syednwaris@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=amit.kucheria@verdurent.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=bgolaszewski@baylibre.com \
    --cc=daniel.lezcano@linaro.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=michals@xilinx.com \
    --cc=rrichter@marvell.com \
    --cc=rui.zhang@intel.com \
    --cc=sgoud@xilinx.com \
    --cc=sneeli@xilinx.com \
    --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 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.