linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: syin@broadcom.com (Sherman Yin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] pinctrl: Rename Broadcom Capri pinctrl driver
Date: Thu, 23 Jan 2014 12:44:43 -0800	[thread overview]
Message-ID: <1390509887-19278-1-git-send-email-syin@broadcom.com> (raw)
In-Reply-To: <1390343886-25852-1-git-send-email-syin@broadcom.com>

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>
---
v2: split single patch into 4 patches

Sherman Yin (4):
  pinctrl: Rename Broadcom Capri pinctrl binding
  pinctrl: Rename Broadcom Capri pinctrl driver
  Update bcm_defconfig with new pinctrl CONFIG
  Update dtsi with new pinctrl compatible string

 ...capri-pinctrl.txt => brcm,bcm11351-pinctrl.txt} |    8 +-
 arch/arm/boot/dts/bcm11351.dtsi                    |    2 +-
 arch/arm/configs/bcm_defconfig                     |    2 +-
 drivers/pinctrl/Kconfig                            |    8 +-
 drivers/pinctrl/Makefile                           |    2 +-
 .../{pinctrl-capri.c => pinctrl-bcm281xx.c}        | 1521 ++++++++++----------
 6 files changed, 775 insertions(+), 768 deletions(-)
 rename Documentation/devicetree/bindings/pinctrl/{brcm,capri-pinctrl.txt => brcm,bcm11351-pinctrl.txt} (98%)
 rename drivers/pinctrl/{pinctrl-capri.c => pinctrl-bcm281xx.c} (25%)

-- 
1.7.9.5

  parent reply	other threads:[~2014-01-23 20:44 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 ` Sherman Yin [this message]
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
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=1390509887-19278-1-git-send-email-syin@broadcom.com \
    --to=syin@broadcom.com \
    --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).