From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: <robh+dt@kernel.org>, <dmaengine@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dan.j.williams@intel.com>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] dmaengine: bindings/edma: dma-channel-mask to array
Date: Wed, 6 Nov 2019 09:46:12 +0200 [thread overview]
Message-ID: <1dbaa288-06b6-7ba4-e1ee-d76202c6be8b@ti.com> (raw)
In-Reply-To: <20191105170101.GE952516@vkoul-mobl>
On 05/11/2019 19.01, Vinod Koul wrote:
> On 25-10-19, 10:30, Peter Ujfalusi wrote:
>> Hi,
>>
>> Changes since v4:
>> - Rebased on next to make it apply cleanly
>> - Added Reviewed-by from Rob for the DT documentation patches
>>
>> Changes since v3:
>> - Update the dma-common.yaml and edma binding documentation according to Rob's
>> suggestion
>>
>> Changes since v2:
>> - Fix dma-common.yaml documentation patch and extend the description of the
>> dma-channel-mask array
>> - The edma documentation now includes information on the dma-channel-mask array
>> size for EDMAs with 32 or 64 channels
>>
>> Changes since v1:
>> - Extend the common dma-channel-mask to uint32-array to be usable for
>> controllers with more than 32 channels
>> - Use the dma-channel-mask instead custom property for available channels for
>> EDMA.
>>
>> The original patch was part of the EDMA multicore usage series.
>>
>> EDMAs can have 32 or 64 channels depending on the SoC, the dma-channel-mask
>> needs to be an array to be usable for the driver.
>
> And now I saw this and have applied these and dropped the ones I fixed
> up manually!
OK, thank you for picking these up! - Péter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
prev parent reply other threads:[~2019-11-06 7:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 7:30 [PATCH v5 0/3] dmaengine: bindings/edma: dma-channel-mask to array Peter Ujfalusi
2019-10-25 7:30 ` [PATCH v5 1/3] dt-bindings: dmaengine: dma-common: Change dma-channel-mask to uint32-array Peter Ujfalusi
2019-10-25 7:30 ` [PATCH v5 2/3] dt-bindings: dma: ti-edma: Document dma-channel-mask for EDMA Peter Ujfalusi
2019-10-25 7:30 ` [PATCH v5 3/3] dmaengine: ti: edma: Add support for handling reserved channels Peter Ujfalusi
2019-11-05 17:01 ` [PATCH v5 0/3] dmaengine: bindings/edma: dma-channel-mask to array Vinod Koul
2019-11-06 7:46 ` Peter Ujfalusi [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=1dbaa288-06b6-7ba4-e1ee-d76202c6be8b@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).