From: leilk.liu@mediatek.com (Leilk Liu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/3] Add Mediatek SPI slave driver
Date: Fri, 28 Sep 2018 18:53:02 +0800 [thread overview]
Message-ID: <1538131985-9471-1-git-send-email-leilk.liu@mediatek.com> (raw)
>From 5479c692171dc52990290d88c505c074fa4db7d4 Mon Sep 17 00:00:00 2001
From: Leilk Liu <leilk.liu@mediatek.com>
Date: Fri, 28 Sep 2018 18:37:40 +0800
Subject: [PATCH v5 0/3] Add Mediatek SPI slave driver
v5:
1. Fix typos in bindings file.
v4:
1. Fix Mark Brown review comment about kconfig & driver.
v3:
1. Fix Rob Herring review comment about bindings.
2. remove unused variables in driver.
v2:
1. Fix Sean Wang review comment.
2. remove unused register and offset define.
3. update bindings file with assigned-clocks and assigned-clocks-parents.
v1:
This series are based on 4.19-rc1 and provide three patches to add mediatek spi slave driver.
Leilk Liu (3):
spi: mediatek: add bindings for Mediatek MT2712 soc platform
spi: mediatek: add spi slave for Mediatek MT2712
arm64: dts: Add spi slave dts
.../devicetree/bindings/spi/spi-slave-mt27xx.txt | 32 ++
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 11 +
drivers/spi/Kconfig | 10 +
drivers/spi/Makefile | 1 +
drivers/spi/spi-slave-mt27xx.c | 554 +++++++++++++++++++++
5 files changed, 608 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-slave-mt27xx.txt
create mode 100644 drivers/spi/spi-slave-mt27xx.c
--
1.9.1
next reply other threads:[~2018-09-28 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 10:53 Leilk Liu [this message]
2018-09-28 10:53 ` [PATCH v5 1/3] spi: mediatek: add bindings for Mediatek MT2712 soc platform Leilk Liu
2018-09-28 14:05 ` Applied "spi: mediatek: add bindings for Mediatek MT2712 soc platform" to the spi tree Mark Brown
2018-09-28 10:53 ` [PATCH v5 2/3] spi: mediatek: add spi slave for Mediatek MT2712 Leilk Liu
2018-09-28 10:53 ` [PATCH v5 3/3] arm64: dts: Add spi slave dts Leilk Liu
2018-09-28 21:07 ` Matthias Brugger
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=1538131985-9471-1-git-send-email-leilk.liu@mediatek.com \
--to=leilk.liu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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).