aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ipq806x/patches/0182-qcom-Kconfig-Make-drivers-mutually-exclusive.patch
diff options
context:
space:
mode:
authorJohn Crispin <john@openwrt.org>2015-02-11 10:09:23 +0000
committerJohn Crispin <john@openwrt.org>2015-02-11 10:09:23 +0000
commit88ddb3746188037afd38d631f7a893587fa8bdf0 (patch)
treedf4684db63441435126c4b6ff1fda4ce615e1ff0 /target/linux/ipq806x/patches/0182-qcom-Kconfig-Make-drivers-mutually-exclusive.patch
parentddcbef5766fa18f52e7a7d1928b25edc63e73937 (diff)
downloadupstream-88ddb3746188037afd38d631f7a893587fa8bdf0.tar.gz
upstream-88ddb3746188037afd38d631f7a893587fa8bdf0.tar.bz2
upstream-88ddb3746188037afd38d631f7a893587fa8bdf0.zip
ipq806x: update target to v3.18
Patches in the ipq806x/patches folder were out of tree in v3.14. The newest patch at the time was from June, so we can safely assume that either the patches have been merged, or they have been rejected for a good reason. If patches are seen missing, we'll cherry-pick them on a per-needed basis. This new kernel have been tested on AP148, which seems to works fine. Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org> SVN-Revision: 44386
Diffstat (limited to 'target/linux/ipq806x/patches/0182-qcom-Kconfig-Make-drivers-mutually-exclusive.patch')
-rw-r--r--target/linux/ipq806x/patches/0182-qcom-Kconfig-Make-drivers-mutually-exclusive.patch47
1 files changed, 0 insertions, 47 deletions
diff --git a/target/linux/ipq806x/patches/0182-qcom-Kconfig-Make-drivers-mutually-exclusive.patch b/target/linux/ipq806x/patches/0182-qcom-Kconfig-Make-drivers-mutually-exclusive.patch
deleted file mode 100644
index f4b551bac6..0000000000
--- a/target/linux/ipq806x/patches/0182-qcom-Kconfig-Make-drivers-mutually-exclusive.patch
+++ /dev/null
@@ -1,47 +0,0 @@
-From 0771849495b4128cac2faf7d49c85c729fc48b20 Mon Sep 17 00:00:00 2001
-From: Andy Gross <agross@codeaurora.org>
-Date: Mon, 30 Jun 2014 21:18:39 -0500
-Subject: [PATCH 182/182] qcom: Kconfig: Make drivers mutually exclusive
-
-This patch makes sure QCOM ADM dmaengine and QCOM Nand cannot be enabled at the
-same time. This is an issue because the dma drivers will conflict with one
-another.
-
-Signed-off-by: Andy Gross <agross@codeaurora.org>
----
- drivers/dma/Kconfig | 2 +-
- drivers/mtd/nand/Kconfig | 6 +++---
- 2 files changed, 4 insertions(+), 4 deletions(-)
-
---- a/drivers/dma/Kconfig
-+++ b/drivers/dma/Kconfig
-@@ -412,7 +412,7 @@ config QCOM_BAM_DMA
-
- config QCOM_ADM
- tristate "Qualcomm ADM support"
-- depends on ARCH_QCOM || (COMPILE_TEST && OF && ARM)
-+ depends on !MTD_QCOM_ADM && (ARCH_QCOM || (COMPILE_TEST && OF && ARM))
- select DMA_ENGINE
- select DMA_VIRTUAL_CHANNELS
- ---help---
---- a/drivers/mtd/nand/Kconfig
-+++ b/drivers/mtd/nand/Kconfig
-@@ -511,15 +511,15 @@ config MTD_NAND_XWAY
- to the External Bus Unit (EBU).
-
- config MTD_QCOM_DMA
-- tristate "QCMO NAND DMA Support"
-- depends on ARCH_QCOM && MTD_QCOM_NAND
-+ tristate "QCOM NAND DMA Support"
-+ depends on !QCOM_ADM && ARCH_QCOM && MTD_QCOM_NAND
- default n
- help
- DMA support for QCOM NAND
-
- config MTD_QCOM_NAND
- tristate "QCOM NAND Device Support"
-- depends on MTD && ARCH_QCOM
-+ depends on MTD && ARCH_QCOM && !QCOM_ADM
- select CRC16
- select BITREVERSE
- select MTD_NAND_IDS