linux-kernel - Re: [PATCH v4 0/3] dmaengine: bindings/edma: dma-channel-mask to array

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 6 Nov 2019 09:45:47 +0200
From:   Peter Ujfalusi <peter.ujfalusi@...com>
To:     Vinod Koul <vkoul@...nel.org>
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 v4 0/3] dmaengine: bindings/edma: dma-channel-mask to
 array

Hi Vinod,

On 05/11/2019 18.51, Vinod Koul wrote:
> On 30-09-19, 14:40, Peter Ujfalusi wrote:
>> Hi,
>>
>> 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.
>>
>> Rob: I'm not sure if I got the dma-common.yaml update correctly...
>>
>> 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.
> 
> Applied, thanks
> 
> There was a conflict on patch3, I have reolved it, please check.

Looks good, I wonder what caused the conflict. The patch looks identical
in your vinod/next and in my linux-next-wip.

Oh, this is v4 and you have picked the v5. That explains.

Thank you,
- Péter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki