mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lizhi Hou <lizhi.hou@amd.com>
To: "Martin Tůma" <tumic@gpxsee.org>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: <vkoul@kernel.org>, <dmaengine@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <max.zhen@amd.com>,
	<sonal.santan@amd.com>, <larry.liu@amd.com>, <brian.xu@amd.com>
Subject: Re: [RESEND PATCH V12 XDMA 1/2] dmaengine: xilinx: xdma: Add xilinx xdma driver
Date: Tue, 21 Feb 2023 19:51:56 -0800	[thread overview]
Message-ID: <6da2e72c-661c-e4de-f563-e06f045414ae@amd.com> (raw)
In-Reply-To: <aeb43671-57fd-654a-8e8d-d14ebb7f4083@gpxsee.org>


On 2/21/23 13:46, Martin Tůma wrote:
> On 21. 02. 23 22:06, Geert Uytterhoeven wrote:
>> Hi Martin,
>>
>> On Tue, Feb 21, 2023 at 9:45 PM Martin Tůma <tumic@gpxsee.org> wrote:
>>> On 21. 02. 23 14:25, Geert Uytterhoeven wrote:
>>>> No platform dependencies at all, while this is a platform driver that
>>>> relies on some other not-yet-existing driver creating an "xdma"
>>>> platform device?
>>>
>>> There is at least one "already-existing" driver based on this driver
>>> that is waiting in the v4l2 queue for xdma - our MGB4 driver:
>>> https://patchwork.kernel.org/project/linux-media/patch/20230207150119.5542-2-tumic@gpxsee.org/ 
>>>
>>
>> Thanks for the link!
>>
>> As VIDEO_MGB4 selects XILINX_XDMA, perhaps XILINX_XDMA
>> can be made invisible, unless compile-testing?
>>
>>      config XILINX_XDMA
>>          tristate "Xilinx DMA/Bridge Subsystem DMA Engine" if 
>> COMPILE_TEST
>>
>> Gr{oetje,eeting}s,
>>
>>                          Geert
>>
>
> Hi,
> I think that the XDMA driver will always be used by a superior PCIe 
> card driver like in our case (mgb4) and using it separately makes no 
> sense/is not possible, so disabling it until some of the superior 
> drivers selects it makes sense for me. But what about out-of-the-tree 
> modules based on xdma? Making the module "invisible" will make compile 
> them much harder I guess? And there will be proprietary drivers based 
> on xdma, see Xilinx XRT: 
> https://github.com/houlz0507/XRT-1/tree/xdma_v4_usage
>
> The xdma authors from Xilinx will definitely give you a more 
> authoritative answer. I'm just a "random" user of the xdma module. 
> Originally our mgb4 driver was based on our own xdma sub-driver (in 
> turn based on some old "test" driver from Xilinx) which I was glad we 
> could abandon when this xdma driver has appeared. I helped the xdma 
> module to become usable for PCIe cards like our v4l2 grabber, but the 
> original intents of the xdma driver are unknown to me. If it is XRT, 
> than Xilinx will probably like the module to stay visible.
>
> M.
>
There are PCIe devices which use the XDMA IP and would use this xdma 
driver. Out of tree drivers for Xilinx/AMD Alveo devices can switch to 
this in kernel xdma driver.


Thanks,

Lizhi


  reply	other threads:[~2023-02-22  3:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 19:05 [RESEND PATCH V12 XDMA 0/2] xilinx XDMA driver Lizhi Hou
2023-02-09 19:05 ` [RESEND PATCH V12 XDMA 1/2] dmaengine: xilinx: xdma: Add xilinx xdma driver Lizhi Hou
2023-02-21 13:25   ` Geert Uytterhoeven
2023-02-21 20:46     ` Martin Tůma
2023-02-21 21:06       ` Geert Uytterhoeven
2023-02-21 21:46         ` Martin Tůma
2023-02-22  3:51           ` Lizhi Hou [this message]
2023-02-22  3:46     ` Lizhi Hou
2023-02-09 19:05 ` [RESEND PATCH V12 XDMA 2/2] dmaengine: xilinx: xdma: Add user logic interrupt support Lizhi Hou
  -- strict thread matches above, loose matches on Subject: below --
2023-02-03 18:13 [RESEND PATCH V12 XDMA 0/2] xilinx XDMA driver Lizhi Hou
2023-02-03 18:13 ` [RESEND PATCH V12 XDMA 1/2] dmaengine: xilinx: xdma: Add xilinx xdma driver Lizhi Hou
2023-01-26 19:12 [RESEND PATCH V12 XDMA 0/2] xilinx XDMA driver Lizhi Hou
2023-01-26 19:12 ` [RESEND PATCH V12 XDMA 1/2] dmaengine: xilinx: xdma: Add xilinx xdma driver Lizhi Hou

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=6da2e72c-661c-e4de-f563-e06f045414ae@amd.com \
    --to=lizhi.hou@amd.com \
    --cc=brian.xu@amd.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=larry.liu@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max.zhen@amd.com \
    --cc=sonal.santan@amd.com \
    --cc=tumic@gpxsee.org \
    --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

all inboxes | Powered by JetHome®