From: Neil Armstrong <narmstrong@baylibre.com>
To: Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Brian Hutchinson <b.hutchman@gmail.com>,
fisaksen@baylibre.com, devicetree@vger.kernel.org
Subject: [PATCH 0/4] arm: dts: complete dm816x device tree
Date: Thu, 22 Oct 2015 11:19:05 +0200 [thread overview]
Message-ID: <5628AA09.506@baylibre.com> (raw)
In order to fix support for the dm816x platform, add missing bits in
the dm816x dtsi.
The last patch adds support for the omap4-hwspinlock.
Neil Armstrong (4):
arm: dts: add dm816x missing #mbox-cells
arm: dts: add dm816x missing spi DT dma handles
arm: dts: add dm816x pwm property to timers
arm: dts: Add omap4-hwspinlock support in dm816x
arch/arm/boot/dts/dm816x.dtsi | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: narmstrong@baylibre.com (Neil Armstrong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm: dts: complete dm816x device tree
Date: Thu, 22 Oct 2015 11:19:05 +0200 [thread overview]
Message-ID: <5628AA09.506@baylibre.com> (raw)
In order to fix support for the dm816x platform, add missing bits in
the dm816x dtsi.
The last patch adds support for the omap4-hwspinlock.
Neil Armstrong (4):
arm: dts: add dm816x missing #mbox-cells
arm: dts: add dm816x missing spi DT dma handles
arm: dts: add dm816x pwm property to timers
arm: dts: Add omap4-hwspinlock support in dm816x
arch/arm/boot/dts/dm816x.dtsi | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
--
1.9.1
next reply other threads:[~2015-10-22 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 9:19 Neil Armstrong [this message]
2015-10-22 9:19 ` [PATCH 0/4] arm: dts: complete dm816x device tree Neil Armstrong
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=5628AA09.506@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=b.hutchman@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fisaksen@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.