From: addy ke <addy.ke@rock-chips.com>
To: broonie@kernel.org, heiko@sntech.de, grant.likely@linaro.org,
robh+dt@kernel.org
Cc: huangtao@rock-chips.com, devicetree@vger.kernel.org,
addy ke <addy.ke@rock-chips.com>,
yzq@rock-chips.com, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, kever.yang@rock-chips.com,
zyw@rock-chips.com, xjq@rock-chips.com,
zhenfu.fang@rock-chips.com, olof@lixom.net, cf@rock-chips.com,
hj@rock-chips.com, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] add rockchip spi drive
Date: Tue, 24 Jun 2014 11:58:42 +0800 [thread overview]
Message-ID: <1403582324-9485-1-git-send-email-addy.ke@rock-chips.com> (raw)
Patch 1 add rockchip spi documentation
Patch 2 add driver for Rockchip RK3XXX SoCs integrated SPI.
Tested on rk3288 sdk board with polling mode and DMA mode.
addy ke (2):
documentation: add rockchip spi documentation
spi: add driver for Rockchip RK3xxx SoCs integrated SPI
.../devicetree/bindings/spi/spi-rockchip.txt | 51 ++
drivers/spi/Kconfig | 11 +
drivers/spi/Makefile | 1 +
drivers/spi/spi-rockchip.c | 894 +++++++++++++++++++++
4 files changed, 957 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-rockchip.txt
create mode 100644 drivers/spi/spi-rockchip.c
--
1.8.3.2
next reply other threads:[~2014-06-24 3:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 3:58 addy ke [this message]
2014-06-24 3:58 ` [PATCH 1/2] documentation: add rockchip spi documentation addy ke
[not found] ` <1403582324-9485-2-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-06-24 10:18 ` Mark Rutland
2014-06-24 10:32 ` Heiko Stübner
2014-06-24 10:47 ` Mark Rutland
2014-06-24 10:33 ` Mark Brown
2014-07-01 1:02 ` [PATCH v2 " addy ke
[not found] ` <1403582324-9485-1-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-06-24 4:07 ` [PATCH 2/2] spi: add driver for Rockchip RK3xxx SoCs integrated SPI addy ke
[not found] ` <1403582852-9751-1-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-06-24 10:56 ` Mark Brown
2014-07-01 1:03 ` [PATCH v2 " addy ke
[not found] ` <1404176639-3315-1-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-07-04 18:32 ` Mark Brown
[not found] ` <20140704183249.GC14896-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-05 18:56 ` Jonas Gorski
2014-07-07 1:42 ` addy ke
2014-07-07 7:08 ` Heiko Stübner
2014-07-07 7:21 ` Mark Brown
[not found] ` <20140707072140.GB30458-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-07 7:26 ` Heiko Stübner
[not found] ` <53B9FB1C.7080008-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-07-07 7:16 ` Mark Brown
2014-07-08 1:53 ` [PATCH v3 " Addy Ke
[not found] ` <1404784397-5157-1-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-07-08 14:56 ` Mark Brown
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=1403582324-9485-1-git-send-email-addy.ke@rock-chips.com \
--to=addy.ke@rock-chips.com \
--cc=broonie@kernel.org \
--cc=cf@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=hj@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=xjq@rock-chips.com \
--cc=yzq@rock-chips.com \
--cc=zhenfu.fang@rock-chips.com \
--cc=zyw@rock-chips.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).