From: matt.porter@linaro.org (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] pinctrl: Rename Broadcom Capri pinctrl driver
Date: Thu, 10 Apr 2014 13:57:10 -0400 [thread overview]
Message-ID: <20140410175710.GD23695@beef> (raw)
In-Reply-To: <CACRpkdZaMcSjy+-15y4kNsBgLZrThwxzJQr7SEy59AVm3yuM_A@mail.gmail.com>
On Thu, Apr 10, 2014 at 07:41:20PM +0200, Linus Walleij wrote:
> On Thu, Apr 10, 2014 at 6:56 PM, Matt Porter <matt.porter@linaro.org> wrote:
> > On Thu, Apr 10, 2014 at 06:51:12PM +0200, Linus Walleij wrote:
> >> On Thu, Apr 10, 2014 at 6:49 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> >> > On Thu, Apr 3, 2014 at 12:40 AM, Sherman Yin <syin@broadcom.com> wrote:
> >> >
> >> >> To be consistent with other Broadcom drivers, the Broadcom Capri pinctrl
> >> >> driver and its related CONFIG option are renamed to bcm281xx.
> >> >>
> >> >> Devicetree compatible string and binding documentation use
> >> >> "brcm,bcm11351-pinctrl" to match the machine binding here:
> >> >> Documentation/devicetree/bindings/arm/bcm/bcm11351.txt
> >> >>
> >> >> This driver supports pinctrl on BCM11130, BCM11140, BCM11351, BCM28145
> >> >> and BCM28155 SoCs.
> >> >>
> >> >> Signed-off-by: Sherman Yin <syin@broadcom.com>
> >> >> Reviewed-by: Matt Porter <mporter@linaro.org>
> >> >> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> >> >> ---
> >> >> drivers/pinctrl/Kconfig | 8 +-
> >> >> drivers/pinctrl/Makefile | 2 +-
> >> >> .../{pinctrl-capri.c => pinctrl-bcm281xx.c} | 1519 ++++++++++----------
> >> >
> >> > This last version from apr 7 does not change
> >> > arch/arm/configs/bcm_defconfig:CONFIG_PINCTRL_CAPRI=y
> >> >
> >> > Doesn't this mean that you render this platform without a pin
> >> > control driver and thus broken?
> >>
> >> Bah I see that it's a separate patch now, sorry...
> >>
> >> Looking closer.
> >
> > I can take that one through mach-bcm for 3.16 to keep these changes
> > in one place.
>
> Nah I might as well take all of it through the pin control tree.
> Can I have your ACK on the defconfig change?
Sounds fine to me, done.
-Matt
next prev parent reply other threads:[~2014-04-10 17:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 22:38 [PATCH] pinctrl: Rename Broadcom Capri pinctrl driver Sherman Yin
2014-01-22 0:59 ` Olof Johansson
2014-01-22 1:35 ` Matt Porter
2014-01-22 4:59 ` Olof Johansson
2014-01-23 8:17 ` Linus Walleij
2014-01-23 8:36 ` Linus Walleij
2014-01-23 20:44 ` [PATCH v2 0/4] " Sherman Yin
2014-01-23 20:44 ` [PATCH v2 1/4] pinctrl: Rename Broadcom Capri pinctrl binding Sherman Yin
2014-01-23 20:44 ` [PATCH v2 2/4] pinctrl: Rename Broadcom Capri pinctrl driver Sherman Yin
2014-01-23 20:44 ` [PATCH v2 3/4] Update bcm_defconfig with new pinctrl CONFIG Sherman Yin
2014-01-27 15:57 ` Christian Daudt
2014-01-23 20:44 ` [PATCH v2 4/4] Update dtsi with new pinctrl compatible string Sherman Yin
2014-04-02 22:40 ` [PATCH v3 0/3] pinctrl: Rename Broadcom Capri pinctrl driver Sherman Yin
2014-04-02 22:40 ` [PATCH v3 1/3] " Sherman Yin
2014-04-10 16:49 ` Linus Walleij
2014-04-10 16:51 ` Linus Walleij
2014-04-10 16:56 ` Matt Porter
2014-04-10 17:41 ` Linus Walleij
2014-04-10 17:57 ` Matt Porter [this message]
2014-04-10 16:55 ` Matt Porter
2014-04-02 22:40 ` [PATCH v3 2/3] Update bcm_defconfig with new pinctrl CONFIG Sherman Yin
2014-04-10 17:56 ` Matt Porter
2014-04-02 22:40 ` [PATCH v3 3/3] pinctrl: fix typo in bindings documentation Sherman Yin
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=20140410175710.GD23695@beef \
--to=matt.porter@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).