public inbox for dmaengine@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <vkoul@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <dan.j.williams@intel.com>
Subject: [PATCH 0/2] dmaengine: ti: k3-udma: Get supported throughput levels from hardware
Date: Fri, 17 Jul 2020 15:09:01 +0300	[thread overview]
Message-ID: <20200717120903.8774-1-peter.ujfalusi@ti.com> (raw)

Hi,

Newer versions of UDMAP have information on the number of different throughput
channels in it's CAP registers.

The driver can auto configure based on the information from the hardware isntead
a table within the match_data.

With this change we can use the same compatible string for identical versions of
UDMAP when only the number of UHCHAN and HCHAN is different.

Regards,
Peter
---
Peter Ujfalusi (2):
  dmaengine: ti: k3-udma: Use defines for capabilities register parsing
  dmaengine: ti: k3-udma: Query throughput level information from
    hardware

 drivers/dma/ti/k3-udma.c | 69 ++++++++++++++++++++--------------------
 drivers/dma/ti/k3-udma.h |  8 +++++
 2 files changed, 42 insertions(+), 35 deletions(-)

-- 
Peter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki


             reply	other threads:[~2020-07-17 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 12:09 Peter Ujfalusi [this message]
2020-07-17 12:09 ` [PATCH 1/2] dmaengine: ti: k3-udma: Use defines for capabilities register parsing Peter Ujfalusi
2020-07-17 12:09 ` [PATCH 2/2] dmaengine: ti: k3-udma: Query throughput level information from hardware Peter Ujfalusi
2020-07-27  8:53 ` [PATCH 0/2] dmaengine: ti: k3-udma: Get supported throughput levels " Vinod Koul

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=20200717120903.8774-1-peter.ujfalusi@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=vkoul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox