Hi On 2018-04-19, Ram Chandra Jangir wrote: > Thanks Stefan, > > Wednesday, April 18, 2018 6:24 PM, Stefan Lippers-Hollmann > [mailto:s....@gmx.de] wrote: > > >Hi > > >On 2018-04-18, Ram Chandra Jangir wrote: > > - Rebased the patches for 4.14 > > - Dropped spi-qup and 0027, 0028, 0029 > > clk patches since it's already included > > in upstream. > > > > Tested on IPQ AP148 Board: > > 1) NOR boot and NAND boot > > 2) Tested USB and PCIe interfaces > > 3) WDOG test > > 4) cpu frequency scaling > > 5) ethernet, 2G and 5G WiFi > > 6) ubi sysupgrade > > >Thank you very much for looking into this, I've given this a very initial > test on my ZyXEL nbg6817 (ipq8065, kernel and rootfs on eMMC, u-boot on > spi-nor). While it boots up fine, there seems to be an issue with the PCIe > initialization, which consequently leads to wlan/ ath10k not working >(full > dmesg attached): > > > [ 0.066646] qcom-pcie 1b500000.pci: 1b500000.pci supply vdda not found, > using dummy regulator > > [ 0.066745] qcom-pcie 1b500000.pci: 1b500000.pci supply vdda_phy not > found, using dummy regulator > > [ 0.066836] qcom-pcie 1b500000.pci: 1b500000.pci supply vdda_refclk not > found, using dummy regulator > > [ 0.067500] OF: PCI: host bridge /soc/pci@1b500000 ranges: > > [ 0.067618] OF: PCI: IO 0x0fe00000..0x0fefffff -> 0x0fe00000 > > [ 0.067648] OF: PCI: MEM 0x08000000..0x0fdfffff -> 0x08000000 > > [ 1.100879] qcom-pcie 1b500000.pci: phy link never came up > > [ 1.102843] qcom-pcie 1b500000.pci: cannot initialize host > > [ 1.103443] qcom-pcie: probe of 1b500000.pci failed with error -110 > > [ 1.103913] qcom-pcie 1b700000.pci: 1b700000.pci supply vdda not found, > using dummy regulator > > [ 1.104028] qcom-pcie 1b700000.pci: 1b700000.pci supply vdda_phy not > found, using dummy regulator > > [ 1.104112] qcom-pcie 1b700000.pci: 1b700000.pci supply vdda_refclk not > found, using dummy regulator > > [ 1.104845] OF: PCI: host bridge /soc/pci@1b700000 ranges: > > [ 1.104883] OF: PCI: IO 0x31e00000..0x31efffff -> 0x31e00000 > > [ 1.104906] OF: PCI: MEM 0x2e000000..0x31dfffff -> 0x2e000000 > > [ 2.138765] qcom-pcie 1b700000.pci: phy link never came up > > [ 2.140724] qcom-pcie 1b700000.pci: cannot initialize host > > [ 2.141245] qcom-pcie: probe of 1b700000.pci failed with error -110 > > From log it looks like your PCI end pint is not connected properly, as link > is not up([ 1.100879] qcom-pcie 1b500000.pci: phy link never came up). > Can you please check that pci gpio values before and after probe.
Is there an easy approach to check this (it's my main router, not really with a serial console attached - although that would be possible, if there'd be a serious reason)? PCIE_QCOM is built in statically be default (CONFIG_PCIE_QCOM=y), both PCIE_DW and PCIE_QCOM are bool, so can't be included as a module. Fully booted, /sys/kernel/debug/gpio is identical between kernel 4.9 (PCIe working) and 4.14 (PCIe not working): # cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-68, parent: platform/800000.pinmux, 800000.pinmux: gpio0 : in 0 8mA no pull gpio1 : out 0 8mA no pull gpio2 : in 0 2mA pull down gpio3 : out 1 2mA no pull gpio4 : in 0 2mA pull down gpio5 : in 0 2mA pull down gpio6 : in 0 2mA pull down gpio7 : in 0 2mA pull down gpio8 : in 0 2mA pull down gpio9 : out 0 2mA pull down gpio10 : out 1 12mA no pull gpio11 : out 1 12mA no pull gpio12 : in 1 12mA no pull gpio13 : in 1 12mA no pull gpio14 : out 0 12mA pull down gpio15 : in 0 12mA pull up gpio16 : in 0 12mA pull up gpio17 : out 0 12mA pull down gpio18 : in 1 10mA pull down gpio19 : in 1 10mA pull down gpio20 : out 0 12mA pull up gpio21 : in 1 10mA pull down gpio22 : in 0 2mA pull down gpio23 : in 0 2mA pull down gpio24 : in 0 2mA pull down gpio25 : in 0 2mA pull down gpio26 : out 0 2mA pull down gpio27 : in 2 8mA no pull gpio28 : in 2 8mA no pull gpio29 : in 2 8mA no pull gpio30 : in 2 8mA no pull gpio31 : in 2 8mA no pull gpio32 : in 2 8mA no pull gpio33 : out 0 2mA pull down gpio34 : in 0 2mA pull down gpio35 : in 0 2mA pull down gpio36 : in 0 2mA pull down gpio37 : in 0 2mA pull down gpio38 : in 2 10mA pull up gpio39 : in 2 10mA pull up gpio40 : in 2 10mA pull up gpio41 : in 2 10mA pull up gpio42 : in 2 16mA no pull gpio43 : in 2 10mA pull up gpio44 : in 2 10mA pull up gpio45 : in 2 10mA pull up gpio46 : in 2 10mA pull up gpio47 : in 2 10mA pull up gpio48 : out 1 2mA no pull gpio49 : in 0 2mA pull down gpio50 : in 0 2mA pull down gpio51 : in 2 8mA no pull gpio52 : in 2 8mA no pull gpio53 : in 0 2mA pull up gpio54 : in 0 2mA pull up gpio55 : in 0 2mA pull down gpio56 : in 0 2mA pull down gpio57 : in 0 2mA pull down gpio58 : in 0 2mA pull down gpio59 : in 2 8mA no pull gpio60 : in 2 8mA no pull gpio61 : in 2 8mA no pull gpio62 : in 2 8mA no pull gpio63 : in 0 2mA pull down gpio64 : out 0 2mA pull down gpio65 : in 0 2mA pull up gpio66 : in 0 2mA pull down gpio67 : in 0 2mA pull down gpio68 : in 0 2mA pull down The device tree files are identical as well. > > I've upgraded the kernel from 4.14.34 to 4.14.35-rc1 locally though: > > I tested with 4.14.34 only, not sure whether 4.14.35 has caused anything. > > > wget -qO- > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.35-rc1 > .gz | \ > > gzip -dc > target/linux/generic/backport-4.14/001-4.14.35-rc1.patch In comparison dmesg from kernel 4.9.94-rc1 (with everything fully working) attached. Regards Stefan Lippers-Hollmann
dmesg-49.log.gz
Description: application/gzip
pgp5x4zarL5eY.pgp
Description: Digitale Signatur von OpenPGP
_______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
