lkml.org 
[lkml]   [2021]   [Jun]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH v3 2/5] arm64: dts: ti: k3-am64-main: Add PCIe DT node
    From
    Date
    Hi Nishanth,

    On 27/05/21 12:21 am, Nishanth Menon wrote:
    > On 19:59-20210526, Kishon Vijay Abraham I wrote:
    >> AM64 has one PCIe instance which can be configured in either
    >> host mode (RC) or device mode (EP). Add PCIe DT node for host
    >> mode and device mode here.
    >>
    >> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
    >> ---
    >> arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 46 ++++++++++++++++++++++++
    >> 1 file changed, 46 insertions(+)
    >>
    >> diff --git a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
    >> index a67f10406a8e..9c77f7da5d28 100644
    >> --- a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
    >> +++ b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
    >> @@ -728,4 +728,50 @@
    >> #clock-cells = <1>;
    >> };
    >> };
    >> +
    >> + pcie0_rc: pcie@f102000 {
    >> + compatible = "ti,am64-pcie-host", "ti,j721e-pcie-host";
    >> + reg = <0x00 0x0f102000 0x00 0x1000>,
    >> + <0x00 0x0f100000 0x00 0x400>,
    >> + <0x00 0x0d000000 0x00 0x00800000>,
    >> + <0x00 0x68000000 0x00 0x00001000>;
    >> + reg-names = "intd_cfg", "user_cfg", "reg", "cfg";
    > [...]
    >> +
    >> + pcie0_ep: pcie-ep@f102000 {
    > Hmm...
    > Warning (unique_unit_address): /bus@f4000/pcie@f102000: duplicate unit-address (also used in node /bus@f4000/pcie-ep@f102000)
    > we could pick reg for pcie-ep for node address, instead of intd_cfg address?
    >
    > OR, does that mess something else up?

    yeah, that actually require changes in the binding to fix it properly,
    since only the first entry in reg should be given for unit address.

    Thanks
    Kishon

    >
    >> + compatible = "ti,am64-pcie-ep", "ti,j721e-pcie-ep";
    >> + reg = <0x00 0x0f102000 0x00 0x1000>,
    >> + <0x00 0x0f100000 0x00 0x400>,
    >> + <0x00 0x0d000000 0x00 0x00800000>,
    >> + <0x00 0x68000000 0x00 0x08000000>;
    >
    > [...]
    >

    \
     
     \ /
      Last update: 2021-06-03 16:18    [W:12.430 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site