devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vaibhav Hiremath <hvaibhav@ti.com>
To: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, b-cousson@ti.com,
	mporter@ti.com, devicetree-discuss@lists.ozlabs.org,
	Vaibhav Hiremath <hvaibhav@ti.com>
Subject: [PATCH 0/5] ARM: dts: AM33XX: Cleanup and pinctrl binding support
Date: Wed, 27 Mar 2013 18:29:11 +0530	[thread overview]
Message-ID: <1364389156-8273-1-git-send-email-hvaibhav@ti.com> (raw)

This patch series fixes the numbering schema for I2C and GPIO
module and adds the pin-control binding for I2C, UART, GPIO-LED across
supported platforms (EVM, EVM-SK and Bone).

I have divided patches based on functionality and _not_
into EVM/Board perspective.

Vaibhav Hiremath (5):
  ARM: dts: AM33XX: Fix the i2c numbering to match hardware/TRM
  ARM: dts: AM33XX: Add default pinctrl binding for I2C device
  ARM: dts: AM33XX: Fix gpio numbering to match hardware/TRM
  ARM: dts: AM33XX: Add pinctrl binding to gpio-leds node
  ARM: dts: AM33XX: Add default pinctrl binding for UART0 device

 arch/arm/boot/dts/am335x-bone.dts  |   35 +++++++++++++++++++++----
 arch/arm/boot/dts/am335x-evm.dts   |   48 +++++++++++++++++++++++++++++------
 arch/arm/boot/dts/am335x-evmsk.dts |   43 ++++++++++++++++++++++++-------
 arch/arm/boot/dts/am33xx.dtsi      |   14 +++++-----
 4 files changed, 108 insertions(+), 32 deletions(-)


             reply	other threads:[~2013-03-27 12:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 12:59 Vaibhav Hiremath [this message]
2013-03-27 12:59 ` [PATCH 1/5] ARM: dts: AM33XX: Fix the i2c numbering to match hardware/TRM Vaibhav Hiremath
2013-03-27 13:22   ` Peter Korsgaard
2013-03-28  5:18     ` Hiremath, Vaibhav
2013-03-27 12:59 ` [PATCH 2/5] ARM: dts: AM33XX: Add default pinctrl binding for I2C device Vaibhav Hiremath
2013-03-27 12:59 ` [PATCH 3/5] ARM: dts: AM33XX: Fix gpio numbering to match hardware/TRM Vaibhav Hiremath
2013-03-27 13:23   ` Peter Korsgaard
2013-03-27 14:11   ` Matt Porter
     [not found] ` <1364389156-8273-1-git-send-email-hvaibhav-l0cyMroinI0@public.gmane.org>
2013-03-27 12:59   ` [PATCH 4/5] ARM: dts: AM33XX: Add pinctrl binding to gpio-leds node Vaibhav Hiremath
2013-03-27 12:59 ` [PATCH 5/5] ARM: dts: AM33XX: Add default pinctrl binding for UART0 device Vaibhav Hiremath
     [not found] ` <686d89bc7b6d4bf1bc1c0524e4b586dd@DLEE51.ent.ti.com>
2013-03-27 13:28   ` [PATCH 1/5] ARM: dts: AM33XX: Fix the i2c numbering to match hardware/TRM Matt Porter
     [not found] ` <a20a6c7b5b5b45328684e5afab385ae5@DFLE51.ent.ti.com>
2013-03-27 13:29   ` [PATCH 2/5] ARM: dts: AM33XX: Add default pinctrl binding for I2C device Matt Porter
     [not found] ` <896a1261daec485db6be66630bc4019a@DFLE51.ent.ti.com>
2013-03-27 13:32   ` [PATCH 5/5] ARM: dts: AM33XX: Add default pinctrl binding for UART0 device Matt Porter
2013-03-28  5:17     ` Hiremath, Vaibhav

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=1364389156-8273-1-git-send-email-hvaibhav@ti.com \
    --to=hvaibhav@ti.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mporter@ti.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).