diff options
author | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-08-19 13:25:42 +0200 |
---|---|---|
committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-08-20 14:19:39 +0200 |
commit | 83b1e40561d2e243b757bb5608b0feeb839fe1fa (patch) | |
tree | da7cc783b54b0b0b9dfa7591ece03535a7e0533a /target/linux/lantiq | |
parent | cf7c101135934710b1958092da9a0c9ad446de4b (diff) | |
download | upstream-83b1e40561d2e243b757bb5608b0feeb839fe1fa.tar.gz upstream-83b1e40561d2e243b757bb5608b0feeb839fe1fa.tar.bz2 upstream-83b1e40561d2e243b757bb5608b0feeb839fe1fa.zip |
kernel: bump 5.4 to 5.4.59
Removed since added upstream:
bcm27xx:
950-0428-staging-vchiq_arm-Add-a-matching-unregister-call.patch
lantiq:
0800-spi-lantiq-ssc-Fix-warning-by-using-WQ_MEM_RECLAI.patch
Manually adjusted patches:
layerscape:
801-audio-0005-Revert-ASoC-fsl_sai-Add-support-for-SAI-new-version.patch
Build-tested: ath79/generic, ramips, lantiq/xrx200, lantiq/xway,
mvebu/cortexa9, sunxi/a53
Run-tested: ipq806x (R7800), layerscape (LS1012A-FRDM, LS1046A-RDB)
Building on layerscape is only possible with workaround from PR #3179.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Tested-By: John Audia <graysky@archlinux.us> [ipq806x]
Tested-by: Pawel Dembicki <paweldembicki@gmail.com> [layerscape]
Diffstat (limited to 'target/linux/lantiq')
-rw-r--r-- | target/linux/lantiq/patches-5.4/0800-spi-lantiq-ssc-Fix-warning-by-using-WQ_MEM_RECLAI.patch | 35 |
1 files changed, 0 insertions, 35 deletions
diff --git a/target/linux/lantiq/patches-5.4/0800-spi-lantiq-ssc-Fix-warning-by-using-WQ_MEM_RECLAI.patch b/target/linux/lantiq/patches-5.4/0800-spi-lantiq-ssc-Fix-warning-by-using-WQ_MEM_RECLAI.patch deleted file mode 100644 index b2e1ff8907..0000000000 --- a/target/linux/lantiq/patches-5.4/0800-spi-lantiq-ssc-Fix-warning-by-using-WQ_MEM_RECLAI.patch +++ /dev/null @@ -1,35 +0,0 @@ -From 907137d9ef048e7d0282c28e47b32aa4084ad395 Mon Sep 17 00:00:00 2001 -From: Hauke Mehrtens <hauke@hauke-m.de> -Date: Mon, 6 Jul 2020 00:05:12 +0200 -Subject: [PATCH v2] spi: lantiq-ssc: Fix warning by using WQ_MEM_RECLAIM - -The lantiq-ssc driver uses internally an own workqueue to wait till the -data is not only written out of the FIFO but really written to the wire. -This workqueue is flushed while the SPI subsystem is working in some -other system workqueue. - -The system workqueue is marked as WQ_MEM_RECLAIM, but the workqueue in -the lantiq-ssc driver does not use WQ_MEM_RECLAIM for now. Add this flag -too to prevent this warning. - -This fixes the following warning: -[ 2.975956] WARNING: CPU: 1 PID: 17 at kernel/workqueue.c:2614 check_flush_dependency+0x168/0x184 -[ 2.984752] workqueue: WQ_MEM_RECLAIM kblockd:blk_mq_run_work_fn is flushing !WQ_MEM_RECLAIM 1e100800.spi:0x0 - -Fixes: 891b7c5fbf61 ("mtd_blkdevs: convert to blk-mq") -Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> ---- - drivers/spi/spi-lantiq-ssc.c | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - ---- a/drivers/spi/spi-lantiq-ssc.c -+++ b/drivers/spi/spi-lantiq-ssc.c -@@ -907,7 +907,7 @@ static int lantiq_ssc_probe(struct platf - master->bits_per_word_mask = SPI_BPW_RANGE_MASK(2, 8) | - SPI_BPW_MASK(16) | SPI_BPW_MASK(32); - -- spi->wq = alloc_ordered_workqueue(dev_name(dev), 0); -+ spi->wq = alloc_ordered_workqueue(dev_name(dev), WQ_MEM_RECLAIM); - if (!spi->wq) { - err = -ENOMEM; - goto err_clk_put; |