linux-kernel - Re: [PATCH v2 0/3] Digiteq Automotive MGB4 driver

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 21 Sep 2022 11:44:49 +0200
From:   Martin Tůma <tumic@...see.org>
To:     sonal.santan@....com
Cc:     dmaengine@...r.kernel.org, linux-i2c@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
        martin.tuma@...iteqautomotive.com, mchehab@...nel.org,
        michal.simek@...inx.com, tumic@...see.org, vkoul@...nel.org
Subject: Re: [PATCH v2 0/3] Digiteq Automotive MGB4 driver

Hi,

 > Xilinx/AMD is working on upstreaming the XDMA driver into Linux
 > dmaengine subsystem for use by all users of XDMA IP. You can find the 
 > V3
 > patch set here:
 >
 > 
https://lore.kernel.org/dmaengine/1663631039-49732-1-git-send-email-lizhi.hou@amd.com/T/#t

That's good news. If this would happen before I have spend two weeks 
converting the original Xilinx "driver" to something with at least a 
theoretical chance to be included into the kernel, it would be even 
better... ;-)

 > Will appreciate your review of that patch set and hopefully MGB4 driver
 > can be rebased on top it?

As I already replied to Lizhi Hou, this new XDMA driver is at the moment 
unusable for most XDMA-based HW as it does not handle the user IRQs 
logic and as it also takes up the user IRQs register memory space, it 
even actively hinders other drivers to at least handle the IRQs themselves.

M.