From: Hans Zhang <18255117159@163.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, robh@kernel.org,
bhelgaas@google.com, jingoohan1@gmail.com,
thomas.richard@bootlin.com, linux-pci@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v6 3/5] PCI: cadence: Use common PCI host bridge APIs for finding the capabilities
Date: Tue, 25 Mar 2025 23:37:25 +0800 [thread overview]
Message-ID: <9118fcc0-e5a5-40f2-be4b-7e06b4b20601@163.com> (raw)
In-Reply-To: <ddabf340-a00f-75b1-2b6b-d9ab550a984f@linux.intel.com>
On 2025/3/25 23:18, Ilpo Järvinen wrote:>>
>> Hi Ilpo,
>>
>> Another question comes to mind:
>> If working in EP mode, devm_pci_alloc_host_bridge will not be executed and
>> there will be no struct pci_host_bridge.
>>
>> Don't know if you have anything to add?
>
> Hi Hans,
>
> No, I don't have further ideas at this point, sorry. It seems it isn't
> realistic without something more substantial that currently isn't there.
>
> This lack of way to have a generic way to read the config before the main
> struct are instanciated by the PCI core seems to be the limitation that
> hinders sharing code between controller drivers and it would have been
> nice to address it.
>
> But please still make the capability list parsing code common, it should
> be relatively straightforward using a macro which can take different read
> functions similar to read_poll_timeout. That will avoid at least some
> amount of code duplication.
>
> Thanks for trying to come up with a solution (or thinking enough to say
> it doesn't work)!
>
Hi Ilpo,
It's okay. It's what I'm supposed to do. Thank you very much for your
discussion with me. I'll try a macro definition like read_poll_timeout.
Will share the revised patches soon for your feedback.
Best regards,
Hans
next prev parent reply other threads:[~2025-03-25 15:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 16:48 [v6 0/5] Introduce generic capability search functions Hans Zhang
2025-03-23 16:48 ` [v6 1/5] PCI: " Hans Zhang
2025-03-24 13:28 ` Ilpo Järvinen
2025-03-24 14:39 ` Hans Zhang
2025-03-24 14:52 ` Ilpo Järvinen
2025-03-25 2:58 ` Hans Zhang
2025-03-27 16:57 ` Manivannan Sadhasivam
2025-03-28 9:41 ` Hans Zhang
2025-03-27 16:58 ` Manivannan Sadhasivam
2025-03-28 9:42 ` Hans Zhang
2025-03-23 16:48 ` [v6 2/5] PCI: dwc: Use common PCI host bridge APIs for finding the capabilities Hans Zhang
2025-03-23 16:48 ` [v6 3/5] PCI: cadence: " Hans Zhang
2025-03-23 18:33 ` kernel test robot
2025-03-24 1:07 ` Hans Zhang
2025-03-23 19:26 ` kernel test robot
2025-03-24 1:08 ` Hans Zhang
2025-03-24 13:44 ` Ilpo Järvinen
2025-03-24 14:29 ` Hans Zhang
2025-03-24 15:02 ` Ilpo Järvinen
2025-03-25 2:59 ` Hans Zhang
2025-03-25 11:15 ` Ilpo Järvinen
2025-03-25 12:16 ` Hans Zhang
2025-03-25 14:47 ` Hans Zhang
2025-03-25 15:18 ` Ilpo Järvinen
2025-03-25 15:37 ` Hans Zhang [this message]
2025-03-28 10:33 ` Hans Zhang
2025-03-28 11:42 ` Ilpo Järvinen
2025-03-29 16:03 ` Hans Zhang
2025-03-31 16:39 ` Ilpo Järvinen
2025-04-01 13:20 ` Hans Zhang
2025-03-23 16:48 ` [v6 4/5] PCI: cadence: Use cdns_pcie_find_*capability to avoid hardcode Hans Zhang
2025-03-23 16:48 ` [v6 5/5] MAINTAINERS: Add entry for PCI host controller helpers Hans Zhang
2025-03-27 17:01 ` Manivannan Sadhasivam
2025-03-28 10:36 ` Hans Zhang
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=9118fcc0-e5a5-40f2-be4b-7e06b4b20601@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=thomas.richard@bootlin.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