From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>, "Lukas Wunner" <lukas@wunner.de>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
quic_krichai@quicinc.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3] PCI: Add D3 support for PCI bridges in DT based platforms
Date: Tue, 27 Feb 2024 22:38:40 +0530 [thread overview]
Message-ID: <20240227170840.GR2587@thinkpad> (raw)
In-Reply-To: <20240227162535.GA239073@bhelgaas>
On Tue, Feb 27, 2024 at 10:25:35AM -0600, Bjorn Helgaas wrote:
[...]
> > Ok, I got the issue. TBH, I added the device tree property based on
> > the existing quirks for the ACPI devices. But none of the DT based
> > platforms I'm aware of (even the legacy Qcom MSM8996 chipset
> > released in early 2016) doesn't have any issue with D3hot. But I'm
> > just nervous to assume it is the case for all the DT based platforms
> > in the wild.
> >
> > But to proceed further, what is your preference? Should we ammend
> > the DT property to make it explicit that the propery only focuses on
> > the D3hot capability of the bridge and it works as per the spec
> > (PMCSR) or bite the bullet and enable D3hot for all the non-ACPI
> > platforms?
> >
> > We can add quirks for the bridges later on if we happen to receive
> > any bug report.
>
> I would assume all devices support D3hot via PMCSR per spec. We can
> add quirks if we discover something that doesn't.
>
When you say "all devices", are you referring to bridges in DT platforms or the
bridges across all platforms?
- Mani
> If we add annotations that "this device works correctly", we're
> digging a hole for ourselves because it's impossible to remove those
> annotations and they complicate all future maintenance.
>
> Bjorn
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-02-27 17:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 11:46 [PATCH v3] PCI: Add D3 support for PCI bridges in DT based platforms Manivannan Sadhasivam
2024-02-14 12:19 ` Lukas Wunner
2024-02-20 22:02 ` Bjorn Helgaas
2024-02-21 5:19 ` Manivannan Sadhasivam
2024-02-21 18:20 ` Bjorn Helgaas
2024-02-22 4:06 ` Manivannan Sadhasivam
2024-02-26 23:39 ` Bjorn Helgaas
2024-02-27 7:30 ` Manivannan Sadhasivam
2024-02-27 16:25 ` Bjorn Helgaas
2024-02-27 17:08 ` Manivannan Sadhasivam [this message]
2024-02-27 17:37 ` Bjorn Helgaas
2024-02-27 18:40 ` Manivannan Sadhasivam
2024-02-27 22:54 ` Bjorn Helgaas
2024-02-22 9:40 ` Lukas Wunner
2024-02-26 23:17 ` Bjorn Helgaas
2024-03-05 16:25 ` Manivannan Sadhasivam
2024-03-05 17:51 ` Bjorn Helgaas
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=20240227170840.GR2587@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=quic_krichai@quicinc.com \
--cc=robh@kernel.org \
/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.