public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: linux-samsung-soc@vger.kernel.org
Cc: "Kukjin Kim" <kgene@kernel.org>, 김학주 <ruppi.kim@hardkernel.com>,
	"Humberto Naves" <hsnaves@gmail.com>,
	"Jan Kiszka" <jan.kiszka@siemens.com>,
	"Johann Pfefferl" <johann.pfefferl@siemens.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>
Subject: [PATCH v2 0/5] ARM: EXYNOS: ODROID-XU DT and LEDs
Date: Sat, 22 Nov 2014 21:26:19 +0100	[thread overview]
Message-ID: <1416687984-3546-1-git-send-email-afaerber@suse.de> (raw)

Hello,

This series adds a dedicated ODROID-XU device tree and enhances it with 
LED configuration, to match the downstream 3.14 based behavior.

Regards,
Andreas

v1 -> v2:
* Inserted needed Sobs from Hakjoo Kim
* Rebased pinctrl (.svc, .{g,w}eint_{con,mask,pend} fields dropped)

Andreas Färber (3):
  ARM: dts: exynos5410: Clean up SMDK5410 indentation
  ARM: dts: exynos5410: Prepare ODROID-XU device tree
  ARM: dts: exynos5410: Add ODROID-XU LEDs

Hakjoo Kim (2):
  pinctrl: exynos: add exynos5410 SoC specific data
  ARM: dts: add pinctrl support to Exynos5410

 .../bindings/pinctrl/samsung-pinctrl.txt           |   1 +
 arch/arm/boot/dts/Makefile                         |   1 +
 arch/arm/boot/dts/exynos5410-odroidxu.dts          | 103 ++++++
 arch/arm/boot/dts/exynos5410-pinctrl.dtsi          | 406 +++++++++++++++++++++
 arch/arm/boot/dts/exynos5410-smdk5410.dts          |   6 +-
 arch/arm/boot/dts/exynos5410.dtsi                  |  30 ++
 drivers/pinctrl/samsung/pinctrl-exynos.c           | 126 +++++++
 drivers/pinctrl/samsung/pinctrl-samsung.c          |   2 +
 drivers/pinctrl/samsung/pinctrl-samsung.h          |   1 +
 9 files changed, 673 insertions(+), 3 deletions(-)
 create mode 100644 arch/arm/boot/dts/exynos5410-odroidxu.dts
 create mode 100644 arch/arm/boot/dts/exynos5410-pinctrl.dtsi

-- 
2.1.2


             reply	other threads:[~2014-11-22 20:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 20:26 Andreas Färber [this message]
2014-11-22 20:26 ` [PATCH v2 1/5] ARM: dts: exynos5410: Clean up SMDK5410 indentation Andreas Färber
2014-11-22 20:26 ` [PATCH v2 2/5] ARM: dts: exynos5410: Prepare ODROID-XU device tree Andreas Färber
2014-11-22 20:26 ` [PATCH v2 3/5] pinctrl: exynos: add exynos5410 SoC specific data Andreas Färber
2014-11-22 21:49   ` Andreas Färber
2014-11-22 22:26     ` [PATCH v3 " Andreas Färber
2014-11-28 11:59       ` Linus Walleij
2014-11-28 12:07         ` Andreas Färber
2014-11-30 12:13           ` Tomasz Figa
2014-12-28 11:16       ` Tomasz Figa
2014-11-22 20:26 ` [PATCH v2 4/5] ARM: dts: add pinctrl support to Exynos5410 Andreas Färber
2014-11-23 17:18   ` Andreas Färber
2014-11-23 17:20     ` [PATCH v3 " Andreas Färber
2014-11-22 20:26 ` [PATCH v2 5/5] ARM: dts: exynos5410: Add ODROID-XU LEDs Andreas Färber
2014-11-23  1:31   ` Andreas Färber

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=1416687984-3546-1-git-send-email-afaerber@suse.de \
    --to=afaerber@suse.de \
    --cc=hsnaves@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=johann.pfefferl@siemens.com \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=ruppi.kim@hardkernel.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