From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Subject: [PATCH v3 0/2] Introduce Socionext F_OSPI SPI flash controller
Date: Thu, 24 Nov 2022 09:33:49 +0900 [thread overview]
Message-ID: <20221124003351.7792-1-hayashi.kunihiko@socionext.com> (raw)
This series adds dt-bindings and a driver for Socionext F_OSPI controller
for connecting an SPI Flash memory over up to 8-bit wide bus.
The controller supports up to 4 chip selects.
Changes since v2:
- Drop a redundant word in the subject line
- Drop quotes of referenceing URL in dt-bindings
- Add Reviewed-by line to dt-bindings patch
Changes since v1:
- Drop vendor-specific properties for devices from host dt-bindings
- Drop a function to parse vendor-specific properties
- Fix wrong maximum addr.bytes (5 to 4)
Kunihiko Hayashi (2):
dt-bindings: spi: Add Socionext F_OSPI controller
spi: Add Socionext F_OSPI SPI flash controller driver
.../bindings/spi/socionext,f-ospi.yaml | 57 ++
drivers/spi/Kconfig | 9 +
drivers/spi/Makefile | 1 +
drivers/spi/spi-sn-f-ospi.c | 703 ++++++++++++++++++
4 files changed, 770 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/socionext,f-ospi.yaml
create mode 100644 drivers/spi/spi-sn-f-ospi.c
--
2.25.1
next reply other threads:[~2022-11-24 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 0:33 Kunihiko Hayashi [this message]
2022-11-24 0:33 ` [PATCH v3 1/2] dt-bindings: spi: Add Socionext F_OSPI controller Kunihiko Hayashi
2022-11-24 0:33 ` [PATCH v3 2/2] spi: Add Socionext F_OSPI SPI flash controller driver Kunihiko Hayashi
2022-11-29 16:49 ` Geert Uytterhoeven
2022-11-30 0:47 ` Kunihiko Hayashi
2022-11-30 8:46 ` Geert Uytterhoeven
2022-11-24 13:27 ` [PATCH v3 0/2] Introduce Socionext F_OSPI SPI flash controller 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=20221124003351.7792-1-hayashi.kunihiko@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.