devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@aj.id.au>
To: Joel Stanley <joel@jms.id.au>
Cc: Russell King <linux@armlinux.org.uk>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Jeremy Kerr <jk@ozlabs.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Andrew Jeffery <andrew@aj.id.au>
Subject: [PATCH v3 0/7] aspeed: Integrate pinctrl and gpio drivers
Date: Tue, 30 Aug 2016 17:25:53 +0930	[thread overview]
Message-ID: <20160830075600.11559-1-andrew@aj.id.au> (raw)

Hi all,

Here's v3 of the Aspeed pinctrl and gpio driver integration patches. v2 of the
integration series can be found at:

  https://lkml.org/lkml/2016/8/19/403

v3 captures changes required to address review comments from v2 of the driver
series:

  https://lkml.org/lkml/2016/8/22/343

Since v2:

* Add interrupt-controller property to gpio devicetree nodes
* Drop unit address from pinctrl devicetree nodes
* ARCH_ASPEED selects MFD_SYSCON

Cheers,

Andrew

---

Andrew Jeffery (7):
  mach-aspeed: Select pinctrl drivers
  mach-aspeed: Select GPIO driver
  aspeed-g4: Add syscon and pin controller nodes
  palmetto: Request relevant mux functions in devicetree
  aspeed-g4: Add gpio controller to devicetree
  aspeed-g5: Add syscon and pin controller nodes
  aspeed-g5: Add gpio controller to devicetree

 arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts |  14 +
 arch/arm/boot/dts/aspeed-g4.dtsi              | 430 ++++++++++++++++++++++++++
 arch/arm/boot/dts/aspeed-g5.dtsi              | 214 +++++++++++++
 arch/arm/mach-aspeed/Kconfig                  |   6 +
 4 files changed, 664 insertions(+)

-- 
2.9.3.1.g0db844e

             reply	other threads:[~2016-08-30  7:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30  7:55 Andrew Jeffery [this message]
2016-08-30  7:55 ` [PATCH v3 1/7] mach-aspeed: Select pinctrl drivers Andrew Jeffery
2016-08-30  7:55 ` [PATCH v3 2/7] mach-aspeed: Select GPIO driver Andrew Jeffery
2016-09-13 12:43   ` Joel Stanley
2016-08-30  7:55 ` [PATCH v3 5/7] aspeed-g4: Add gpio controller to devicetree Andrew Jeffery
2016-08-30  7:55 ` [PATCH v3 6/7] aspeed-g5: Add syscon and pin controller nodes Andrew Jeffery
     [not found] ` <20160830075600.11559-1-andrew-zrmu5oMJ5Fs@public.gmane.org>
2016-08-30  7:55   ` [PATCH v3 3/7] aspeed-g4: " Andrew Jeffery
2016-08-30  7:55   ` [PATCH v3 4/7] palmetto: Request relevant mux functions in devicetree Andrew Jeffery
     [not found]     ` <20160830075600.11559-5-andrew-zrmu5oMJ5Fs@public.gmane.org>
2016-09-13 12:41       ` Joel Stanley
2016-09-13 20:58         ` Benjamin Herrenschmidt
     [not found]           ` <1473800295.8689.295.camel-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2016-09-14  0:59             ` Joel Stanley
2016-08-30  7:56   ` [PATCH v3 7/7] aspeed-g5: Add gpio controller to devicetree Andrew Jeffery
2016-09-13 12:44   ` [PATCH v3 0/7] aspeed: Integrate pinctrl and gpio drivers Joel Stanley

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=20160830075600.11559-1-andrew@aj.id.au \
    --to=andrew@aj.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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).