All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Hans Zhang <18255117159@163.com>
Cc: Aksh Garg <a-garg7@ti.com>, Bjorn Helgaas <bhelgaas@google.com>,
	Siddharth Vadapalli <s-vadapalli@ti.com>,
	sashiko@lists.linux.dev, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: cadence: Use cdns_pcie_find_capability() to get PCIe Cap offset in host driver
Date: Thu, 7 May 2026 10:32:31 -0500	[thread overview]
Message-ID: <20260507153231.GA971257@bhelgaas> (raw)
In-Reply-To: <3280415c-3c38-4b69-b2a5-6b97d0d24e54@163.com>

On Thu, May 07, 2026 at 11:21:39PM +0800, Hans Zhang wrote:
> On 5/7/26 20:31, Aksh Garg wrote:
> ...

> > I have tested this on J7200 and J721E SoCs, which uses pci-j721e.c
> > driver for their PCIe controllers. The patch alone fails to find the
> > capabilities using cdns_pcie_find_capability() for Root Port.
> > 
> > With the "is_hpa" flag patch, and the patch "PCI: cadence: Use
> > cdns_pcie_find_capability() to get PCIe Cap offset in host driver" along
> > with the diff suggested above:
> 
> Thank you very much for your test. We need to wait for Bjorn's approval.

Just post a revised series incorporating the fix.

Thanks for the testing, Aksh!

Bjorn

      reply	other threads:[~2026-05-07 15:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 16:19 [PATCH] PCI: cadence: Use cdns_pcie_find_capability() to get PCIe Cap offset in host driver Hans Zhang
2026-05-03 16:52 ` sashiko-bot
2026-05-04  8:22   ` Hans Zhang
2026-05-05 21:23     ` Bjorn Helgaas
2026-05-06 16:04       ` Hans Zhang
2026-05-06 17:12         ` Bjorn Helgaas
2026-05-07  3:31           ` Hans Zhang
2026-05-07  3:48             ` Hans Zhang
2026-05-07 12:31               ` Aksh Garg
2026-05-07 15:21                 ` Hans Zhang
2026-05-07 15:32                   ` Bjorn Helgaas [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=20260507153231.GA971257@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=18255117159@163.com \
    --cc=a-garg7@ti.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=sashiko@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.