[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250822135147.GA3480664-robh@kernel.org>
Date: Fri, 22 Aug 2025 08:51:47 -0500
From: Rob Herring <robh@...nel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@....qualcomm.com>
Cc: Manivannan Sadhasivam <mani@...nel.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Krzysztof WilczyĆski <kwilczynski@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Bartosz Golaszewski <brgl@...ev.pl>,
Saravana Kannan <saravanak@...gle.com>, linux-pci@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org,
Krishna Chaitanya Chundru <krishna.chundru@....qualcomm.com>,
Brian Norris <briannorris@...omium.org>
Subject: Re: [PATCH 4/6] PCI: of: Add an API to get the BDF for the device
node
On Tue, Aug 19, 2025 at 12:44:53PM +0530, Manivannan Sadhasivam wrote:
> Bus:Device:Function (BDF) numbers are used to uniquely identify a
> device/function on a PCI bus. Hence, add an API to get the BDF from the
> devicetree node of a device.
For FDT, the bus should always be 0. It doesn't make sense for FDT. The
bus number in DT reflects how firmware configured the PCI buses, but
there's no firmware configuration of PCI for FDT.
Powered by blists - more mailing lists