[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191105170101.GE952516@vkoul-mobl>
Date: Tue, 5 Nov 2019 22:31:01 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Peter Ujfalusi <peter.ujfalusi@...com>
Cc: robh+dt@...nel.org, dmaengine@...r.kernel.org,
linux-kernel@...r.kernel.org, dan.j.williams@...el.com,
devicetree@...r.kernel.org
Subject: Re: [PATCH v5 0/3] dmaengine: bindings/edma: dma-channel-mask to
array
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!
--
~Vinod
Powered by blists - more mailing lists