From: Franklin S Cooper Jr <fcooper@ti.com>
To: broonie@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
ssantosh@kernel.org, linux@armlinux.org.uk,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Franklin S Cooper Jr <fcooper@ti.com>
Subject: [PATCH 0/3] ARM: dts: keystone-k2g-evm: Add SPI nodes and enable SPI1 on K2G EVM
Date: Fri, 8 Sep 2017 15:46:35 -0500 [thread overview]
Message-ID: <20170908204638.13149-1-fcooper@ti.com> (raw)
Update the binding document to indicate the required requirements
for 66AK2G. In addition add the proper SPI nodes for 66AK2G. For K2G
EVM enable SPI1 which is used for the on board SPI NOR.
Franklin S Cooper Jr (1):
dt-bindings: spi: spi-davinci: Update binding for 66AK2Gx pwr dm
property
Murali Karicheri (1):
ARM: dts: keystone-k2g-evm: add bindings for SPI NOR flash
Vitaly Andrianov (1):
ARM: dts: keystone-k2g: Add SPI nodes
.../devicetree/bindings/spi/spi-davinci.txt | 10 +++++
arch/arm/boot/dts/keystone-k2g-evm.dts | 37 +++++++++++++++++
arch/arm/boot/dts/keystone-k2g.dtsi | 48 ++++++++++++++++++++++
3 files changed, 95 insertions(+)
--
2.9.4.dirty
next reply other threads:[~2017-09-08 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 20:46 Franklin S Cooper Jr [this message]
[not found] ` <20170908204638.13149-1-fcooper-l0cyMroinI0@public.gmane.org>
2017-09-08 20:46 ` [PATCH 1/3] dt-bindings: spi: spi-davinci: Update binding for 66AK2Gx pwr dm property Franklin S Cooper Jr
2017-09-18 19:29 ` Rob Herring
[not found] ` <20170908204638.13149-2-fcooper-l0cyMroinI0@public.gmane.org>
2017-09-19 12:35 ` Mark Brown
2017-09-19 13:47 ` Applied "spi: spi-davinci: Update binding for 66AK2Gx pwr dm property" to the spi tree Mark Brown
2017-09-08 20:46 ` [PATCH 2/3] ARM: dts: keystone-k2g: Add SPI nodes Franklin S Cooper Jr
2017-09-08 20:46 ` [PATCH 3/3] ARM: dts: keystone-k2g-evm: add bindings for SPI NOR flash Franklin S Cooper Jr
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=20170908204638.13149-1-fcooper@ti.com \
--to=fcooper@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@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).