diff options
Diffstat (limited to 'target/linux/ipq40xx/patches-4.19')
3 files changed, 0 insertions, 99 deletions
diff --git a/target/linux/ipq40xx/patches-4.19/079-v4.20-ARM-dts-qcom-ipq4019-fix-PCI-range.patch b/target/linux/ipq40xx/patches-4.19/079-v4.20-ARM-dts-qcom-ipq4019-fix-PCI-range.patch deleted file mode 100644 index ecf2a4aefb..0000000000 --- a/target/linux/ipq40xx/patches-4.19/079-v4.20-ARM-dts-qcom-ipq4019-fix-PCI-range.patch +++ /dev/null @@ -1,25 +0,0 @@ -From da89f500cb55fb3f19c4b399b46d8add0abbd4d6 Mon Sep 17 00:00:00 2001 -From: Mathias Kresin <dev@kresin.me> -Date: Wed, 25 Jul 2018 10:37:48 +0200 -Subject: [PATCH] ARM: dts: qcom: ipq4019: fix PCI range - -The PCI range is invalid and PCI attached devices doen't work. - -Signed-off-by: Mathias Kresin <dev@kresin.me> -Signed-off-by: John Crispin <john@phrozen.org> -Signed-off-by: Andy Gross <andy.gross@linaro.org> ---- - arch/arm/boot/dts/qcom-ipq4019.dtsi | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - ---- a/arch/arm/boot/dts/qcom-ipq4019.dtsi -+++ b/arch/arm/boot/dts/qcom-ipq4019.dtsi -@@ -405,7 +405,7 @@ - #size-cells = <2>; - - ranges = <0x81000000 0 0x40200000 0x40200000 0 0x00100000 -- 0x82000000 0 0x48000000 0x48000000 0 0x10000000>; -+ 0x82000000 0 0x40300000 0x40300000 0 0x400000>; - - interrupts = <GIC_SPI 141 IRQ_TYPE_EDGE_RISING>; - interrupt-names = "msi"; diff --git a/target/linux/ipq40xx/patches-4.19/083-ARM-dts-qcom-ipq4019-enlarge-PCIe-BAR-range.patch b/target/linux/ipq40xx/patches-4.19/083-ARM-dts-qcom-ipq4019-enlarge-PCIe-BAR-range.patch deleted file mode 100644 index 1283f93708..0000000000 --- a/target/linux/ipq40xx/patches-4.19/083-ARM-dts-qcom-ipq4019-enlarge-PCIe-BAR-range.patch +++ /dev/null @@ -1,42 +0,0 @@ -From: Christian Lamparter <chunkeey@gmail.com> -Date: Mon, 25 Feb 2019 20:14:19 +0100 -Subject: [PATCH] ARM: dts: qcom: ipq4019: enlarge PCIe BAR range - -David Bauer reported that the VDSL modem (attached via PCIe) -on his AVM Fritz!Box 7530 was complaining about not having -enough space in the BAR. A closer inspection of the old -qcom-ipq40xx.dtsi pulled from the GL-iNet repository listed: - -| qcom,pcie@80000 { -| compatible = "qcom,msm_pcie"; -| reg = <0x80000 0x2000>, -| <0x99000 0x800>, -| <0x40000000 0xf1d>, -| <0x40000f20 0xa8>, -| <0x40100000 0x1000>, -| <0x40200000 0x100000>, -| <0x40300000 0xd00000>; -| reg-names = "parf", "phy", "dm_core", "elbi", -| "conf", "io", "bars"; - -Matching the reg-names with the listed reg leads to -<0xd00000> as the size for the "bars". - -BugLink: https://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg45212.html -Reported-by: David Bauer <mail@david-bauer.net> -Signed-off-by: Christian Lamparter <chunkeey@gmail.com> ---- - ---- a/arch/arm/boot/dts/qcom-ipq4019.dtsi -+++ b/arch/arm/boot/dts/qcom-ipq4019.dtsi -@@ -405,8 +405,8 @@ - #address-cells = <3>; - #size-cells = <2>; - -- ranges = <0x81000000 0 0x40200000 0x40200000 0 0x00100000 -- 0x82000000 0 0x40300000 0x40300000 0 0x400000>; -+ ranges = <0x81000000 0 0x40200000 0x40200000 0 0x00100000>, -+ <0x82000000 0 0x40300000 0x40300000 0 0x00d00000>; - - interrupts = <GIC_SPI 141 IRQ_TYPE_EDGE_RISING>; - interrupt-names = "msi"; diff --git a/target/linux/ipq40xx/patches-4.19/084-ARM-dts-qcom-ipq4019-Fix-MSI-IRQ-type.patch b/target/linux/ipq40xx/patches-4.19/084-ARM-dts-qcom-ipq4019-Fix-MSI-IRQ-type.patch deleted file mode 100644 index b5492c9f98..0000000000 --- a/target/linux/ipq40xx/patches-4.19/084-ARM-dts-qcom-ipq4019-Fix-MSI-IRQ-type.patch +++ /dev/null @@ -1,32 +0,0 @@ -From: Niklas Cassel <niklas.cassel@linaro.org> -Subject: [PATCH] ARM: dts: qcom: ipq4019: Fix MSI IRQ type -Date: Thu, 24 Jan 2019 14:00:47 +0100 - -The databook clearly states that the MSI IRQ (msi_ctrl_int) is a level -triggered interrupt. - -The msi_ctrl_int will be high for as long as any MSI status bit is set, -thus the IRQ type should be set to IRQ_TYPE_LEVEL_HIGH, causing the -IRQ handler to keep getting called, as long as any MSI status bit is set. - -A git grep shows that ipq4019 is the only SoC using snps,dw-pcie that has -configured this IRQ incorrectly. - -Not having the correct IRQ type defined will cause us to lose interrupts, -which in turn causes timeouts in the PCIe endpoint drivers. - -Signed-off-by: Niklas Cassel <niklas.cassel@linaro.org> -Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org> ---- - ---- a/arch/arm/boot/dts/qcom-ipq4019.dtsi -+++ b/arch/arm/boot/dts/qcom-ipq4019.dtsi -@@ -408,7 +408,7 @@ - ranges = <0x81000000 0 0x40200000 0x40200000 0 0x00100000>, - <0x82000000 0 0x40300000 0x40300000 0 0x00d00000>; - -- interrupts = <GIC_SPI 141 IRQ_TYPE_EDGE_RISING>; -+ interrupts = <GIC_SPI 141 IRQ_TYPE_LEVEL_HIGH>; - interrupt-names = "msi"; - #interrupt-cells = <1>; - interrupt-map-mask = <0 0 0 0x7>; |