linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linux GPIO <linux-gpio@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [GIT PULL] intel-gpio for 5.15-1
Date: Thu, 12 Aug 2021 16:46:27 +0300	[thread overview]
Message-ID: <YRUmM1E80OTIrApK@black.fi.intel.com> (raw)

Hi Linux GPIO  maintainers,

Mostly DesignWare changes, but really small update for v5.15 for the Intel /
ACPI stuff. Has been in Linux Next for a couple days without any complains
from bots nor people.

Thanks,

With Best Regards,
Andy Shevchenko

The following changes since commit e73f0f0ee7541171d89f2e2491130c7771ba58d3:

  Linux 5.14-rc1 (2021-07-11 15:07:40 -0700)

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.15-1

for you to fetch changes up to 5111c2b6b0194b509f47e6338c4deeeb4497bda8:

  gpio: dwapb: Get rid of legacy platform data (2021-08-11 16:01:06 +0300)

----------------------------------------------------------------
intel-gpio for v5.15-1

* Rework DesignWare driver to use software nodes instead of platform data
* Drop duplication of forward declaration for ACPI in consumer.h
* Get rid of legacy PCI PM code in ML IOH driver

The following is an automated git shortlog grouped by driver:

dwapb:
 -  Get rid of legacy platform data
 -  Read GPIO base from gpio-base property
 -  Unify ACPI enumeration checks in get_irq() and configure_irqs()

gpiolib:
 -  Deduplicate forward declaration in the consumer.h header

mfd:
 -  intel_quark_i2c_gpio: Convert GPIO to use software nodes

ml-ioh:
 -  Convert to dev_pm_ops

----------------------------------------------------------------
Andy Shevchenko (5):
      gpiolib: Deduplicate forward declaration in the consumer.h header
      gpio: dwapb: Unify ACPI enumeration checks in get_irq() and configure_irqs()
      gpio: dwapb: Read GPIO base from gpio-base property
      mfd: intel_quark_i2c_gpio: Convert GPIO to use software nodes
      gpio: dwapb: Get rid of legacy platform data

Vaibhav Gupta (1):
      gpio: ml-ioh: Convert to dev_pm_ops

 drivers/gpio/gpio-dwapb.c                | 56 +++++++++++++++----------
 drivers/gpio/gpio-ml-ioh.c               | 49 +++++-----------------
 drivers/mfd/intel_quark_i2c_gpio.c       | 71 +++++++++++++++++---------------
 include/linux/gpio/consumer.h            |  6 +--
 include/linux/platform_data/gpio-dwapb.h | 25 -----------
 5 files changed, 84 insertions(+), 123 deletions(-)
 delete mode 100644 include/linux/platform_data/gpio-dwapb.h

-- 
With Best Regards,
Andy Shevchenko



             reply	other threads:[~2021-08-12 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 13:46 Andy Shevchenko [this message]
2021-08-13  7:49 ` [GIT PULL] intel-gpio for 5.15-1 Bartosz Golaszewski

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=YRUmM1E80OTIrApK@black.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    /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).