From: Pavel Pisa <pisa@fel.cvut.cz>
To: Jason Gunthorpe <jgg@nvidia.com>,
Xu Yilun <yilun.xu@linux.intel.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-fpga@vger.kernel.org, Michal Simek <michal.simek@amd.com>,
Xu Yilun <yilun.xu@intel.com>,
Pavel Hronek <hronepa1@fel.cvut.cz>,
Jiri Novak <jnovak@fel.cvut.cz>,
Ondrej Ille <ondrej.ille@gmail.com>
Subject: Re: AMD/Xilinx Zynq FPGA manager stopped to work after 6.16.0-g283564a43383
Date: Tue, 5 Aug 2025 21:39:59 +0200 [thread overview]
Message-ID: <202508052140.00023.pisa@fel.cvut.cz> (raw)
In-Reply-To: <20250805185235.GP184255@nvidia.com>
Hello all
On Tuesday 05 of August 2025 20:52:35 Jason Gunthorpe wrote:
> On Wed, Aug 06, 2025 at 01:12:46AM +0800, Xu Yilun wrote:
> > @@ -405,12 +405,12 @@ static int zynq_fpga_ops_write(struct fpga_manager
> > *mgr, struct sg_table *sgt) }
> > }
> >
> > - priv->dma_nelms =
> > - dma_map_sgtable(mgr->dev.parent, sgt, DMA_TO_DEVICE, 0);
> > - if (priv->dma_nelms == 0) {
> > + err = dma_map_sgtable(mgr->dev.parent, sgt, DMA_TO_DEVICE, 0);
> > + if (err) {
> > dev_err(&mgr->dev, "Unable to DMA map (TO_DEVICE)\n");
> > - return -ENOMEM;
> > + return err;
> > }
> > + priv->dma_nelms = sgt->nents;
>
> That looks pretty good, Marek is certainly right the original had a
> bug.
>
> Jason
Thanks for the fast correction proposal. I have tested the change
at our kernel build, actual mainline version form midnight
rebuild with patch now
Linux mzapo 6.16.0+ #2 SMP Tue Aug 5 20:59:36 CEST 2025 armv7l GNU/Linux
and it works correctly, DTBOCFG and FPGA manager is able to load
CTU CAN FD IP core design and then driver is loaded and its instances
are setup according to the device tree overlay and driver detects
CAN controllers implemented in FPGA. I have not run whole CAN test
sequence but I do not expect problems there. You can add my
Reported-by: Pavel Pisa <pisa@fel.cvut.cz>
Tested-by: Pavel Pisa <pisa@fel.cvut.cz>
Do you have some idea how fast can the change propagate
into mainline? I would setup automatic patching with
the fix if the testing setup is broken for some longer time.
If the fix can get in mainline in days or week then I would
spent time on that.
Best wishes,
Pavel
Pavel Pisa
phone: +420 603531357
e-mail: pisa@cmp.felk.cvut.cz
Department of Control Engineering FEE CVUT
Karlovo namesti 13, 121 35, Prague 2
university: http://control.fel.cvut.cz/
personal: http://cmp.felk.cvut.cz/~pisa
social: https://social.kernel.org/ppisa
projects: https://www.openhub.net/accounts/ppisa
CAN related:http://canbus.pages.fel.cvut.cz/
RISC-V education: https://comparch.edu.cvut.cz/
Open Technologies Research Education and Exchange Services
https://gitlab.fel.cvut.cz/otrees/org/-/wikis/home
next prev parent reply other threads:[~2025-08-05 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250804134826eucas1p1350956e17ae463332a69eaa67dc2f8d7@eucas1p1.samsung.com>
2025-08-04 13:48 ` AMD/Xilinx Zynq FPGA manager stopped to work after 6.16.0-g283564a43383 Pavel Pisa
2025-08-05 10:01 ` Marek Szyprowski
2025-08-05 17:12 ` Xu Yilun
2025-08-05 18:52 ` Jason Gunthorpe
2025-08-05 19:39 ` Pavel Pisa [this message]
2025-08-06 7:11 ` Xu Yilun
2025-08-06 5:22 ` Marek Szyprowski
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=202508052140.00023.pisa@fel.cvut.cz \
--to=pisa@fel.cvut.cz \
--cc=hronepa1@fel.cvut.cz \
--cc=jgg@nvidia.com \
--cc=jnovak@fel.cvut.cz \
--cc=linux-fpga@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=michal.simek@amd.com \
--cc=ondrej.ille@gmail.com \
--cc=yilun.xu@intel.com \
--cc=yilun.xu@linux.intel.com \
/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).