linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Alexander Stein <alexander.stein@systec-electronic.com>,
	Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: [GIT PULL] pin control fixes for v4.10
Date: Wed, 1 Feb 2017 09:56:05 +0100	[thread overview]
Message-ID: <CACRpkdbBJpzsDJ6BkLnu3YAr+1CHWFemctMhNDpt=T9dTgBs_A@mail.gmail.com> (raw)

Hi Linus,

another week another set of pin control fixes. The subsystem has seen
high patch-spot activity recently.

The majority of the patches are for Intel, I vaguely think it mostly concern
phones, tablets and maybe chromebooks and even laptops with this Intel
Atom family chips.

Please pull them in!

Yours,
Linus Walleij


The following changes since commit 566cf877a1fcb6d6dc0126b076aad062054c2637:

  Linux 4.10-rc6 (2017-01-29 14:25:17 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v4.10-4

for you to fetch changes up to cdca06e4e85974d8a3503ab15709dbbaf90d3dd1:

  pinctrl: baytrail: Add missing spinlock usage in
byt_gpio_irq_handler (2017-01-30 15:53:57 +0100)

----------------------------------------------------------------
Pin control fixes for the v4.10 series.

Driver fixes only:

- One fix to the Berlin driver making the SD card work fully
  again.

- One fix to the Allwinner/sunxi bias function: one premature
  change needs to be partially reverted.

- The remaining four patches are to Intel embedded SoCs: baytrail
  (three patches) and merrifield (one patch): register access
  debounce fixes and a missing spinlock.

----------------------------------------------------------------
Alexander Stein (1):
      pinctrl: baytrail: Add missing spinlock usage in byt_gpio_irq_handler

Andy Shevchenko (3):
      pinctrl: intel: merrifield: Add missed check in mrfld_config_set()
      pinctrl: baytrail: Rectify debounce support (part 2)
      pinctrl: baytrail: Debounce register is one per community

Jisheng Zhang (1):
      pinctrl: berlin-bg4ct: fix the value for "sd1a" of pin SCRD0_CRD_PRES

Maxime Ripard (1):
      pinctrl: sunxi: Don't enforce bias disable (for now)

 drivers/pinctrl/berlin/berlin-bg4ct.c      |  2 +-
 drivers/pinctrl/intel/pinctrl-baytrail.c   | 27 ++++++++++++++++++++-------
 drivers/pinctrl/intel/pinctrl-merrifield.c |  3 +++
 drivers/pinctrl/sunxi/pinctrl-sunxi.c      |  3 +--
 4 files changed, 25 insertions(+), 10 deletions(-)

             reply	other threads:[~2017-02-01  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01  8:56 Linus Walleij [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-26 13:42 [GIT PULL] pin control fixes for v4.10 Linus Walleij
2017-01-05 16:18 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='CACRpkdbBJpzsDJ6BkLnu3YAr+1CHWFemctMhNDpt=T9dTgBs_A@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=alexander.stein@systec-electronic.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=torvalds@linux-foundation.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).