From: Rob Herring <robh@kernel.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: vkoul@kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, dan.j.williams@intel.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/3] dt-bindings: dma: ti-edma: Document dma-channel-mask for EDMA
Date: Fri, 27 Sep 2019 15:48:54 -0500 [thread overview]
Message-ID: <20190927204854.GA20463@bogus> (raw)
In-Reply-To: <20190926111954.9184-3-peter.ujfalusi@ti.com>
On Thu, Sep 26, 2019 at 02:19:53PM +0300, Peter Ujfalusi wrote:
> Similarly to paRAM slots, channels can be used by other cores.
>
> The common dma-channel-mask property can be used for specifying the
> available channels.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
> Documentation/devicetree/bindings/dma/ti-edma.txt | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/dma/ti-edma.txt b/Documentation/devicetree/bindings/dma/ti-edma.txt
> index 4bbc94d829c8..014187088020 100644
> --- a/Documentation/devicetree/bindings/dma/ti-edma.txt
> +++ b/Documentation/devicetree/bindings/dma/ti-edma.txt
> @@ -42,6 +42,11 @@ Optional properties:
> - ti,edma-reserved-slot-ranges: PaRAM slot ranges which should not be used by
> the driver, they are allocated to be used by for example the
> DSP. See example.
> +- dma-channel-mask: Mask of usable channels.
> + Single uint32 for EDMA with 32 channels, array of two uint32 for
> + EDMA with 64 channels. See example and
> + Documentation/devicetree/bindings/dma/dma-common.yaml
> +
>
> ------------------------------------------------------------------------------
> eDMA3 Transfer Controller
> @@ -91,6 +96,9 @@ edma: edma@49000000 {
> ti,edma-memcpy-channels = <20 21>;
> /* The following PaRAM slots are reserved: 35-44 and 100-109 */
> ti,edma-reserved-slot-ranges = <35 10>, <100 10>;
> + /* The following channels are reserved: 35-44 */
> + dma-channel-mask = <0xffffffff>, /* Channel 0-31 */
> + <0xffffe007>; /* Channel 32-63 */
Doesn't matter yet, but you have a mismatch here with the schema. While
the <> around each int or not doesn't matter for the dtb, it does for
the schema.
dma-channel-mask = <0xffffffff>, <0xffffe007>;
minItems: 1
maxItems: 255
dma-channel-mask = <0xffffffff 0xffffe007>;
items:
minItems: 1
maxItems: 255
I think the latter case is slightly more logical here as you have 1
thing (a mask). If had N of something (like interrupts), then the former
makes sense.
Rob
next prev parent reply other threads:[~2019-09-27 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 11:19 [PATCH v3 0/3] dmaengine: bindings/edma: dma-channel-mask to array Peter Ujfalusi
2019-09-26 11:19 ` [PATCH v3 1/3] dt-bindings: dmaengine: dma-common: Change dma-channel-mask to uint32-array Peter Ujfalusi
2019-09-27 20:25 ` Rob Herring
2019-09-26 11:19 ` [PATCH v3 2/3] dt-bindings: dma: ti-edma: Document dma-channel-mask for EDMA Peter Ujfalusi
2019-09-27 20:48 ` Rob Herring [this message]
2019-09-30 10:55 ` Peter Ujfalusi
2019-09-26 11:19 ` [PATCH v3 3/3] dmaengine: ti: edma: Add support for handling reserved channels Peter Ujfalusi
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=20190927204854.GA20463@bogus \
--to=robh@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--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).