From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <arnd@arndb.de>, <tony@atomide.com>
Cc: <nsekhar@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<vinod.koul@intel.com>, <balbi@ti.com>,
<linux-omap@vger.kernel.org>
Subject: [PATCH v02 0/2] ARM: DTS: am33xx/am437x: Use the new eDMA bindings
Date: Thu, 17 Dec 2015 15:33:35 +0200 [thread overview]
Message-ID: <1450359217-3038-1-git-send-email-peter.ujfalusi@ti.com> (raw)
Hi,
Changes since v1:
- Updated to use the non 16bit arrays [1]
- send the two patch as a series
[1]
As it has been discussed earlier:
https://www.mail-archive.com/linux-omap@vger.kernel.org/msg122117.html
the DT bindings has been changes compared to what we had in 4.4-rc1: the arrays
now don't have the 16bit type.
The changes are now merged to mainline and Vinod provided us a branch:
git://git.infradead.org/users/vkoul/slave-dma.git fix/edma
Which is based on 4.4-rc1 and only contains the two patch for changing the eDMA
bindings.
Regards,
Peter
---
Peter Ujfalusi (2):
ARM: DTS: am33xx: Use the new DT bindings for the eDMA3
ARM: DTS: am437x: Use the new DT bindings for the eDMA3
arch/arm/boot/dts/am335x-evm.dts | 9 +---
arch/arm/boot/dts/am335x-pepper.dts | 11 +----
arch/arm/boot/dts/am33xx.dtsi | 94 ++++++++++++++++++++++++++-----------
arch/arm/boot/dts/am4372.dtsi | 80 +++++++++++++++++++++++--------
arch/arm/boot/dts/am437x-gp-evm.dts | 9 +---
5 files changed, 133 insertions(+), 70 deletions(-)
--
2.6.4
next reply other threads:[~2015-12-17 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 13:33 Peter Ujfalusi [this message]
2015-12-17 13:33 ` [PATCH v02 1/2] ARM: DTS: am33xx: Use the new DT bindings for the eDMA3 Peter Ujfalusi
2015-12-17 13:33 ` [PATCH v02 2/2] ARM: DTS: am437x: " Peter Ujfalusi
2015-12-17 17:48 ` [PATCH v02 0/2] ARM: DTS: am33xx/am437x: Use the new eDMA bindings Tony Lindgren
2015-12-18 5:18 ` Vinod Koul
2015-12-18 13:46 ` Tony Lindgren
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=1450359217-3038-1-git-send-email-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=tony@atomide.com \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®