From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"heiko@sntech.de" <heiko@sntech.de>,
"hayashi.kunihiko@socionext.com" <hayashi.kunihiko@socionext.com>,
"tiwai@suse.de" <tiwai@suse.de>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"spujar@nvidia.com" <spujar@nvidia.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"kthota@nvidia.com" <kthota@nvidia.com>,
"mperttunen@nvidia.com" <mperttunen@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"stefan.wahren@i2se.com" <stefan.wahren@i2se.com>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"krzk@kernel.org" <krzk@kernel.org>,
"kishon@ti.com" <kishon@ti.com>,
"maxime.ripard@bootlin.com" <maxime.ripard@bootlin.com>,
"jagan@amarulasolutions.com" <jagan@amarulasolutions.com>,
linux-pc
Subject: Re: [PATCH 01/10] PCI: save pci_bus pointer in pcie_port structure
Date: Thu, 28 Mar 2019 07:18:03 +0000 [thread overview]
Message-ID: <20190328151008.5e563e3a@xhacker.debian> (raw)
In-Reply-To: <1553613207-3988-2-git-send-email-vidyas@nvidia.com>
On Tue, 26 Mar 2019 20:43:18 +0530Vidya Sagar wrote:
>
> save pci_bus pointer created by PCIe sub-system's
> pci_scan_root_bus_bridge() to be used by host controller drivers for post
> processing. Tegra host controller driver needs it for the following
> reasons
> - to derive pci_host_bridge structure from pci_bus which is used to
> configure iATU's outbound regions for different windows accesses
> - to traverse and configure downstream hierarchy. One such case is,
> configuring all immediate downstream devices to D0 state before transiting
> link to L2 state. Saving pci_bus pointer seems the best method compared to
> deriving it by other means.
hmm, I submitted similar patch for another purpose last month,
https://patchwork.kernel.org/patch/10830029/
then v3 weeks ago
https://lkml.org/lkml/2019/3/18/375
And get Acks from Gustavo. But it seems that it isn't merged to dwc next
branch in Lorenzo's tree
Maybe Lorenzo have some idea of handling this case.
Thanks
next prev parent reply other threads:[~2019-03-28 7:18 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 15:13 [PATCH 00/10] Add Tegra194 PCIe support Vidya Sagar
2019-03-26 15:13 ` [PATCH 01/10] PCI: save pci_bus pointer in pcie_port structure Vidya Sagar
2019-03-28 7:18 ` Jisheng Zhang [this message]
2019-03-28 7:38 ` Vidya Sagar
2019-03-26 15:13 ` [PATCH 02/10] PCI: perform dbi regs write lock towards the end Vidya Sagar
2019-03-26 15:13 ` [PATCH 03/10] PCI: dwc: Move config space capability search API Vidya Sagar
2019-03-28 12:33 ` Thierry Reding
2019-04-01 11:46 ` Vidya Sagar
2019-03-26 15:13 ` [PATCH 04/10] PCI: Add #defines for PCIe spec r4.0 features Vidya Sagar
2019-03-26 15:13 ` [PATCH 05/10] dt-bindings: PCI: tegra: Add device tree support for T194 Vidya Sagar
2019-03-27 10:10 ` Jon Hunter
2019-03-27 10:53 ` Vidya Sagar
2019-03-28 13:15 ` Thierry Reding
2019-04-01 10:01 ` Vidya Sagar
2019-04-01 15:07 ` Thierry Reding
2019-04-02 11:41 ` Vidya Sagar
2019-04-02 14:35 ` Thierry Reding
2019-04-03 6:22 ` Vidya Sagar
2019-04-02 19:21 ` Bjorn Helgaas
2019-03-31 6:42 ` Rob Herring
2019-04-01 11:18 ` Vidya Sagar
2019-04-01 14:31 ` Thierry Reding
2019-04-02 9:16 ` Vidya Sagar
2019-04-02 14:20 ` Thierry Reding
2019-04-03 5:29 ` Vidya Sagar
2019-04-08 18:29 ` Trent Piepho
2019-04-09 11:07 ` Vidya Sagar
2019-03-26 15:13 ` [PATCH 06/10] arm64: tegra: Add P2U and PCIe controller nodes to Tegra194 DT Vidya Sagar
2019-03-28 16:59 ` Thierry Reding
2019-04-01 12:37 ` Vidya Sagar
2019-03-26 15:13 ` [PATCH 07/10] arm64: tegra: Enable PCIe slots in P2972-0000 board Vidya Sagar
2019-03-26 15:13 ` [PATCH 08/10] phy: tegra: Add PCIe PIPE2UPHY support Vidya Sagar
2019-04-03 8:05 ` Kishon Vijay Abraham I
2019-04-03 10:45 ` Vidya Sagar
2019-03-26 15:13 ` [PATCH 09/10] PCI: tegra: Add Tegra194 PCIe support Vidya Sagar
2019-03-27 10:07 ` Jon Hunter
2019-03-29 20:52 ` Bjorn Helgaas
2019-04-02 7:17 ` Vidya Sagar
2019-04-02 14:14 ` Thierry Reding
2019-04-03 9:15 ` Vidya Sagar
2019-04-02 18:31 ` Bjorn Helgaas
2019-04-03 9:43 ` Vidya Sagar
2019-04-03 17:36 ` Bjorn Helgaas
2019-04-04 19:53 ` Vidya Sagar
2019-04-05 18:58 ` Bjorn Helgaas
2019-04-09 11:30 ` Vidya Sagar
2019-04-09 13:26 ` Bjorn Helgaas
2019-04-10 6:10 ` Vidya Sagar
2019-04-10 8:14 ` Liviu Dudau
2019-04-10 9:53 ` Vidya Sagar
2019-04-10 11:35 ` Liviu Dudau
2019-03-26 15:13 ` [PATCH 10/10] arm64: Add Tegra194 PCIe driver to defconfig Vidya Sagar
2019-03-27 10:08 ` Jon Hunter
2019-03-27 10:12 ` Vidya Sagar
2019-03-27 12:26 ` Jon Hunter
2019-03-28 8:19 ` Jisheng Zhang
2019-04-01 12:45 ` Vidya Sagar
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=20190328151008.5e563e3a@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--cc=catalin.marinas@arm.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=kthota@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mperttunen@nvidia.com \
--cc=spujar@nvidia.com \
--cc=stefan.wahren@i2se.com \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.de \
--cc=vidyas@nvidia.com \
--cc=will.deacon@arm.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).