dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Meghana Madhyastha <meghana.madhyastha@gmail.com>
To: "Mark Brown" <broonie@kernel.org>,
	"Daniel Vetter" <daniel.vetter@intel.com>,
	linux-spi@vger.kernel.org, "Noralf Trønnes" <noralf@tronnes.org>,
	"Sean Paul" <seanpaul@chromium.org>,
	dri-devel@lists.freedesktop.org
Subject: [PATCH v3 0/2] Chunk splitting of spi transfers
Date: Mon, 12 Mar 2018 09:53:30 +0000	[thread overview]
Message-ID: <cover.1520848302.git.meghana.madhyastha@gmail.com> (raw)

-Call spi_split_transfers_maxsize in __spi_pump_messages
to split large chunks for spi dma transfers.
-Remove chunk splitting in the tinydrm spi helper (as now the core is
handling the chunk splitting).

Changes in v3:
-Remove max_chunk 
-Remove tinydrm_spi_max_transfer_size()                        
-Change master->max_dma_len in patch 0/2 and explain why it is changed

Meghana Madhyastha (2):
  spi: Split spi message into chunks of <65535 in the spi subsystem
  drm/tinydrm: Remove chunk splitting in tinydrm_spi_transfer

 drivers/gpu/drm/tinydrm/core/tinydrm-helpers.c | 80 ++------------------------
 drivers/gpu/drm/tinydrm/mipi-dbi.c             | 10 +---
 drivers/spi/spi-bcm2835.c                      | 22 +++----
 3 files changed, 16 insertions(+), 96 deletions(-)

-- 
2.11.0

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-03-12  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12  9:53 Meghana Madhyastha [this message]
2018-03-12  9:54 ` [PATCH v3 1/2] spi: Split spi message into chunks of <65535 in the spi subsystem Meghana Madhyastha
2018-03-16 23:55   ` Eric Anholt
2018-03-12  9:54 ` [PATCH v3 2/2] drm/tinydrm: Remove chunk splitting in tinydrm_spi_transfer Meghana Madhyastha

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=cover.1520848302.git.meghana.madhyastha@gmail.com \
    --to=meghana.madhyastha@gmail.com \
    --cc=broonie@kernel.org \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=noralf@tronnes.org \
    --cc=seanpaul@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox