Will the “ nvidia,disable-clock-request; ” parameter be valid

Version: R35.2.1

PCIE C0 Device Tree :

pcie@14180000 {
	status = "okay";

	nvidia,disable-aspm-states = <0xf>;
	nvidia,enable-power-down;
	nvidia,disable-clock-request;

#if TEGRA_PCIE_VERSION >= DT_VERSION_2
phys = <&p2u_hsio_2>, <&p2u_hsio_3>, <&p2u_hsio_4>,
<&p2u_hsio_5>;
phy-names = “p2u-0”, “p2u-1”, “p2u-2”, “p2u-3”;

else
phys = <&p2u_2>,
<&p2u_3>,
<&p2u_4>,
<&p2u_5>;
phy-names = “pcie-p2u-0”, “pcie-p2u-1”, “pcie-p2u-2”, “pcie-p2u-3”;
endif

};

Will the “ nvidia,disable-clock-request; ” parameter be valid ?

kernel/nvidia/drivers/pci/dwc/pcie-tegra.c and kernel/nvidia/drivers/pci/host/pcie-tegra-dw.c not used.

not quite sure about your question. I still see the driver use this property.

kernel-5.10/drivers/pci/controller/dwc/pcie-tegra194.c does not resolve the " nvidia,disable-clock-request; " parameter,

Is PCIE clock-request always enabled ?

xavier PCIE C0 link EP device, EP PEX_CLK0_P don’t have clk.

Hi,

I just double confirmed. This is deprecated and not in use.

supports-clkreq will be used to do the opposite behavior in latest driver.

Are PEX_C0_CLKREQ and PEX_C0_RST enabled by default in R35.2.1?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.