From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
"maintainer:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE..."
<bcm-kernel-feedback-list@broadcom.com>,
"Stefan Wahren" <stefan.wahren@i2se.com>,
"Doug Berger" <opendmb@gmail.com>,
"Matheus Castello" <matheus@castello.eng.br>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Lukas Wunner" <lukas@wunner.de>,
"Nathan Chancellor" <natechancellor@gmail.com>,
"Al Cooper" <alcooperx@gmail.com>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:BROADCOM BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] pinctrl: bcm: Allow PINCTRL_BCM2835 for ARCH_BRCMSTB
Date: Thu, 09 May 2019 15:53:36 -0700 [thread overview]
Message-ID: <87woizqlxr.fsf@anholt.net> (raw)
In-Reply-To: <20190509205955.27842-1-f.fainelli@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
Florian Fainelli <f.fainelli@gmail.com> writes:
> Hi Linus,
>
> This patch series allows making use of the pinctrl-bcm2835 driver on
> ARCH_BRCMSTB where it is also used. Binding document is updated, and
> then the Kconfig language is updated to allow selecting this driver with
> ARCH_BRCMSTB, finally, Al updates the logic to account for the
> additional registers that were added on 7211.
As far as platform maintainer goes, patch 1-2 are:
Reviewed-by: Eric Anholt <eric@anholt.net>
and patch 3 is:
Acked-by: Eric Anholt <eric@anholt.net>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-05-09 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 20:59 [PATCH 0/3] pinctrl: bcm: Allow PINCTRL_BCM2835 for ARCH_BRCMSTB Florian Fainelli
2019-05-09 20:59 ` [PATCH 1/3] dt-bindings: pinctrl: bcm2835-gpio: Document BCM7211 compatible Florian Fainelli
2019-05-16 13:25 ` Linus Walleij
2019-05-09 20:59 ` [PATCH 2/3] pinctrl: bcm: Allow PINCTRL_BCM2835 for ARCH_BRCMSTB Florian Fainelli
2019-05-16 13:25 ` Linus Walleij
2019-05-09 20:59 ` [PATCH 3/3] pinctrl: bcm2835: bcm7211: Add support for 7211 pull-up functionality Florian Fainelli
2019-05-13 8:14 ` Stefan Wahren
2019-05-13 16:27 ` Florian Fainelli
2019-05-16 13:27 ` Linus Walleij
2019-05-09 22:53 ` Eric Anholt [this message]
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=87woizqlxr.fsf@anholt.net \
--to=eric@anholt.net \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lukas@wunner.de \
--cc=mark.rutland@arm.com \
--cc=matheus@castello.eng.br \
--cc=natechancellor@gmail.com \
--cc=opendmb@gmail.com \
--cc=rafal@milecki.pl \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.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).