From: Jerome Brunet <jbrunet@baylibre.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: [PATCH 0/3] pinctrl: meson: g12a fixes
Date: Thu, 17 Jan 2019 11:23:12 +0100 [thread overview]
Message-ID: <20190117102315.1833-1-jbrunet@baylibre.com> (raw)
This patchset fixes the initial pinctrl support added for th g12a SoC
family, which is mainly around the register regions claimed by the
driver.
Linus, would it possible for you to provide a tag with these changes to
Kevin ?
ATM, we can only use the devices for which the pinmux is already set by
the bootloader. Enabling the broken pinctrl driver could cause regressions
in kernelCI. Having a tag, would allow us to start using pinctrl on this
SoC in this cycle, w/o regression. It would be nice :)
Jerome
Jerome Brunet (2):
dt-bindings: pinctrl: meson: update register descriptions
pinctrl: meson: add optional region for drive strength
Xingyu Chen (1):
pinctrl: meson: fix G12A ao pull registers base address
.../bindings/pinctrl/meson,pinctrl.txt | 10 ++++----
drivers/pinctrl/meson/pinctrl-meson.c | 24 ++++++++++++-------
drivers/pinctrl/meson/pinctrl-meson.h | 1 +
3 files changed, 22 insertions(+), 13 deletions(-)
--
2.20.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-01-17 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 10:23 Jerome Brunet [this message]
2019-01-17 10:23 ` [PATCH 1/3] dt-bindings: pinctrl: meson: update register descriptions Jerome Brunet
2019-01-17 10:23 ` [PATCH 2/3] pinctrl: meson: fix G12A ao pull registers base address Jerome Brunet
2019-01-17 10:23 ` [PATCH 3/3] pinctrl: meson: add optional region for drive strength Jerome Brunet
2019-01-21 13:53 ` [PATCH 0/3] pinctrl: meson: g12a fixes Linus Walleij
2019-01-21 15:36 ` Jerome Brunet
2019-02-07 3:11 ` Kevin Hilman
2019-02-08 13:57 ` Linus Walleij
2019-02-08 17:27 ` Kevin Hilman
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=20190117102315.1833-1-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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).