From: Vinod Koul <vkoul@kernel.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: 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 0/2] dmaengine: ti: k3-udma: Support for per channel atype
Date: Mon, 2 Mar 2020 14:44:28 +0530 [thread overview]
Message-ID: <20200302091428.GI4148@vkoul-mobl> (raw)
In-Reply-To: <20200218143126.11361-1-peter.ujfalusi@ti.com>
On 18-02-20, 16:31, Peter Ujfalusi wrote:
> Hi,
>
> The series is on top of the 5.6 update patches:
> https://lore.kernel.org/lkml/20200214091441.27535-1-peter.ujfalusi@ti.com/
>
> UDMA channels have ATYPE property which tells UDMA on how to treat the pointers
> within descriptors (and TRs).
> The ATYPE defined for j721e are:
> 0: pointers are physical addresses (no translation)
> 1: pointers are intermediate addresses (PVU)
> 2: pointers are virtual addresses (SMMU)
>
> When Linux is booting within a virtualized environment channels must have the
> ATYPE configured correctly to be able to access memory (ATYPE == 0 is not
> allowed).
> The ATYPE can be different for channels and their ATYPE depends on which
> endpoint they are servicing, but it is not hardwired.
>
> In order to be able to tell the driver the ATYPE for the channel we need to
> extend the dma-cells in case the device is going to be used in virtualized
> setup.
>
> Non virtualized setups can still use dma-cells == 1.
>
> If dma-cells == 2, then the UDMA node must have ti,udma-atype property which
> is used for non slave channels (where no DT binding is exist for a channel).
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2020-03-02 9:14 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
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 ` Vinod Koul [this message]
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=20200302091428.GI4148@vkoul-mobl \
--to=vkoul@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 \
/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