From: Dan O'Donovan <dan@emutex.com>
To: mika.westerberg@linux.intel.com, linus.walleij@linaro.org
Cc: heikki.krogerus@linux.intel.com, linux-gpio@vger.kernel.org,
Dan O'Donovan <dan@emutex.com>
Subject: [PATCH 0/5] pinctrl: cherryview: fixes and enhancements
Date: Thu, 2 Jun 2016 22:55:38 +0100 [thread overview]
Message-ID: <1464904543-4094-1-git-send-email-dan@emutex.com> (raw)
This series includes a number of fixes and enhancements for the
Cherryview pinctrl/gpio driver, developed during integration on the
UP Board (based on the Intel X5-Z8350 "Cherry Trail" Atom SoC).
Of particular note is a workaround for a documented silicon bug which
causes data corruption of concurrent accesses to the GPIO controller
registers on this SoC.
Other patches include clean-up of checkpatch warnings, implementation
of additional pin config functions and options, and a fix for a loss
of pin config register state that can occur when switching in and out
of GPIO pin mode.
Dan O'Donovan (5):
pinctrl: cherryview: convert bare unsigned to unsigned int
pinctrl: cherryview: add option to set open-drain pin config
pinctrl: cherryview: add handlers for pin_config_group_get/set
pinctrl: cherryview: prevent concurrent access to GPIO controllers
pinctrl: cherryview: restore padctrl1 reg when gpio is disabled
drivers/pinctrl/intel/pinctrl-cherryview.c | 296 +++++++++++++++++++----------
1 file changed, 196 insertions(+), 100 deletions(-)
--
2.1.4
next reply other threads:[~2016-06-02 21:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 21:55 Dan O'Donovan [this message]
2016-06-02 21:55 ` [PATCH 1/5] pinctrl: cherryview: convert bare unsigned to unsigned int Dan O'Donovan
2016-06-06 10:28 ` Mika Westerberg
2016-06-09 16:04 ` Dan O'Donovan
2016-06-02 21:55 ` [PATCH 2/5] pinctrl: cherryview: add option to set open-drain pin config Dan O'Donovan
2016-06-06 10:32 ` Mika Westerberg
2016-06-02 21:55 ` [PATCH 3/5] pinctrl: cherryview: add handlers for pin_config_group_get/set Dan O'Donovan
2016-06-02 21:55 ` [PATCH 4/5] pinctrl: cherryview: prevent concurrent access to GPIO controllers Dan O'Donovan
2016-06-06 10:31 ` Mika Westerberg
2016-06-09 16:11 ` Dan O'Donovan
2016-06-02 21:55 ` [PATCH 5/5] pinctrl: cherryview: restore padctrl1 reg when gpio is disabled Dan O'Donovan
2016-06-06 10:40 ` Mika Westerberg
2016-06-09 16:41 ` Dan O'Donovan
2016-06-10 6:00 ` Mika Westerberg
2016-06-10 8:43 ` Dan O'Donovan
2016-06-08 8:32 ` [PATCH 0/5] pinctrl: cherryview: fixes and enhancements Linus Walleij
2016-06-10 12:23 ` [PATCH v2 0/3] " Dan O'Donovan
2016-06-10 12:23 ` [PATCH v2 1/3] pinctrl: cherryview: prevent concurrent access to GPIO controllers Dan O'Donovan
2016-06-13 12:23 ` Linus Walleij
2016-06-13 12:30 ` Dan O'Donovan
2016-06-10 12:23 ` [PATCH v2 2/3] pinctrl: cherryview: add option to set open-drain pin config Dan O'Donovan
2016-06-13 12:25 ` Linus Walleij
2016-06-10 12:23 ` [PATCH v2 3/3] pinctrl: cherryview: add handlers for pin_config_group_get/set Dan O'Donovan
2016-06-13 12:26 ` Linus Walleij
2016-06-13 9:21 ` [PATCH v2 0/3] pinctrl: cherryview: fixes and enhancements Mika Westerberg
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=1464904543-4094-1-git-send-email-dan@emutex.com \
--to=dan@emutex.com \
--cc=heikki.krogerus@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 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).