From: "Martin Tůma" <tumic@gpxsee.org>
To: sonal.santan@amd.com
Cc: dmaengine@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
martin.tuma@digiteqautomotive.com, mchehab@kernel.org,
michal.simek@xilinx.com, tumic@gpxsee.org, vkoul@kernel.org
Subject: Re: [PATCH v2 0/3] Digiteq Automotive MGB4 driver
Date: Wed, 21 Sep 2022 11:44:49 +0200 [thread overview]
Message-ID: <285cddef-bc3e-dd86-46e0-5f4de6ebcd32@gpxsee.org> (raw)
In-Reply-To: <40c6af79-9288-7a67-e41b-30c288dbe1ff@amd.com>
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.
prev parent reply other threads:[~2022-09-21 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 18:55 [PATCH v2 0/3] Digiteq Automotive MGB4 driver tumic
2022-09-19 18:55 ` [PATCH v2 1/3] Added platform module alias for the xiic I2C driver tumic
2022-09-20 14:30 ` Michal Simek
2022-09-19 18:55 ` [PATCH v2 2/3] Added Xilinx XDMA IP core driver tumic
2022-09-20 2:12 ` kernel test robot
2022-09-21 6:24 ` Lizhi Hou
2022-09-21 9:25 ` Martin Tůma
2022-09-21 15:15 ` Lizhi Hou
2022-09-21 15:35 ` Martin Tůma
2022-09-19 18:55 ` [PATCH v2 3/3] Added Digiteq Automotive MGB4 driver tumic
2022-10-03 5:19 ` kernel test robot
2022-09-21 5:32 ` [PATCH v2 0/3] " Sonal Santan
2022-09-21 9:44 ` Martin Tůma [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=285cddef-bc3e-dd86-46e0-5f4de6ebcd32@gpxsee.org \
--to=tumic@gpxsee.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martin.tuma@digiteqautomotive.com \
--cc=mchehab@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=sonal.santan@amd.com \
--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).