[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000b01dc101d$b834db40$289e91c0$@samsung.com>
Date: Mon, 18 Aug 2025 14:24:30 +0530
From: "Shradha Todi" <shradha.t@...sung.com>
To: "'Krzysztof Kozlowski'" <krzk@...nel.org>, <linux-pci@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
<linux-samsung-soc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-phy@...ts.infradead.org>
Cc: <mani@...nel.org>, <lpieralisi@...nel.org>, <kwilczynski@...nel.org>,
<robh@...nel.org>, <bhelgaas@...gle.com>, <jingoohan1@...il.com>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <alim.akhtar@...sung.com>,
<vkoul@...nel.org>, <kishon@...nel.org>, <arnd@...db.de>,
<m.szyprowski@...sung.com>, <jh80.chung@...sung.com>,
<pankaj.dubey@...sung.com>
Subject: RE: [PATCH v3 12/12] arm64: dts: fsd: Add PCIe support for Tesla
FSD SoC
> > +&pcieep2 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pcie1_clkreq>, <&pcie1_wake>, <&pcie1_preset>,
> > + <&pcie0_slot1>;
> > +};
> > +
> > +&pcierc0 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pcie0_clkreq>, <&pcie0_wake0>, <&pcie0_preset0>,
> > + <&pcie0_slot0>;
> > +};
> > +
> > +&pcieep0 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pcie0_clkreq>, <&pcie0_wake0>, <&pcie0_preset0>,
> > + <&pcie0_slot0>;
> > +};
> > +
> > +&pcierc1 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pcie0_clkreq>, <&pcie0_wake1>, <&pcie0_preset0>;
> > +};
> > +
> > +&pcieep1 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pcie0_clkreq>, <&pcie0_wake1>, <&pcie0_preset0>;
>
>
> All these are pointless, because the node is disabled. The board level
> should be complete, so also supplies and enabling the device.
>
I will enable required nodes. Had enabled while testing but missed to
add in patch. Though all nodes will not be enabled as it is a dual-mode
controller and cannot run as both RC and EP at the same time.
> Best regards,
> Krzysztof
Powered by blists - more mailing lists