From: kernel test robot <lkp@intel.com>
To: Manikanta Maddireddy <mmaddireddy@nvidia.com>,
jingoohan1@gmail.com, mani@kernel.org, lpieralisi@kernel.org,
kwilczynski@kernel.org, bhelgaas@google.com,
linux-pci@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, robh@kernel.org,
thierry.reding@kernel.org, jonathanh@nvidia.com,
vidyas@nvidia.com, cassel@kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
mmaddireddy@nvidia.com
Subject: Re: [PATCH v2 3/3] PCI: tegra194: Notify Endpoint functions on PERST# assert
Date: Fri, 23 Oct 2026 09:38:54 +0800 [thread overview]
Message-ID: <202610230923.2lf3BsLs-lkp@intel.com> (raw)
In-Reply-To: <20261021061903.1269605-4-mmaddireddy@nvidia.com>
Hi Manikanta,
kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus linus/master v7.3 next-20261022]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Manikanta-Maddireddy/PCI-dwc-Reuse-Endpoint-resources-after-fundamental-reset/20261021-114901
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20261021061903.1269605-4-mmaddireddy%40nvidia.com
patch subject: [PATCH v2 3/3] PCI: tegra194: Notify Endpoint functions on PERST# assert
config: xtensa-randconfig-1001-20261022 (https://download.01.org/0day-ci/archive/20261023/202610230923.2lf3BsLs-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 15.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261023/202610230923.2lf3BsLs-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202610230923.2lf3BsLs-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/pci/controller/dwc/pcie-tegra194.c: In function 'pex_ep_event_pex_rst_assert':
>> drivers/pci/controller/dwc/pcie-tegra194.c:1708:9: error: implicit declaration of function 'pci_epc_linkdown'; did you mean 'dw_pcie_ep_linkdown'? [-Wimplicit-function-declaration]
1708 | pci_epc_linkdown(pcie->pci.ep.epc);
| ^~~~~~~~~~~~~~~~
| dw_pcie_ep_linkdown
vim +1708 drivers/pci/controller/dwc/pcie-tegra194.c
1688
1689 static void pex_ep_event_pex_rst_assert(struct tegra_pcie_dw *pcie)
1690 {
1691 u32 val;
1692 int ret;
1693
1694 if (pcie->ep_state == EP_STATE_DISABLED)
1695 return;
1696
1697 ret = readl_poll_timeout(pcie->appl_base + APPL_DEBUG, val,
1698 ((val & APPL_DEBUG_LTSSM_STATE_MASK) == LTSSM_STATE_DETECT_QUIET) ||
1699 ((val & APPL_DEBUG_LTSSM_STATE_MASK) == LTSSM_STATE_DETECT_ACT) ||
1700 ((val & APPL_DEBUG_LTSSM_STATE_MASK) == LTSSM_STATE_PRE_DETECT_QUIET) ||
1701 ((val & APPL_DEBUG_LTSSM_STATE_MASK) == LTSSM_STATE_DETECT_WAIT) ||
1702 ((val & APPL_DEBUG_LTSSM_STATE_MASK) == LTSSM_STATE_L2_IDLE),
1703 LTSSM_DELAY_US, LTSSM_TIMEOUT_US);
1704 if (ret)
1705 dev_info(pcie->dev, "LTSSM state: 0x%x detect timeout: %d\n", val, ret);
1706
1707 /* Avoid the DBI register reinitialization in dw_pcie_ep_linkdown(). */
> 1708 pci_epc_linkdown(pcie->pci.ep.epc);
1709
1710 /*
1711 * Deassert LTSSM state to stop the state toggling between
1712 * Polling and Detect.
1713 */
1714 val = appl_readl(pcie, APPL_CTRL);
1715 val &= ~APPL_CTRL_LTSSM_EN;
1716 appl_writel(pcie, val, APPL_CTRL);
1717
1718 reset_control_assert(pcie->core_rst);
1719
1720 tegra_pcie_disable_phy(pcie);
1721
1722 reset_control_assert(pcie->core_apb_rst);
1723
1724 clk_disable_unprepare(pcie->core_clk);
1725
1726 pm_runtime_put_sync(pcie->dev);
1727
1728 if (pcie->enable_ext_refclk) {
1729 ret = tegra_pcie_bpmp_set_pll_state(pcie, false);
1730 if (ret)
1731 dev_err(pcie->dev, "Failed to turn off UPHY: %d\n",
1732 ret);
1733 }
1734
1735 ret = tegra_pcie_bpmp_set_ctrl_state(pcie, false);
1736 if (ret)
1737 dev_err(pcie->dev, "Failed to disable controller: %d\n", ret);
1738
1739 pcie->ep_state = EP_STATE_DISABLED;
1740 dev_dbg(pcie->dev, "Uninitialization of endpoint is completed\n");
1741 }
1742
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-10-23 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 6:19 [PATCH v2 0/3] PCI: dwc: Avoid full EP cleanup on PERST# Manikanta Maddireddy
2026-10-21 6:19 ` [PATCH v2 1/3] PCI: dwc: Reuse Endpoint resources after fundamental reset Manikanta Maddireddy
2026-10-21 6:38 ` sashiko-bot
2026-10-21 6:19 ` [PATCH v2 2/3] PCI: tegra194: Avoid full Endpoint reinit on PERST# Manikanta Maddireddy
2026-10-21 6:48 ` sashiko-bot
2026-10-21 6:19 ` [PATCH v2 3/3] PCI: tegra194: Notify Endpoint functions on PERST# assert Manikanta Maddireddy
2026-10-21 7:00 ` sashiko-bot
2026-10-23 1:38 ` kernel test robot [this message]
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=202610230923.2lf3BsLs-lkp@intel.com \
--to=lkp@intel.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--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=mmaddireddy@nvidia.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
--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 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.