All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux pin control <linux-gpio@vger.kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [GIT PULL] intel-pinctrl for 5.10-1
Date: Fri, 18 Sep 2020 17:50:47 +0300	[thread overview]
Message-ID: <20200918145047.GA71533@black.fi.intel.com> (raw)

Hi Linus,

Regular bunch of cleanups and fixes of Intel pin control drivers for v5.10.

Thanks,

With Best Regards,
Andy Shevchenko

The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:

  Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-v5.10-1

for you to fetch changes up to a0bf06dc51dbbc5ad182b1bcf4d879db8d297c5e:

  pinctrl: cherryview: Preserve CHV_PADCTRL1_INVRXTX_TXDATA flag on GPIOs (2020-09-07 11:57:19 +0300)

----------------------------------------------------------------
intel-pinctrl for v5.10-1

* Add last part of cleanup Cherryview driver to align with other drivers
* Due to above clean up Cherryview and Baytrail drivers to use common API

The following is an automated git shortlog grouped by driver:

baytrail:
 -  Switch to use intel_pinctrl_get_soc_data()

cherryview:
 -  Preserve CHV_PADCTRL1_INVRXTX_TXDATA flag on GPIOs
 -  Switch to use intel_pinctrl_get_soc_data()
 -  Utilize temporary variable to hold device pointer
 -  Switch to use struct intel_pinctrl
 -  Move custom community members to separate data struct
 -  Drop stale comment

intel:
 -  Update header block to reflect direct dependencies
 -  Extract intel_pinctrl_get_soc_data() helper for wider use

----------------------------------------------------------------
Andy Shevchenko (8):
      pinctrl: cherryview: Drop stale comment
      pinctrl: cherryview: Move custom community members to separate data struct
      pinctrl: cherryview: Switch to use struct intel_pinctrl
      pinctrl: cherryview: Utilize temporary variable to hold device pointer
      pinctrl: intel: Extract intel_pinctrl_get_soc_data() helper for wider use
      pinctrl: baytrail: Switch to use intel_pinctrl_get_soc_data()
      pinctrl: cherryview: Switch to use intel_pinctrl_get_soc_data()
      pinctrl: intel: Update header block to reflect direct dependencies

Hans de Goede (1):
      pinctrl: cherryview: Preserve CHV_PADCTRL1_INVRXTX_TXDATA flag on GPIOs

 drivers/pinctrl/intel/Kconfig              |  12 +-
 drivers/pinctrl/intel/pinctrl-baytrail.c   |  24 +---
 drivers/pinctrl/intel/pinctrl-cherryview.c | 184 ++++++++++++++---------------
 drivers/pinctrl/intel/pinctrl-intel.c      |  24 +++-
 drivers/pinctrl/intel/pinctrl-intel.h      |   7 +-
 5 files changed, 117 insertions(+), 134 deletions(-)

-- 
With Best Regards,
Andy Shevchenko



             reply	other threads:[~2020-09-18 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 14:50 Andy Shevchenko [this message]
2020-09-21 21:45 ` [GIT PULL] intel-pinctrl for 5.10-1 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=20200918145047.GA71533@black.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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.