Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Vidya Sagar <vidyas@nvidia.com>
Cc: linux-pci@vger.kernel.org,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: PCIe tegra194 endpoint mode regulator question
Date: Wed, 17 Sep 2025 11:26:39 +0200	[thread overview]
Message-ID: <aMp-z6BufaYil30R@ryzen> (raw)

Hello Tegra PCIe maintainers,

Looking at the device tree binding for Tegra PCIe endpoint mode:
Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie-ep.yaml

We can see that 'vddio-pex-ctl-supply' is marked as required.

However, when inspecting the driver itself:
drivers/pci/controller/dwc/pcie-tegra194.c

regulator_enable(pcie->pex_ctl_supply);
is only called in tegra_pcie_config_controller().
tegra_pcie_init_controller() is called by tegra_pcie_config_rp()
(Root Complex mode), however regulator_enable(pcie->pex_ctl_supply);
is never called by tegra_pcie_config_ep() or pex_ep_event_pex_rst_deassert(),
or any other function called when the driver is using any of the
PCIe endpoint mode compatible strings.

So, I think there is something wrong here.

Either:
1) 'vddio-pex-ctl-supply' shouldn't be marked as required in the
   PCIe endpoint mode device tree binding (or perhaps not be there
   at all, since regulator_enable(pcie->pex_ctl_supply) is never called.)

2) drivers/pci/controller/dwc/pcie-tegra194.c should call
   regulator_enable(pcie->pex_ctl_supply) even in the endpoint mode case.


Looking forward to your feedback.


Kind regards,
Niklas

             reply	other threads:[~2025-09-17  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  9:26 Niklas Cassel [this message]
2025-09-18 10:47 ` PCIe tegra194 endpoint mode regulator question Jon Hunter

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=aMp-z6BufaYil30R@ryzen \
    --to=cassel@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=thierry.reding@gmail.com \
    --cc=vidyas@nvidia.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