devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "Abel Vesa" <abel.vesa@linaro.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: PCI: qcom: Fix register maps items and add 3.3V supply
Date: Wed, 5 Jun 2024 07:50:33 -0600	[thread overview]
Message-ID: <20240605135033.GA2468218-robh@kernel.org> (raw)
In-Reply-To: <20240605054928.GB2417@thinkpad>

On Wed, Jun 05, 2024 at 11:19:28AM +0530, Manivannan Sadhasivam wrote:
> On Tue, Jun 04, 2024 at 05:58:06PM -0600, Rob Herring wrote:
> > On Tue, Jun 04, 2024 at 07:05:12PM +0300, Abel Vesa wrote:
> > > All PCIe controllers found on X1E80100 have MHI register region and
> > > VDDPE supplies. Add them to the schema as well.
> > > 
> > > Fixes: 692eadd51698 ("dt-bindings: PCI: qcom: Document the X1E80100 PCIe Controller")
> > > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> > > ---
> > > This patchset fixes the following warning:
> > > https://lore.kernel.org/all/171751454535.785265.18156799252281879515.robh@kernel.org/
> > > 
> > > Also fixes a MHI reg region warning that will be triggered by the following patch:
> > > https://lore.kernel.org/all/20240604-x1e80100-dts-fixes-pcie6a-v2-1-0b4d8c6256e5@linaro.org/
> > > ---
> > >  Documentation/devicetree/bindings/pci/qcom,pcie-x1e80100.yaml | 6 ++++--
> > >  1 file changed, 4 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie-x1e80100.yaml b/Documentation/devicetree/bindings/pci/qcom,pcie-x1e80100.yaml
> > > index 1074310a8e7a..7ceba32c4cf9 100644
> > > --- a/Documentation/devicetree/bindings/pci/qcom,pcie-x1e80100.yaml
> > > +++ b/Documentation/devicetree/bindings/pci/qcom,pcie-x1e80100.yaml
> > > @@ -19,11 +19,10 @@ properties:
> > >      const: qcom,pcie-x1e80100
> > >  
> > >    reg:
> > > -    minItems: 5
> > > +    minItems: 6
> > >      maxItems: 6
> > >  
> > >    reg-names:
> > > -    minItems: 5
> > >      items:
> > >        - const: parf # Qualcomm specific registers
> > >        - const: dbi # DesignWare PCIe registers
> > > @@ -71,6 +70,9 @@ properties:
> > >        - const: pci # PCIe core reset
> > >        - const: link_down # PCIe link down reset
> > >  
> > > +  vddpe-3v3-supply:
> > > +    description: A phandle to the PCIe endpoint power supply
> > 
> > TBC, this is a rail on the host side provided to a card? If so, we have 
> > standard properties for standard PCI voltage rails.
> 
> There is a 'vpcie3v3-supply' property and it should satisfy the requirement. But
> 'vddpe-3v3-supply' is already used on multiple Qcom SoCs. So changing the name
> in dts warrants the driver to support both supplies for backwards compatibility,
> but that should be fine.

Ideally, we would have a 'enable slot' or 'power on slot' function that 
turns on all the standard slot supplies and wiggles PERST# (and 
perhaps link state management) all following the timing defined in the 
PCI spec. Then the host drivers wouldn't have to do anything other than 
perhaps opt-in to use that.

> > It is also preferred that you put them in a root port node rather than the
> > host bridge.
> 
> Even though the resource split between root port and host bridge is not clear in
> Qcom SoCs, I think from logical stand point it makes sense.

Yeah, since it's typically 1:1 that's been blurred.

Rob

  reply	other threads:[~2024-06-05 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 16:05 [PATCH] dt-bindings: PCI: qcom: Fix register maps items and add 3.3V supply Abel Vesa
2024-06-04 16:09 ` Krzysztof Kozlowski
2024-06-04 16:32 ` Abel Vesa
2024-06-04 23:58 ` Rob Herring
2024-06-05  5:49   ` Manivannan Sadhasivam
2024-06-05 13:50     ` Rob Herring [this message]
2024-06-05  5:28 ` Manivannan Sadhasivam

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=20240605135033.GA2468218-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kw@linux.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.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 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).