From: Michal Suchanek <hramrach@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Han Xu <han.xu@freescale.com>, Mark Brown <broonie@kernel.org>,
Michal Suchanek <hramrach@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Javier Martinez Canillas <javier@osg.samsung.com>,
"Rafal Milecki" <zajec5@gmail.com>,
Jagan Teki <jteki@openedev.com>, "Andrew F. Davis" <afd@ti.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Gabor Juhos <juhosg@openwrt.org>,
"Bean Huo " <beanhuo@micron.com>,
Furquan Shaikh <furquan@google.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org,
Subject: [PATCH v6 09/10] spi: fsl-espi: expose maximum transfer size limit
Date: 2 Dec 2015 10:38:21 -0000 [thread overview]
Message-ID: <515f8373f20ed814f8761ebadfec0e306517b0e3.1449052427.git.hramrach@gmail.com> (raw)
In-Reply-To: <cover.1449052427.git.hramrach@gmail.com>
The fsl-espi hardware can trasfer at most 64K data so report teh
limitation.
Based on patch by Heiner Kallweit <hkallweit1@gmail.com>
CC: Heiner Kallweit <hkallweit1@gmail.com>
Signed-off-by: Michal Suchanek <hramrach@gmail.com>
---
drivers/spi/spi-fsl-espi.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/spi/spi-fsl-espi.c b/drivers/spi/spi-fsl-espi.c
index c27124a..7fd6a4c 100644
--- a/drivers/spi/spi-fsl-espi.c
+++ b/drivers/spi/spi-fsl-espi.c
@@ -643,6 +643,11 @@ static int fsl_espi_runtime_resume(struct device *dev)
}
#endif
+static size_t fsl_espi_max_transfer_size(struct spi_device *spi)
+{
+ return SPCOM_TRANLEN_MAX;
+}
+
static struct spi_master * fsl_espi_probe(struct device *dev,
struct resource *mem, unsigned int irq)
{
@@ -670,6 +675,7 @@ static struct spi_master * fsl_espi_probe(struct device *dev,
master->cleanup = fsl_espi_cleanup;
master->transfer_one_message = fsl_espi_do_one_msg;
master->auto_runtime_pm = true;
+ master->max_transfer_size = fsl_espi_max_transfer_size;
mpc8xxx_spi = spi_master_get_devdata(master);
--
2.6.2
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2015-12-02 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 10:38 [PATCH v6 00/10] Add error checking to spi-nor read and write Michal Suchanek
2015-12-02 10:38 ` [PATCH v6 03/10] mtd: fsl-quadspi: return amount of data read/written or error Michal Suchanek
2015-12-02 21:06 ` Han Xu
2015-12-02 23:07 ` Brian Norris
2015-12-02 10:38 ` [PATCH v6 02/10] mtd: m25p80: return amount of data transferred or error in read/write Michal Suchanek
2015-12-02 10:38 ` [PATCH v6 01/10] mtd: spi-nor: change return value of read/write Michal Suchanek
2015-12-02 10:38 ` [PATCH v6 07/10] mtd: spi-nor: add read loop Michal Suchanek
2015-12-02 10:38 ` [PATCH v6 04/10] mtd: spi-nor: check return value from read/write Michal Suchanek
2015-12-02 10:38 ` [PATCH v6 05/10] mtd: spi-nor: stop passing around retlen Michal Suchanek
2015-12-02 10:38 ` [PATCH v6 06/10] mtd: spi-nor: simplify write loop Michal Suchanek
[not found] ` <2236d87ad516f118f58eb5df232d441f970c4499.1449052427.git.hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-15 20:22 ` Han Xu
2015-12-15 23:45 ` Michal Suchanek
2015-12-02 10:38 ` [PATCH v6 08/10] spi: expose master transfer size limitation Michal Suchanek
2015-12-02 10:38 ` Michal Suchanek [this message]
2015-12-02 10:38 ` [PATCH v6 10/10] mtd: m25p80: read in spi_max_transfer_size chunks Michal Suchanek
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=515f8373f20ed814f8761ebadfec0e306517b0e3.1449052427.git.hramrach@gmail.com \
--to=hramrach@gmail.com \
--cc=afd@ti.com \
--cc=beanhuo@micron.com \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=furquan@google.com \
--cc=han.xu@freescale.com \
--cc=hkallweit1@gmail.com \
--cc=javier@osg.samsung.com \
--cc=jteki@openedev.com \
--cc=juhosg@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=zajec5@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).