Thread (9 messages) 9 messages, 3 authors, 2019-02-08

Re: [PATCH 0/3] pinctrl: meson: g12a fixes

From: Kevin Hilman <khilman@baylibre.com>
Date: 2019-02-08 17:27:14
Also in: linux-amlogic, linux-gpio, lkml

Linus Walleij [off-list ref] writes:
On Mon, Jan 21, 2019 at 4:36 PM Jerome Brunet [off-list ref] wrote:
quoted
On Mon, 2019-01-21 at 14:53 +0100, Linus Walleij wrote:
quoted
On Thu, Jan 17, 2019 at 11:23 AM Jerome Brunet [off-list ref] wrote:
quoted
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 ?
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=ib-meson-fixes
quoted
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 :)
When you say "this cycle" do you mean I should target fixes (v5.0-rcN)
or next (v5.1) with these patches?
I was referring to the 5.1 release but it is a good question, I did not really
think about 5.0.

Those changes are mainly fixes, so guess it could go in the 5.0 but support
for this SoC is still in its early stages, so either way is fine by me.

Whatever is simpler for you I guess ;)
I already merged it for devel and other stuff on top so it will be for v5.1
as it looks now.
OK, assuming that tag is still valid (and immutable), that works for me.

Kevin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help