From: Leilk Liu <leilk.liu@mediatek.com>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-spi@vger.kernel.org>, <linux-mediatek@lists.infradead.org>
Subject: [PATCH V6 0/3] spi: mediatek: add single/quad mode support
Date: Mon, 21 Mar 2022 09:39:19 +0800 [thread overview]
Message-ID: <20220321013922.24067-1-leilk.liu@mediatek.com> (raw)
This series of patches are based on spi for-next, and provide 3 patches to support MT7986.
V6:
1. remove SPI_CFG3_IPM_PIN_MODE_OFFSET.
2. add Reviewed-by: AngeloGioacchino Del Regno
V5:
1. remove 3 patches that already applied.
2. use devm_clk_get_optional.
3. remove of_mtk_spi_parse_dt()
v4:
1. fix Rob comment in v3;
2. use "mediatek,mt7986-spi-ipm","mediatek,spi-ipm"
v3:
1. add Rob Acked-by in "dt-bindings: spi: Add compatible for MT7986 with single mode";
2. add a fix patch "spi: mediatek: support tick_delay without enhance_timing";
3. fix Angelogioacchino comments;
4. use mt7986 instead of ipm in dt-binding.
v2:
1. rebase this series on spi for-next.
2. fix Rob and Krzysztof comments in v1.
Leilk Liu (3):
spi: mediatek: add spi memory support for ipm design
dt-bindings: spi: support hclk
spi: mediatek: support hclk
.../bindings/spi/mediatek,spi-mt65xx.yaml | 4 +
drivers/spi/spi-mt65xx.c | 386 +++++++++++++++++-
2 files changed, 373 insertions(+), 17 deletions(-)
--
2.25.1
next reply other threads:[~2022-03-21 1:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 1:39 Leilk Liu [this message]
2022-03-21 1:39 ` [PATCH V6 1/3] spi: mediatek: add spi memory support for ipm design Leilk Liu
2022-03-21 1:39 ` [PATCH V6 2/3] dt-bindings: spi: support hclk Leilk Liu
2022-03-21 23:30 ` Rob Herring
2022-03-21 1:39 ` [PATCH V6 3/3] spi: mediatek: " Leilk Liu
2022-04-05 9:32 ` [PATCH V6 0/3] spi: mediatek: add single/quad mode support 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=20220321013922.24067-1-leilk.liu@mediatek.com \
--to=leilk.liu@mediatek.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-mediatek@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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).