linux-kernel - Re: [PATCH RESEND] dmaengine: ti-dma-crossbar: Correct am335x/am43xx mux value type

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, 8 Nov 2017 19:52:33 +0530
From:   Vinod Koul <vinod.koul@...el.com>
To:     Peter Ujfalusi <peter.ujfalusi@...com>
Cc:     dan.j.williams@...el.com, dmaengine@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org
Subject: Re: [PATCH RESEND] dmaengine: ti-dma-crossbar: Correct am335x/am43xx
 mux value type

On Wed, Nov 08, 2017 at 12:02:25PM +0200, Peter Ujfalusi wrote:
> The used 0x1f mask is only valid for am335x family of SoC, different family
> using this type of crossbar might have different number of electable
> events. In case of am43xx family 0x3f mask should have been used for
> example.
> Instead of trying to handle each family's mask, just use u8 type to store
> the mux value since the event offsets are aligned to byte offset.
> 
> Fixes: 42dbdcc6bf965 ("dmaengine: ti-dma-crossbar: Add support for crossbar on AM33xx/AM43xx")
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@...com>
> ---
> Vinod,
> 
> this patch somehow got missed, I have sent it in May:
> https://patchwork.kernel.org/patch/9736747/

not sure how, but applied now

-- 
~Vinod