From: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>
To: broonie@kernel.org, robh+dt@kernel.org, krzk+dt@kernel.org
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, paul@crapouillou.net,
contact@artur-rojek.eu, dongsheng.qiu@ingenic.com,
aric.pzqi@ingenic.com, rick.tyliu@ingenic.com,
sernia.zhou@foxmail.com, zhenwenjin@gmail.com,
reimu@sudomaker.com
Subject: [PATCH v2 0/3] Improve SPI support for Ingenic SoCs.
Date: Sat, 23 Apr 2022 03:09:40 +0800 [thread overview]
Message-ID: <1650654583-89933-1-git-send-email-zhouyanjie@wanyeetech.com> (raw)
1.Add support for using GPIOs as chip select lines on Ingenic SoCs.
2.Add support for probing the spi-ingenic driver on the JZ4775 SoC,
the X1000 SoC, and the X2000 SoC.
3.Modify annotation texts to be more in line with the current state.
v1->v2:
Use "device_property_read_u32()" instead "of_property_read_u32()" as
Paul Cercueil's suggestion.
周琰杰 (Zhou Yanjie) (3):
SPI: Ingenic: Add support for use GPIO as chip select line.
dt-bindings: SPI: Add bindings for new Ingenic SoCs.
SPI: Ingenic: Add support for new Ingenic SoCs.
.../devicetree/bindings/spi/ingenic,spi.yaml | 3 ++
drivers/spi/Kconfig | 4 +-
drivers/spi/spi-ingenic.c | 49 +++++++++++++++++++---
3 files changed, 49 insertions(+), 7 deletions(-)
--
2.7.4
next reply other threads:[~2022-04-22 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 19:09 周琰杰 (Zhou Yanjie) [this message]
2022-04-22 19:09 ` [PATCH v2 1/3] SPI: Ingenic: Add support for use GPIO as chip select line 周琰杰 (Zhou Yanjie)
2022-04-22 19:20 ` Paul Cercueil
2022-04-23 12:54 ` Zhou Yanjie
2022-04-22 19:09 ` [PATCH v2 2/3] dt-bindings: SPI: Add bindings for new Ingenic SoCs 周琰杰 (Zhou Yanjie)
2022-04-22 19:09 ` [PATCH v2 3/3] SPI: Ingenic: Add support " 周琰杰 (Zhou Yanjie)
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=1650654583-89933-1-git-send-email-zhouyanjie@wanyeetech.com \
--to=zhouyanjie@wanyeetech.com \
--cc=aric.pzqi@ingenic.com \
--cc=broonie@kernel.org \
--cc=contact@artur-rojek.eu \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.qiu@ingenic.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=reimu@sudomaker.com \
--cc=rick.tyliu@ingenic.com \
--cc=robh+dt@kernel.org \
--cc=sernia.zhou@foxmail.com \
--cc=zhenwenjin@gmail.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).