From: Rob Herring <robh@kernel.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: vkoul@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
dan.j.williams@intel.com, grygorii.strashko@ti.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: dma: ti: k3-udma: Update for atype support (virtualization)
Date: Wed, 26 Feb 2020 09:21:23 -0600 [thread overview]
Message-ID: <20200226152123.GA25719@bogus> (raw)
In-Reply-To: <20200218143126.11361-2-peter.ujfalusi@ti.com>
On Tue, 18 Feb 2020 16:31:25 +0200, Peter Ujfalusi wrote:
> In UDMA each channel can use different ATYPE value which tells UDMA how
> the addresses in the descriptors should be treated:
> 0: pointers are physical addresses (no translation)
> 1: pointers are intermediate addresses (PVU)
> 2: pointers are virtual addresses (SMMU)
>
> When virtualized environment is used then the dma binding should use
> additional cell to configure the desired ATYPE for the channel.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
> .../devicetree/bindings/dma/ti/k3-udma.yaml | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-02-26 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 14:31 [PATCH 0/2] dmaengine: ti: k3-udma: Support for per channel atype Peter Ujfalusi
2020-02-18 14:31 ` [PATCH 1/2] dt-bindings: dma: ti: k3-udma: Update for atype support (virtualization) Peter Ujfalusi
2020-02-26 15:21 ` Rob Herring [this message]
2020-02-18 14:31 ` [PATCH 2/2] dmaengine: ti: k3-udma: Implement support for atype (for virtualization) Peter Ujfalusi
2020-03-02 9:14 ` [PATCH 0/2] dmaengine: ti: k3-udma: Support for per channel atype 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=20200226152123.GA25719@bogus \
--to=robh@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).