From: Manikanta Maddireddy <mmaddireddy@nvidia.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"kwilczynski@kernel.org" <kwilczynski@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
"kishon@kernel.org" <kishon@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Frank.Li@nxp.com" <Frank.Li@nxp.com>,
"den@valinux.co.jp" <den@valinux.co.jp>,
"hongxing.zhu@nxp.com" <hongxing.zhu@nxp.com>,
"jingoohan1@gmail.com" <jingoohan1@gmail.com>,
Vidya Sagar <vidyas@nvidia.com>,
"cassel@kernel.org" <cassel@kernel.org>,
"18255117159@163.com" <18255117159@163.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 1/9] PCI: tegra194: Drive CLKREQ# signal low explicitly
Date: Sun, 15 Mar 2026 22:46:08 +0530 [thread overview]
Message-ID: <2ec931b6-a287-419e-821e-35420c12378d@nvidia.com> (raw)
In-Reply-To: <vtylufhul43vacnq6gxvoyshtiesl2is5rmfgxw2ijlzntyvch@sbt7dhufem6q>
On 05/03/26 4:28 pm, Manivannan Sadhasivam wrote:
> On Tue, Mar 03, 2026 at 12:27:50PM +0530, Manikanta Maddireddy wrote:
>> From: Vidya Sagar <vidyas@nvidia.com>
>>
>> Currently, the default setting is that CLKREQ# signal of a Root Port
>> is internally overridden to '0' to enable REFCLK to flow out to the slot.
>> It is observed that one of the PCIe switches (case in point Broadcom PCIe
>> Gen4 switch) is propagating the CLKREQ# signal of the Root Port to the
>> downstream side of the switch and expecting the Endpoint devices to pull
>> it low so that it (PCIe switch) can give out the REFCLK although the Switch
>> as such doesn't support CLK-PM or ASPM-L1SS. So, as a workaround, this
>> patch drives the CLKREQ# of the Root Port itself low to avoid link up
>> issues between PCIe switch downstream port and Endpoint devices. This is
>
> Is the CLKREQ# signal shared with the switch and the endpoint devices
> connected to its downstream port also?
>
Yes, this is the observation.
>> not a wrong thing to do after all the CLKREQ# is anyway being overridden
>> to '0' internally and now it is just that the same is being propagated
>> outside also.
>>
>
> What do you mean by 'propagating outside'?
>
> And what is the difference between APPL_PINMUX_CLKREQ_OVERRIDE and
> APPL_PINMUX_CLKREQ_DEFAULT_VALUE?
>
> - Mani
APPL_PINMUX_CLKREQ_OVERRIDE: This overrides CLKREQ# input PAD to PCIe
controller.
APPL_PINMUX_CLKREQ_OVERRIDE: This overrides CLKREQ# output PAD to low.
Propagating outside means driving CLKREQ# pin as low.
- Manikanta
>
>> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
>> Tested-by: Jon Hunter <jonathanh@nvidia.com>
>> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
>> Signed-off-by: Manikanta Maddireddy <mmaddireddy@nvidia.com>
>> ---
>> Changes V6 -> V7: Fix commit message
>> Changes V1 -> V6: None
>>
>> drivers/pci/controller/dwc/pcie-tegra194.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-tegra194.c b/drivers/pci/controller/dwc/pcie-tegra194.c
>> index b1ae46761915..2f1f882fc737 100644
>> --- a/drivers/pci/controller/dwc/pcie-tegra194.c
>> +++ b/drivers/pci/controller/dwc/pcie-tegra194.c
>> @@ -44,6 +44,7 @@
>> #define APPL_PINMUX_CLKREQ_OVERRIDE BIT(3)
>> #define APPL_PINMUX_CLK_OUTPUT_IN_OVERRIDE_EN BIT(4)
>> #define APPL_PINMUX_CLK_OUTPUT_IN_OVERRIDE BIT(5)
>> +#define APPL_PINMUX_CLKREQ_DEFAULT_VALUE BIT(13)
>>
>> #define APPL_CTRL 0x4
>> #define APPL_CTRL_SYS_PRE_DET_STATE BIT(6)
>> @@ -1411,6 +1412,7 @@ static int tegra_pcie_config_controller(struct tegra_pcie_dw *pcie,
>> val = appl_readl(pcie, APPL_PINMUX);
>> val |= APPL_PINMUX_CLKREQ_OVERRIDE_EN;
>> val &= ~APPL_PINMUX_CLKREQ_OVERRIDE;
>> + val &= ~APPL_PINMUX_CLKREQ_DEFAULT_VALUE;
>> appl_writel(pcie, val, APPL_PINMUX);
>> }
>>
>> --
>> 2.34.1
>>
>
--
nvpublic
next prev parent reply other threads:[~2026-03-15 17:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 6:57 [PATCH v7 0/9] Enhancements to pcie-tegra194 driver Manikanta Maddireddy
2026-03-03 6:57 ` [PATCH v7 1/9] PCI: tegra194: Drive CLKREQ# signal low explicitly Manikanta Maddireddy
2026-03-05 10:58 ` Manivannan Sadhasivam
2026-03-15 17:16 ` Manikanta Maddireddy [this message]
2026-03-16 3:26 ` Manivannan Sadhasivam
2026-03-03 6:57 ` [PATCH v7 2/9] PCI: tegra194: Calibrate P2U for Endpoint mode Manikanta Maddireddy
2026-03-05 10:59 ` Manivannan Sadhasivam
2026-03-15 17:17 ` Manikanta Maddireddy
2026-03-16 3:27 ` Manivannan Sadhasivam
2026-03-03 6:57 ` [PATCH v7 3/9] PCI: tegra194: Remove IRQF_ONESHOT flag during Endpoint interrupt registration Manikanta Maddireddy
2026-03-05 11:02 ` Manivannan Sadhasivam
2026-03-05 11:04 ` Manivannan Sadhasivam
2026-03-03 6:57 ` [PATCH v7 4/9] PCI: tegra194: Enable DMA interrupt Manikanta Maddireddy
2026-03-05 11:06 ` Manivannan Sadhasivam
2026-03-03 6:57 ` [PATCH v7 5/9] PCI: tegra194: Enable hardware hot reset mode in Endpoint Manikanta Maddireddy
2026-03-03 6:57 ` [PATCH v7 6/9] PCI: tegra194: Disable L1.2 capability of Tegra234 EP Manikanta Maddireddy
2026-03-05 11:09 ` Manivannan Sadhasivam
2026-03-03 6:57 ` [PATCH v7 7/9] dt-bindings: PCI: tegra194: Add monitor clock support Manikanta Maddireddy
2026-03-03 6:57 ` [PATCH v7 8/9] PCI: tegra194: Add core " Manikanta Maddireddy
2026-03-05 11:12 ` Manivannan Sadhasivam
2026-03-15 18:06 ` Manikanta Maddireddy
2026-03-16 3:30 ` Manivannan Sadhasivam
2026-03-03 6:57 ` [PATCH v7 9/9] PCI: tegra194: Add ASPM L1 entrance latency config Manikanta Maddireddy
2026-03-05 11:15 ` 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=2ec931b6-a287-419e-821e-35420c12378d@nvidia.com \
--to=mmaddireddy@nvidia.com \
--cc=18255117159@163.com \
--cc=Frank.Li@nxp.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=conor+dt@kernel.org \
--cc=den@valinux.co.jp \
--cc=gregkh@linuxfoundation.org \
--cc=hongxing.zhu@nxp.com \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--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