From: Beniamino Galvani <b.galvani@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, Carlo Caione <carlo@caione.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Jerry Cao <jerry.cao@amlogic.com>,
Victor Wan <victor.wan@amlogic.com>,
Beniamino Galvani <b.galvani@gmail.com>
Subject: [PATCH v3 0/4] spi: Add support for Amlogic Meson SPIFC
Date: Sat, 22 Nov 2014 16:21:38 +0100 [thread overview]
Message-ID: <1416669702-7841-1-git-send-email-b.galvani@gmail.com> (raw)
Hi,
this patchset adds a driver for the SPIFC (SPI flash controller)
available in Amlogic Meson6 and Meson8 SoCs. The driver has been
tested on a Meson8 based device to communicate with a Macronix
mx25l1606e serial flash.
Changes since v2 [ https://lkml.org/lkml/2014/11/17/669 ]:
- introduce spi_transfer_is_last() helper instead of using a flag
in spi_transfer structure
- rebase DTS patch on arm-soc
Changes since v1 [ https://lkml.org/lkml/2014/11/9/35 ]:
- decrease busy wait timeout
- remove check on xfer->speed_hz value in meson_spifc_transfer_one()
- implement transfer_one() instead of transfer_one_message()
- remove useless memset of devdata
- use fixed regmap config
- implement PM operations
- don't set master->bus_num
- allow modular build of the driver
Beniamino Galvani (4):
spi: core: Add spi_transfer_is_last() helper
spi: meson: Add device tree bindings documentation for SPIFC
spi: meson: Add support for Amlogic Meson SPIFC
ARM: dts: meson: add node for SPIFC
.../devicetree/bindings/spi/spi-meson.txt | 22 +
arch/arm/boot/dts/meson.dtsi | 9 +
drivers/spi/Kconfig | 7 +
drivers/spi/Makefile | 1 +
drivers/spi/spi-meson-spifc.c | 462 +++++++++++++++++++++
include/linux/spi/spi.h | 6 +
6 files changed, 507 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-meson.txt
create mode 100644 drivers/spi/spi-meson-spifc.c
--
1.9.1
next reply other threads:[~2014-11-22 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 15:21 Beniamino Galvani [this message]
2014-11-22 15:21 ` [PATCH v3 1/4] spi: core: Add spi_transfer_is_last() helper Beniamino Galvani
2014-11-24 18:53 ` Mark Brown
2014-11-22 15:21 ` [PATCH v3 2/4] spi: meson: Add device tree bindings documentation for SPIFC Beniamino Galvani
2014-11-24 18:54 ` Mark Brown
2014-11-22 15:21 ` [PATCH v3 3/4] spi: meson: Add support for Amlogic Meson SPIFC Beniamino Galvani
[not found] ` <1416669702-7841-4-git-send-email-b.galvani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-24 18:55 ` Mark Brown
2014-11-22 15:21 ` [PATCH v3 4/4] ARM: dts: meson: add node for SPIFC Beniamino Galvani
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=1416669702-7841-1-git-send-email-b.galvani@gmail.com \
--to=b.galvani@gmail.com \
--cc=broonie@kernel.org \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jerry.cao@amlogic.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=victor.wan@amlogic.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).