From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: PCIe EPF
Date: Thu, 2 Apr 2020 18:44:37 +0100 [thread overview]
Message-ID: <CA+V-a8uZX+D1peigQuoTgmJq6KzZhUN_J7DjA_jCw=Re=titkw@mail.gmail.com> (raw)
In-Reply-To: <TYAPR01MB45442E975AEA3EDD22A3CD3BD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com>
Hi Shimoda-san,
On Thu, Apr 2, 2020 at 5:58 AM Yoshihiro Shimoda
<yoshihiro.shimoda.uh@renesas.com> wrote:
>
> Hi Prabhakar-san,
>
> > From: Yoshihiro Shimoda, Sent: Thursday, April 2, 2020 10:23 AM
> <snip>
> > By the way, according to previous your report, you are using pci/next branch
> > and the branch is based on v5.6-rc1. There is no evidence though,
> > I'd like to use next-20200401 tag from linux-next repo to use v5.6 based kernel
> > whether the strange issue happens on the latest v5.6 kernel code or not.
> > Note that I confirmed the next-20200401 tag has a commit d293237739414d
> > ("misc: pci_endpoint_test: Use streaming DMA APIs for buffer allocation").
>
> I'm afraid but I'd like to recall this because next-20200401 seems unstable on
> R-Car Gen3 environment (a lot of WARING happens). So, perhaps using linux mainline
> v5.6 + merging pci/next branch is better.
>
Taking your advice I rebased my patches on Geert's tree [1] (master
branch) and choose
M3N as my root device, and with rigorous testing I can confirm
read/write/copy work
without any issues. Using the same branch with G2N as root device still failed.
Since this is a Root device issue and not ep I am posting v6 and
swiotlb can be handled
separately for G2x platforms.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git/
Cheers,
--Prabhakar
> Best regards,
> Yoshihiro Shimoda
>
> > Best regards,
> > Yoshihiro Shimoda
>
prev parent reply other threads:[~2020-04-02 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 11:37 PCIe EPF Lad, Prabhakar
2020-03-20 5:28 ` Kishon Vijay Abraham I
2020-03-21 22:49 ` Lad, Prabhakar
2020-03-24 1:58 ` Kishon Vijay Abraham I
2020-03-24 14:41 ` Lad, Prabhakar
2020-03-28 18:44 ` Lad, Prabhakar
2020-03-29 14:04 ` Lad, Prabhakar
2020-03-30 11:59 ` Kishon Vijay Abraham I
2020-03-30 13:09 ` Lad, Prabhakar
2020-03-30 13:20 ` Kishon Vijay Abraham I
2020-03-30 13:46 ` Lad, Prabhakar
2020-03-31 7:10 ` Yoshihiro Shimoda
2020-03-31 17:25 ` Lad, Prabhakar
2020-04-01 1:25 ` Yoshihiro Shimoda
2020-04-01 8:00 ` Lad, Prabhakar
2020-04-01 8:50 ` Yoshihiro Shimoda
2020-04-01 9:24 ` Lad, Prabhakar
2020-04-02 1:22 ` Yoshihiro Shimoda
2020-04-02 4:58 ` Yoshihiro Shimoda
2020-04-02 17:44 ` Lad, Prabhakar [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='CA+V-a8uZX+D1peigQuoTgmJq6KzZhUN_J7DjA_jCw=Re=titkw@mail.gmail.com' \
--to=prabhakar.csengg@gmail.com \
--cc=Chris.Paterson2@renesas.com \
--cc=kishon@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=yoshihiro.shimoda.uh@renesas.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).