From: Mark Brown <broonie@kernel.org> To: Vincent Whitchurch <vincent.whitchurch@axis.com> Cc: krzysztof.kozlowski@linaro.org, andi@etezian.org, kernel@axis.com, alim.akhtar@samsung.com, linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 4/4] spi: s3c64xx: Fix large transfers with DMA Date: Mon, 26 Sep 2022 14:52:49 +0100 [thread overview] Message-ID: <YzGusRaUtlFLT/d/@sirena.org.uk> (raw) In-Reply-To: <YzGsRkyf9tyvjvBy@axis.com> [-- Attachment #1.1: Type: text/plain, Size: 437 bytes --] On Mon, Sep 26, 2022 at 03:42:30PM +0200, Vincent Whitchurch wrote: > On Mon, Sep 19, 2022 at 03:38:29PM +0100, Mark Brown wrote: > > The driver should just set max_transfer_size and let the core > > handle this. > Hmm, AFAICS, the core doesn't actually do anything with > max_transfer_size? It's only used from spi-mem and a handful of other > clients via spi_max_transfer_size(). Then we should fix the core to handle it properly. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --] [-- Attachment #2: Type: text/plain, Size: 176 bytes --] _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: Vincent Whitchurch <vincent.whitchurch@axis.com> Cc: krzysztof.kozlowski@linaro.org, andi@etezian.org, kernel@axis.com, alim.akhtar@samsung.com, linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 4/4] spi: s3c64xx: Fix large transfers with DMA Date: Mon, 26 Sep 2022 14:52:49 +0100 [thread overview] Message-ID: <YzGusRaUtlFLT/d/@sirena.org.uk> (raw) In-Reply-To: <YzGsRkyf9tyvjvBy@axis.com> [-- Attachment #1: Type: text/plain, Size: 437 bytes --] On Mon, Sep 26, 2022 at 03:42:30PM +0200, Vincent Whitchurch wrote: > On Mon, Sep 19, 2022 at 03:38:29PM +0100, Mark Brown wrote: > > The driver should just set max_transfer_size and let the core > > handle this. > Hmm, AFAICS, the core doesn't actually do anything with > max_transfer_size? It's only used from spi-mem and a handful of other > clients via spi_max_transfer_size(). Then we should fix the core to handle it properly. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-09-26 13:54 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-16 11:39 [PATCH 0/4] spi: Fix DMA bugs in (not only) spi-s3c64xx Vincent Whitchurch 2022-09-16 11:39 ` Vincent Whitchurch 2022-09-16 11:39 ` [PATCH 1/4] spi: spi-loopback-test: Add test to trigger DMA/PIO mixing Vincent Whitchurch 2022-09-16 11:39 ` Vincent Whitchurch 2022-09-19 14:41 ` Mark Brown 2022-09-19 14:41 ` Mark Brown 2022-09-16 11:39 ` [PATCH 2/4] spi: Save current RX and TX DMA devices Vincent Whitchurch 2022-09-16 11:39 ` Vincent Whitchurch 2022-09-16 11:39 ` [PATCH 3/4] spi: Fix cache corruption due to DMA/PIO overlap Vincent Whitchurch 2022-09-16 11:39 ` Vincent Whitchurch 2022-09-16 16:06 ` kernel test robot 2022-09-16 16:06 ` kernel test robot 2022-09-16 11:39 ` [PATCH 4/4] spi: s3c64xx: Fix large transfers with DMA Vincent Whitchurch 2022-09-16 11:39 ` Vincent Whitchurch 2022-09-19 9:43 ` Krzysztof Kozlowski 2022-09-19 9:43 ` Krzysztof Kozlowski 2022-09-19 14:38 ` Mark Brown 2022-09-19 14:38 ` Mark Brown 2022-09-26 13:42 ` Vincent Whitchurch 2022-09-26 13:42 ` Vincent Whitchurch 2022-09-26 13:52 ` Mark Brown [this message] 2022-09-26 13:52 ` Mark Brown 2022-09-19 16:50 ` (subset) [PATCH 0/4] spi: Fix DMA bugs in (not only) spi-s3c64xx Mark Brown 2022-09-19 16:50 ` 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=YzGusRaUtlFLT/d/@sirena.org.uk \ --to=broonie@kernel.org \ --cc=alim.akhtar@samsung.com \ --cc=andi@etezian.org \ --cc=kernel@axis.com \ --cc=krzysztof.kozlowski@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=linux-spi@vger.kernel.org \ --cc=vincent.whitchurch@axis.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: linkBe 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.