mbox series

[GIT,PULL] intel-gpio for 5.17-1

Message ID Ybn8pxv5xPgc5nGz@black.fi.intel.com
State New
Headers show
Series [GIT,PULL] intel-gpio for 5.17-1 | expand

Pull-request

git@gitolite.kernel.org:pub/scm/linux/kernel/git/andy/linux-gpio-intel.git tags/intel-gpio-v5.17-1

Message

Andy Shevchenko Dec. 15, 2021, 2:33 p.m. UTC
Hi Linux GPIO  maintainers,

Approximately a dozen of changes for v5.17 against Intel GPIO drivers and
GPIO ACPI library. It has ben a while in Linux Next without any error reported.

Thanks,

With Best Regards,
Andy Shevchenko

The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:

  Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/andy/linux-gpio-intel.git tags/intel-gpio-v5.17-1

for you to fetch changes up to 9d5f0f6644b1404f40266a2682add712dc9931f5:

  gpio: sch: fix typo in a comment (2021-12-13 13:29:09 +0200)

----------------------------------------------------------------
intel-gpio for v5.17-1

* Don't set type for IRQ already in use in case of ACPI
* Drop unused call from GPIO ACPI library
* Clean up ML IOH and PCH GPIO drivers to make it closer to each other
* Clarify use of register file version in DesignWare driver

The following is an automated git shortlog grouped by driver:

dwapb:
 -  clarify usage of the register file version

gpiolib:
 -  acpi: Unify debug and other messages format
 -  acpi: Do not set the IRQ type if the IRQ is already in use
 -  acpi: shrink devm_acpi_dev_add_driver_gpios()
 -  acpi: Remove never used devm_acpi_dev_remove_driver_gpios()

ml-ioh:
 -  Change whitespace to match gpio-pch.c
 -  Use BIT() to match gpio-pch.c
 -  Cache &pdev->dev to reduce repetition

pch:
 -  Cache &pdev->dev to reduce repetition
 -  Use .driver_data instead of checking Device IDs again

sch:
 -  fix typo in a comment

----------------------------------------------------------------
Andy Shevchenko (4):
      gpiolib: acpi: Remove never used devm_acpi_dev_remove_driver_gpios()
      gpiolib: acpi: shrink devm_acpi_dev_add_driver_gpios()
      gpiolib: acpi: Unify debug and other messages format
      gpio: dwapb: clarify usage of the register file version

Bjorn Helgaas (5):
      gpio: pch: Use .driver_data instead of checking Device IDs again
      gpio: pch: Cache &pdev->dev to reduce repetition
      gpio: ml-ioh: Cache &pdev->dev to reduce repetition
      gpio: ml-ioh: Use BIT() to match gpio-pch.c
      gpio: ml-ioh: Change whitespace to match gpio-pch.c

Hans de Goede (1):
      gpiolib: acpi: Do not set the IRQ type if the IRQ is already in use

Jason Wang (1):
      gpio: sch: fix typo in a comment

 drivers/gpio/gpio-dwapb.c     | 10 +++++----
 drivers/gpio/gpio-ml-ioh.c    | 52 +++++++++++++++++++++----------------------
 drivers/gpio/gpio-pch.c       | 42 +++++++++++++++++-----------------
 drivers/gpio/gpio-sch.c       |  2 +-
 drivers/gpio/gpiolib-acpi.c   | 51 ++++++++++++++++++------------------------
 include/linux/gpio/consumer.h |  2 --
 6 files changed, 75 insertions(+), 84 deletions(-)

Comments

Bartosz Golaszewski Dec. 16, 2021, 9:14 a.m. UTC | #1
On Wed, Dec 15, 2021 at 3:33 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> Hi Linux GPIO  maintainers,
>
> Approximately a dozen of changes for v5.17 against Intel GPIO drivers and
> GPIO ACPI library. It has ben a while in Linux Next without any error reported.
>
> Thanks,
>
> With Best Regards,
> Andy Shevchenko
>
> The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
>
>   Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
>
> are available in the Git repository at:
>
>   git@gitolite.kernel.org:pub/scm/linux/kernel/git/andy/linux-gpio-intel.git tags/intel-gpio-v5.17-1
>
> for you to fetch changes up to 9d5f0f6644b1404f40266a2682add712dc9931f5:
>
>   gpio: sch: fix typo in a comment (2021-12-13 13:29:09 +0200)
>
> ----------------------------------------------------------------
> intel-gpio for v5.17-1
>
> * Don't set type for IRQ already in use in case of ACPI
> * Drop unused call from GPIO ACPI library
> * Clean up ML IOH and PCH GPIO drivers to make it closer to each other
> * Clarify use of register file version in DesignWare driver
>
> The following is an automated git shortlog grouped by driver:
>
> dwapb:
>  -  clarify usage of the register file version
>
> gpiolib:
>  -  acpi: Unify debug and other messages format
>  -  acpi: Do not set the IRQ type if the IRQ is already in use
>  -  acpi: shrink devm_acpi_dev_add_driver_gpios()
>  -  acpi: Remove never used devm_acpi_dev_remove_driver_gpios()
>
> ml-ioh:
>  -  Change whitespace to match gpio-pch.c
>  -  Use BIT() to match gpio-pch.c
>  -  Cache &pdev->dev to reduce repetition
>
> pch:
>  -  Cache &pdev->dev to reduce repetition
>  -  Use .driver_data instead of checking Device IDs again
>
> sch:
>  -  fix typo in a comment
>
> ----------------------------------------------------------------
> Andy Shevchenko (4):
>       gpiolib: acpi: Remove never used devm_acpi_dev_remove_driver_gpios()
>       gpiolib: acpi: shrink devm_acpi_dev_add_driver_gpios()
>       gpiolib: acpi: Unify debug and other messages format
>       gpio: dwapb: clarify usage of the register file version
>
> Bjorn Helgaas (5):
>       gpio: pch: Use .driver_data instead of checking Device IDs again
>       gpio: pch: Cache &pdev->dev to reduce repetition
>       gpio: ml-ioh: Cache &pdev->dev to reduce repetition
>       gpio: ml-ioh: Use BIT() to match gpio-pch.c
>       gpio: ml-ioh: Change whitespace to match gpio-pch.c
>
> Hans de Goede (1):
>       gpiolib: acpi: Do not set the IRQ type if the IRQ is already in use
>
> Jason Wang (1):
>       gpio: sch: fix typo in a comment
>
>  drivers/gpio/gpio-dwapb.c     | 10 +++++----
>  drivers/gpio/gpio-ml-ioh.c    | 52 +++++++++++++++++++++----------------------
>  drivers/gpio/gpio-pch.c       | 42 +++++++++++++++++-----------------
>  drivers/gpio/gpio-sch.c       |  2 +-
>  drivers/gpio/gpiolib-acpi.c   | 51 ++++++++++++++++++------------------------
>  include/linux/gpio/consumer.h |  2 --
>  6 files changed, 75 insertions(+), 84 deletions(-)
>
> --
> With Best Regards,
> Andy Shevchenko
>
>

Pulled, thanks!

Bart
Andy Shevchenko Dec. 16, 2021, 11:36 a.m. UTC | #2
On Thu, Dec 16, 2021 at 10:14:05AM +0100, Bartosz Golaszewski wrote:
> On Wed, Dec 15, 2021 at 3:33 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > Hi Linux GPIO  maintainers,
> >
> > Approximately a dozen of changes for v5.17 against Intel GPIO drivers and
> > GPIO ACPI library. It has ben a while in Linux Next without any error reported.

> Pulled, thanks!

Thanks!

Are you going to pull series with the OF node assignments clean up?
I forgot to mention here that my PR does not include them.
Bartosz Golaszewski Dec. 16, 2021, 11:46 a.m. UTC | #3
On Thu, Dec 16, 2021 at 12:37 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Thu, Dec 16, 2021 at 10:14:05AM +0100, Bartosz Golaszewski wrote:
> > On Wed, Dec 15, 2021 at 3:33 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > Hi Linux GPIO  maintainers,
> > >
> > > Approximately a dozen of changes for v5.17 against Intel GPIO drivers and
> > > GPIO ACPI library. It has ben a while in Linux Next without any error reported.
>
> > Pulled, thanks!
>
> Thanks!
>
> Are you going to pull series with the OF node assignments clean up?
> I forgot to mention here that my PR does not include them.
>

Yes, I'll queue it this week.

Bart
Andy Shevchenko Dec. 16, 2021, 1:05 p.m. UTC | #4
On Thu, Dec 16, 2021 at 12:46:11PM +0100, Bartosz Golaszewski wrote:
> On Thu, Dec 16, 2021 at 12:37 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > On Thu, Dec 16, 2021 at 10:14:05AM +0100, Bartosz Golaszewski wrote:
> > > On Wed, Dec 15, 2021 at 3:33 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > >
> > > > Hi Linux GPIO  maintainers,
> > > >
> > > > Approximately a dozen of changes for v5.17 against Intel GPIO drivers and
> > > > GPIO ACPI library. It has ben a while in Linux Next without any error reported.
> >
> > > Pulled, thanks!
> >
> > Thanks!
> >
> > Are you going to pull series with the OF node assignments clean up?
> > I forgot to mention here that my PR does not include them.
> >
> 
> Yes, I'll queue it this week.

Thanks!

Do you know that your branches were kicked off from the Linux Next?
Are you going to drop previous gpio-sim from the Linux Next?
Andy Shevchenko Dec. 16, 2021, 1:13 p.m. UTC | #5
On Thu, Dec 16, 2021 at 03:05:18PM +0200, Andy Shevchenko wrote:
> On Thu, Dec 16, 2021 at 12:46:11PM +0100, Bartosz Golaszewski wrote:
> > On Thu, Dec 16, 2021 at 12:37 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > > On Thu, Dec 16, 2021 at 10:14:05AM +0100, Bartosz Golaszewski wrote:
> > > > On Wed, Dec 15, 2021 at 3:33 PM Andy Shevchenko
> > > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > >
> > > > > Hi Linux GPIO  maintainers,
> > > > >
> > > > > Approximately a dozen of changes for v5.17 against Intel GPIO drivers and
> > > > > GPIO ACPI library. It has ben a while in Linux Next without any error reported.
> > >
> > > > Pulled, thanks!
> > >
> > > Thanks!
> > >
> > > Are you going to pull series with the OF node assignments clean up?
> > > I forgot to mention here that my PR does not include them.
> > >
> > 
> > Yes, I'll queue it this week.
> 
> Thanks!
> 
> Do you know that your branches were kicked off from the Linux Next?
> Are you going to drop previous gpio-sim from the Linux Next?


Last seen GPIO for-next
$ git tag --contains 9dbd1ab2050
next-20211207
next-20211208
next-20211210

Last seen your old GPIO simulator
$ git tag --contains 5065e08e4ef3c
DONT-USE-next-20211105
next-20211101
next-20211102
next-20211103
next-20211104
next-20211105
next-20211106
next-20211108
next-20211109
next-20211110
next-20211111
next-20211112
next-20211115
next-20211116
next-20211117
next-20211118
next-20211123
next-20211124
next-20211125
next-20211126
next-20211129
next-20211130
next-20211201
next-20211202
next-20211203
next-20211206
next-20211207
next-20211208
next-20211210
next-20211213
next-20211214
next-20211215
Bartosz Golaszewski Dec. 16, 2021, 2:01 p.m. UTC | #6
On Thu, Dec 16, 2021 at 2:06 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Thu, Dec 16, 2021 at 12:46:11PM +0100, Bartosz Golaszewski wrote:
> > On Thu, Dec 16, 2021 at 12:37 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > On Thu, Dec 16, 2021 at 10:14:05AM +0100, Bartosz Golaszewski wrote:
> > > > On Wed, Dec 15, 2021 at 3:33 PM Andy Shevchenko
> > > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > >
> > > > > Hi Linux GPIO  maintainers,
> > > > >
> > > > > Approximately a dozen of changes for v5.17 against Intel GPIO drivers and
> > > > > GPIO ACPI library. It has ben a while in Linux Next without any error reported.
> > >
> > > > Pulled, thanks!
> > >
> > > Thanks!
> > >
> > > Are you going to pull series with the OF node assignments clean up?
> > > I forgot to mention here that my PR does not include them.
> > >
> >
> > Yes, I'll queue it this week.
>
> Thanks!
>
> Do you know that your branches were kicked off from the Linux Next?
> Are you going to drop previous gpio-sim from the Linux Next?
>

No, I didn't, thanks for the heads-up. Old gpio-sim code conflicted
with the one that was queued for v5.17. Should be good now.

Bart
Andy Shevchenko Dec. 17, 2021, 9:52 a.m. UTC | #7
On Fri, Dec 17, 2021 at 1:38 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> On Thu, Dec 16, 2021 at 2:06 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Thu, Dec 16, 2021 at 12:46:11PM +0100, Bartosz Golaszewski wrote:
> > > On Thu, Dec 16, 2021 at 12:37 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > On Thu, Dec 16, 2021 at 10:14:05AM +0100, Bartosz Golaszewski wrote:

...

> > > > Are you going to pull series with the OF node assignments clean up?
> > > > I forgot to mention here that my PR does not include them.
> > >
> > > Yes, I'll queue it this week.
> >
> > Thanks!
> >
> > Do you know that your branches were kicked off from the Linux Next?
> > Are you going to drop previous gpio-sim from the Linux Next?
>
> No, I didn't, thanks for the heads-up. Old gpio-sim code conflicted
> with the one that was queued for v5.17. Should be good now.

Thanks

Btw, I have noticed you rebased your tree, can you, please, do not
forget to put --rebase-merges to your `git rebase` command line so the
merge won't change commit IDs?
Bartosz Golaszewski Dec. 17, 2021, 11:13 a.m. UTC | #8
On Fri, Dec 17, 2021 at 10:53 AM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Fri, Dec 17, 2021 at 1:38 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> > On Thu, Dec 16, 2021 at 2:06 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > > On Thu, Dec 16, 2021 at 12:46:11PM +0100, Bartosz Golaszewski wrote:
> > > > On Thu, Dec 16, 2021 at 12:37 PM Andy Shevchenko
> > > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > > On Thu, Dec 16, 2021 at 10:14:05AM +0100, Bartosz Golaszewski wrote:
>
> ...
>
> > > > > Are you going to pull series with the OF node assignments clean up?
> > > > > I forgot to mention here that my PR does not include them.
> > > >
> > > > Yes, I'll queue it this week.
> > >
> > > Thanks!
> > >
> > > Do you know that your branches were kicked off from the Linux Next?
> > > Are you going to drop previous gpio-sim from the Linux Next?
> >
> > No, I didn't, thanks for the heads-up. Old gpio-sim code conflicted
> > with the one that was queued for v5.17. Should be good now.
>
> Thanks
>
> Btw, I have noticed you rebased your tree, can you, please, do not
> forget to put --rebase-merges to your `git rebase` command line so the
> merge won't change commit IDs?
>

Oof you saved me from another LinusRant. I already pushed it, let's
see if I can get back to the previous state...

Bart
Bartosz Golaszewski Dec. 17, 2021, 11:29 a.m. UTC | #9
On Fri, Dec 17, 2021 at 12:13 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>
> On Fri, Dec 17, 2021 at 10:53 AM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> >
> > On Fri, Dec 17, 2021 at 1:38 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> > > On Thu, Dec 16, 2021 at 2:06 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > On Thu, Dec 16, 2021 at 12:46:11PM +0100, Bartosz Golaszewski wrote:
> > > > > On Thu, Dec 16, 2021 at 12:37 PM Andy Shevchenko
> > > > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > > > On Thu, Dec 16, 2021 at 10:14:05AM +0100, Bartosz Golaszewski wrote:
> >
> > ...
> >
> > > > > > Are you going to pull series with the OF node assignments clean up?
> > > > > > I forgot to mention here that my PR does not include them.
> > > > >
> > > > > Yes, I'll queue it this week.
> > > >
> > > > Thanks!
> > > >
> > > > Do you know that your branches were kicked off from the Linux Next?
> > > > Are you going to drop previous gpio-sim from the Linux Next?
> > >
> > > No, I didn't, thanks for the heads-up. Old gpio-sim code conflicted
> > > with the one that was queued for v5.17. Should be good now.
> >
> > Thanks
> >
> > Btw, I have noticed you rebased your tree, can you, please, do not
> > forget to put --rebase-merges to your `git rebase` command line so the
> > merge won't change commit IDs?
> >
>
> Oof you saved me from another LinusRant. I already pushed it, let's
> see if I can get back to the previous state...
>

Done, reflog is my best friend now. Please take a look if all looks good to you.

Bart
Andy Shevchenko Dec. 17, 2021, 11:47 a.m. UTC | #10
On Fri, Dec 17, 2021 at 12:29:50PM +0100, Bartosz Golaszewski wrote:
> On Fri, Dec 17, 2021 at 12:13 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> > On Fri, Dec 17, 2021 at 10:53 AM Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
> > > On Fri, Dec 17, 2021 at 1:38 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:

...

> > > Btw, I have noticed you rebased your tree, can you, please, do not
> > > forget to put --rebase-merges to your `git rebase` command line so the
> > > merge won't change commit IDs?
> >
> > Oof you saved me from another LinusRant. I already pushed it, let's
> > see if I can get back to the previous state...
> 
> Done, reflog is my best friend now. Please take a look if all looks good to you.

Looks excellent, thanks!