12 Apr, 2019
5 commits
-
M4 complain that there are two much period done message sent to m4, that
M4 don't have enough time to handle these messages.The solution for this issue is to reduce the number of period done message.
We allocate a specific memory for period done message, every time there is
period done coming, it will be writed to this memory, not write it directly
to the work queue, that queue will not be overflow, and the old period done
message will be overwrited.In the rpmsg_i2s_work, we first check if there is period done message, then
send it first, after that, send the command in queue.Signed-off-by: Shengjiu Wang
Reviewed-by: Daniel Baluta
(cherry picked from commit caabdfa176453cc7c8d6521f7865a670a7265a18) -
Previously we add snd_soc_find_dai to check if the codec is probed or
not, but this bring kernel dump issue when CONFIG_LOCKDEP=y.[ 2.823379] WARNING: CPU: 2 PID: 1 at sound/soc/soc-core.c:1016 snd_soc_find_dai+0x144/0x150
[ 2.831827] Modules linked in:
[ 2.834907] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.14.78-00007-g524e1b1f0b3f #18
[ 2.842748] Hardware name: FSL i.MX8MM EVK board (DT)
[ 2.847811] task: ffff8000624f0000 task.stack: ffff000008078000
[ 2.853745] PC is at snd_soc_find_dai+0x144/0x150
[ 2.858462] LR is at snd_soc_find_dai+0x140/0x150...
[ 3.469675] Call trace:
[ 3.472135] Exception stack(0xffff00000807ba40 to 0xffff00000807bb80)
[ 3.478590] ba40: 0000000000000000 00000000ffffffff 0000000000000000 0000000000000002
[ 3.4864333.596564] [] bus_add_driver+0x110/0x230
[ 3.602149] [] driver_register+0x68/0x100
[ 3.607735] [] __platform_driver_register+0x54/0x60
[ 3.614191] [] imx_rpmsg_driver_init+0x20/0x28
[ 3.620213] [] do_one_initcall+0x44/0x130
[ 3.625801] [] kernel_init_freeable+0x1e0/0x280
[ 3.631909] [] kernel_init+0x18/0x110
[ 3.637148] [] ret_from_fork+0x10/0x1cSo we could't resolve the warning "snd_soc_register_card failed (-517)".
Fixes: 2bf5f9704785 ("MLK-19854-1: ASoC: imx-cs42888: fix error when m4
image is not loaded")
Signed-off-by: Shengjiu Wang(cherry picked from commit 58ffdf239288cfa6904640fc8432c182cf56589b)
-
Previously we add snd_soc_find_dai to check if the codec is probed or
not, but this bring kernel dump issue when CONFIG_LOCKDEP=y.[ 2.823379] WARNING: CPU: 2 PID: 1 at sound/soc/soc-core.c:1016 snd_soc_find_dai+0x144/0x150
[ 2.831827] Modules linked in:
[ 2.834907] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.14.78-00007-g524e1b1f0b3f #18
[ 2.842748] Hardware name: FSL i.MX8MM EVK board (DT)
[ 2.847811] task: ffff8000624f0000 task.stack: ffff000008078000
[ 2.853745] PC is at snd_soc_find_dai+0x144/0x150
[ 2.858462] LR is at snd_soc_find_dai+0x140/0x150...
[ 3.469675] Call trace:
[ 3.472135] Exception stack(0xffff00000807ba40 to 0xffff00000807bb80)
[ 3.478590] ba40: 0000000000000000 00000000ffffffff 0000000000000000 0000000000000002
[ 3.4864333.596564] [] bus_add_driver+0x110/0x230
[ 3.602149] [] driver_register+0x68/0x100
[ 3.607735] [] __platform_driver_register+0x54/0x60
[ 3.614191] [] imx_rpmsg_driver_init+0x20/0x28
[ 3.620213] [] do_one_initcall+0x44/0x130
[ 3.625801] [] kernel_init_freeable+0x1e0/0x280
[ 3.631909] [] kernel_init+0x18/0x110
[ 3.637148] [] ret_from_fork+0x10/0x1cSo we could't resolve the warning "snd_soc_register_card failed (-517)".
Fixes: a52c88bc3932 ("MLK-19854-1: ASoC: imx-wm8960: fix error when m4
image is not loaded")
Signed-off-by: Shengjiu Wang(cherry picked from commit f5d9013702e172a243da74a42941a62283bbe4a8)
-
Previously we add snd_soc_find_dai to check if the codec is probed or
not, but this bring kernel dump issue when CONFIG_LOCKDEP=y.[ 2.823379] WARNING: CPU: 2 PID: 1 at sound/soc/soc-core.c:1016 snd_soc_find_dai+0x144/0x150
[ 2.831827] Modules linked in:
[ 2.834907] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.14.78-00007-g524e1b1f0b3f #18
[ 2.842748] Hardware name: FSL i.MX8MM EVK board (DT)
[ 2.847811] task: ffff8000624f0000 task.stack: ffff000008078000
[ 2.853745] PC is at snd_soc_find_dai+0x144/0x150
[ 2.858462] LR is at snd_soc_find_dai+0x140/0x150...
[ 3.469675] Call trace:
[ 3.472135] Exception stack(0xffff00000807ba40 to 0xffff00000807bb80)
[ 3.478590] ba40: 0000000000000000 00000000ffffffff 0000000000000000 0000000000000002
[ 3.4864333.596564] [] bus_add_driver+0x110/0x230
[ 3.602149] [] driver_register+0x68/0x100
[ 3.607735] [] __platform_driver_register+0x54/0x60
[ 3.614191] [] imx_rpmsg_driver_init+0x20/0x28
[ 3.620213] [] do_one_initcall+0x44/0x130
[ 3.625801] [] kernel_init_freeable+0x1e0/0x280
[ 3.631909] [] kernel_init+0x18/0x110
[ 3.637148] [] ret_from_fork+0x10/0x1cSo we could't resolve the warning "snd_soc_register_card failed (-517)".
Fixes: 75632b22a332 ("MLK-20247: ASoC: imx-rpmsg: fix error when
m4 image is not loaded")
Signed-off-by: Shengjiu Wang(cherry picked from commit bbc1868d1c3ec448301d76606e7199f74aa35581)
-
With CONFIG_LOCKDEP=y, there will kernel dump
[ 55.305563] INFO: trying to register non-static key.
[ 55.310540] the code is fine but needs lockdep annotation.
[ 55.316027] turning off the locking correctness validator.
[ 55.321520] CPU: 0 PID: 32 Comm: kworker/0:1 Tainted: G W 4.14.78-00007-g524e1b1f0b3f #18
[ 55.330827] Hardware name: FSL i.MX8MM EVK board (DT)
[ 55.335892] Workqueue: events rpmsg_work_handler
[ 55.340515] Call trace:
[ 55.342971] [] dump_backtrace+0x0/0x270
[ 55.348375] [] show_stack+0x24/0x30
[ 55.353433] [] dump_stack+0xb8/0xf0
[ 55.358490] [] register_lock_class+0x364/0x548
[ 55.364501] [] __lock_acquire+0x7c/0x18a8
[ 55.370077] [] lock_acquire+0xc8/0x290
[ 55.375394] [] _raw_spin_lock_irqsave+0x54/0x70
[ 55.381493] [] i2s_rpmsg_cb+0xe8/0x1b0
[ 55.386810] [] rpmsg_recv_done+0x144/0x210
[ 55.392476] [] vring_interrupt+0x44/0x78
[ 55.397966] [] imx_mu_rpmsg_callback+0x6c/0x80
[ 55.403977] [] notifier_call_chain+0x5c/0x98
[ 55.409813] [] __blocking_notifier_call_chain+0x58/0xa0
[ 55.416605] [] blocking_notifier_call_chain+0x3c/0x50
[ 55.423223] [] rpmsg_work_handler+0x88/0xe8
[ 55.428974] [] process_one_work+0x290/0x738
[ 55.434723] [] worker_thread+0x58/0x460
[ 55.440127] [] kthread+0x104/0x130
[ 55.445096] [] ret_from_fork+0x10/0x1cThe reason is that the spin lock is not initilized.
Signed-off-by: Shengjiu Wang
(cherry picked from commit 0e98ac55f17f6505f92c515c3c04581039e21865)
11 Apr, 2019
1 commit
-
Add the missing complete operations for dma_completion to fix the
problem of blocking at the wait_for_completion_interruptible()
function in some situations.Signed-off-by: Clark Wang
(cherry picked from commit a19a00c51df5c3ead4d64ea3136f5bce60b2e6af)
10 Apr, 2019
5 commits
-
The variable "is_canfd" will stay true after the following sequence:
root@imx8qxpmek:~# ip link set can0 type can bitrate 1000000 dbitrate 4000000 fd on
root@imx8qxpmek:~# ip link set can0 up
root@imx8qxpmek:~# ip link set can0 down
root@imx8qxpmek:~# ip link set can0 type can bitrate 1000000It will use alloc_canfd_skb() to allocate skb for normal CAN when
"is_canfd" is true, which will affect the receive of remote frame.Signed-off-by: Joakim Zhang
-
should check imx8-gpu instead of imx8x-gpu string for i.mx8 gpu sub-system
Signed-off-by: Xianzhong
(cherry picked from commit ce6483c43465651469c75b0e5093bdc749866f84) -
Disable typec irq when suspend to avoid the threaded irq to access
some resource(e.g. i2c over rpmsg) but those resource is not
available at later phrase, also use IRQ_DISABLE_UNLAZY flag to
mask the irq on irq chip level when irq happens.Suggested-by: Anson Huang
Acked-by: Peter Chen
Signed-off-by: Li Jun
(cherry picked from commit 61869f787fb0ee2f00d0fe9443cb8b487e16e5ec) -
While system suspend, the typec event handling required service
maybe is not available(suspended), so we need freeze those event
handling by using freezable workqueue, e.g while tcpm is handling
PD message but system suspend started.Acked-by: Peter Chen
Signed-off-by: Li Jun
(cherry picked from commit 270d4df94b7c2c773a171fe012fb8ce89196964f) -
We should assign dedicated id for every tcon instance.
This makes us be able to figure out bewteen master and
slave tcon. Only side-by-side display mode is likely
impacted. Based on tests, no functional change is
observed before or after this patch is applied.Signed-off-by: Liu Ying
(cherry picked from commit e181d9e56b096bbdc919f65b223d1bde413df1bb)
29 Mar, 2019
4 commits
-
Introduce inmate linux support for jailhouse, we need to benchmark
inmate OS, so choose linux. The clock/pin are preconfigured by 1st
root cell linux.Signed-off-by: Peng Fan
Acked-by: Ye Li -
CID: 5781508
device pointer should not be used before null checkSigned-off-by: Xianzhong
(cherry picked from commit 17942905375a282ed9896c3cc778a246c321f5f0) -
Vulkan driver has problem to commit command without device mutex,
command object has race condition risk without mutex protection.move _ProcessUserCommandBufferList into command mutex region.
Signed-off-by: Xianzhong
(cherry picked from commit 10120a64fd9342c8effd21eb62bc51f88f1493cb) -
It is only used in this file, so staticize it.
Signed-off-by: Liu Ying
(cherry picked from commit e293f8671509ed54c83a51b40da53da3bdf216f5)
28 Mar, 2019
6 commits
-
It isn't used out side of the file for now.
Signed-off-by: Liu Ying
(cherry picked from commit 13a0d5c3b15e42834b872b0da904f874ff717500) -
Due to TKT320590, we are asked to turn TCON into operation mode later after
the first dumb frame is generated by DPU. This makes DPR/PRG be able to
evade the frame. However, it turns out we have to set the TCON into operation
mode first and then wait for Framegen frame counter moving, otherwise, the
display pipeline cannot be setup correctly sometimes(If pixel combiner is used,
one of the two display streams is likely broken). This is a mysterious issue.
So, we've already taken a workaround for the cases where pixel combiner is used.It appears that the similar issue is likely to happen for cases where pixel
combiner is unused. That is to say, if pixel combiner is unused and prefetch
engine is used, the first atomic flush after the enablement is likely to fail -
content shadow load irq doesn't come. The sequence which the patch takes is
the same to the one taken by the previous workaround. Based on tests, it is
valid for cases with or without pixel combiner.Signed-off-by: Liu Ying
(cherry picked from commit b6126aa9697c77896d2085997eec2a6995509f4b) -
To avoid potential division by zero in ipu_init_sync_panel(),
let's check the rounded_pixel_clk rate prior to that.Detected by CoverityScan, CID#56278 ("Division or modulo by zero")
Signed-off-by: Liu Ying
(cherry picked from commit 1523150b71f1aa0610f61ea47a9f3bdbcda92522) -
To avoid potential division by zero in ipu_init_async_panel(),
let's check the di_clk rate prior to that.Detected by CoverityScan, CID#56264 ("Division or modulo by zero")
Signed-off-by: Liu Ying
(cherry picked from commit d7777247e6ba4ca9fcc313bef6672060859fed19) -
To avoid potential out of bounds array access on tbl->used[][],
let's check the tsk->ipu_id prior to that. Based on the context,
this is what we can do to make the coverity happy.Detected by CoverityScan, CID#17689 ("Derefernece before null check")
Signed-off-by: Liu Ying
(cherry picked from commit f5dcf709c54da8e64eb84f1dd7a4452ad8d942cf) -
The check on !sp_tsk0 is unnecessary in ipu_task_thread(), because the
beforehand "list_del(&sp_tsk0->node);" within the context implies sp_tsk0
is not null, otherwise, we'll dereference a null pointer earlier.Detected by CoverityScan, CID#17842 ("Logically dead code")
Signed-off-by: Liu Ying
(cherry picked from commit 9ad5edd076d61bc8bb3a558e523cc7b31f2c3043)
27 Mar, 2019
8 commits
-
Because we are re-initializing the proxy at close it might
happen that work is still pending which causes the following crash:[ 94.699835] Unable to handle kernel NULL pointer dereference at virtual address 00000008
[ 94.707923] Mem abort info:
[ 94.710722] Exception class = DABT (current EL), IL = 32 bits
[ 94.716637] SET = 0, FnV = 0
[ 94.719686] EA = 0, S1PTW = 0
[ 94.722822] Data abort info:
[ 94.725698] ISV = 0, ISS = 0x00000005
[ 94.729530] CM = 0, WnR = 0
[ 94.732504] user pgtable: 4k pages, 48-bit VAs, pgd = ffff8008d9ba3000
[ 94.739035] [0000000000000008] *pgd=0000000938419003, *pud=0000000000000000
[ 94.746015] Internal error: Oops: 96000005 [#1] PREEMPT SMP
[ 94.751589] Modules linked in:
[ 94.754652] CPU: 0 PID: 2068 Comm: kworker/0:2 Not tainted 4.14.98-dirty #75
[ 94.761700] Hardware name: Freescale i.MX8QM MEK (DT)
[ 94.766768] task: ffff8008f23ae200 task.stack: ffff000014378000
[ 94.772705] PC is at process_one_work+0x34/0x414
[ 94.777325] LR is at process_one_work+0x1e0/0x414In order to fix this, we make sure that no work is pending before starting
the re-initialization.Signed-off-by: Daniel Baluta
Reviewed-by: Shengjiu Wang
(cherry picked from commit 2c00c24be5f8b63636e3f9005e15a3de42058438) -
Double check that the DTG IRQ STATUS register bit is set when handling
the vblank and CTXLD kick interrupts to make sure we avoid spurious
interrupts and kick the CTXLD in a bad moment.Signed-off-by: Laurentiu Palcu
Reviewed-by: Robert Chiras
(cherry picked from commit cc56e4e07f623d0b831e0f8347f2f3198697ee20) -
Using one completion variable is not feasible as we can hit corner cases like
enabling and then quickly disabling DCSS where we end up signaling that DTG was
correctly disabled when, in fact, a VBLANK interrupt was received.Signed-off-by: Laurentiu Palcu
Reviewed-by: Robert Chiras
(cherry picked from commit 8073e87dce34548bea758c34d3b3557819c75551) -
Currently, we set the colorimetry to BT.2020 even if the color-depth is
8 bit. This is not according to HDMI specification.This patch makes sure we follow the specs.
Signed-off-by: Laurentiu Palcu
CC: Sandor Yu
Reviewed-by: Sandor Yu
Reviewed-by: Robert Chiras
(cherry picked from commit cdacfaadd5dccfdca5dd68640d8f08506f6a9114) -
A fixed PLL PMS setting for attached panel is obviously not
enough for any other mipi panel which needs a different PLL
output clock frequency, and besides, for the CEA-861 standard
display modes, the 'pll_pms' table also can not cover all the
modes requirements. So a general way is created to solve this
problem which can provide an optimum solution to output a PLL
bit clock to match the request frequency in a maximum degree
and also satisfy the input clock and intermediate clocks limit
according to the PLL specification.Signed-off-by: Fancy Fang
(cherry picked from commit a73fdd5e48fe0df47685cfc197fe66edc1e28405) -
Add a new property 'pref-rate' support which can be used to
assign a different clock frequency for the DPHY PLL reference
clock in the dtb file. And if this property does not exist,
the default clock frequency for the reference clock will be
used. And according to the spec, the DPHY PLL reference clk
frequency should be in [6MHz, 300MHz] range.Signed-off-by: Fancy Fang
(cherry picked from commit a9fafe8108505f8a1580af898ff5fa9c26d03680) -
When there is no existing horizontal blanking word counts in
'dsim_hblank_par' tables, these data requires to be computed
according to the 'hfp', 'hbp' and 'hsa' timings which are in
pixel unit. So the pixel unit data requires to be converted
to word count unit data correctly to match the PLL output clk
frequency.Signed-off-by: Fancy Fang
(cherry picked from commit af9ab0d4362d9298978e2ac62033f65ea1cc09ed) -
Change the 'bit_clk' and 'pix_clk' fields of struct sec_mipi_dsim
and the 'bit_clk' field of struct dsim_pll_pms from 'uint64_t' type
to 'uint32_t' type, since first, these two fields are in KHz unit,
and so 32 bit unsigned integer is enough to hold the data values,
and second, use 32 bit integer can simplify related clocks compute.Signed-off-by: Fancy Fang
(cherry picked from commit 3e62c748a531ca5eacbf6a616d3a979be5222b9c)
25 Mar, 2019
1 commit
-
Since, the partition reset irq would be triggered anytime.
Do not read the status of the MU if master side is in suspend mode.Signed-off-by: Richard Zhu
(cherry picked from commit 117dbcb1ce258587f8d162c0b3219f32d6de6fbc)
24 Mar, 2019
7 commits
-
Coverity reported potential arithmetic overflow of a 32-bit
multiply operation. Adding a cast to promote the mulitply opertion to use
64 bits.Signed-off-by: Oliver Brown
-
Coverity reported a potential divide by zero. Adding a check to prevent
a divide by zero.Signed-off-by: Oliver Brown
-
Fixed a dead code error reported by Coverity.
CID 1826265: Logically dead codeSigned-off-by: Oliver Brown
(cherry picked from commit 4b25b038a2278b0782e144ec3e3907fbcbc138c1) -
Fixed two issues resported by Coverity:
CID 343354: Uninitialized scalar variable
CID 343355: Uninitialized scalar variableSigned-off-by: Oliver Brown
(cherry picked from commit abc359e835dca5942d9dc101bfdc55f243e01d65) -
Fixed CID 3411368, Unsigned compared against 0. Removed comparison with
no effect.Signed-off-by: Oliver Brown
(cherry picked from commit 7a90cb82d00109cdd00eea67fbf9d75b6efe6172) -
Fixed CID 17375, Unsigned compared against 0. Removed code with no effect.
Signed-off-by: Oliver Brown
(cherry picked from commit b86debc52acd4131515f62130f52c2d0f48cdbfe) -
Fix Covertity CID 18110 Uninitialized scalar variable
Signed-off-by: Oliver Brown
(cherry picked from commit 0f2a05c5cef95dabdbdd1e78531cd42aec24876a)
23 Mar, 2019
1 commit
-
Some rpmsg user may require rpmsg resume before the user start
handle its irq, e.g the typec controller use a GPIO as irq and
use rpmsg to get event status, so move imx rpmsg power management
ops to noirq phrase.Reviewed-by: Richard Zhu
Tested-by: Clark Wang
Signed-off-by: Anson Huang
Signed-off-by: Li Jun
22 Mar, 2019
2 commits
-
Changing error message "Link rate is too high - forcing link to lower rate"
to a debug message "Lowering DP link rate from to ".Signed-off-by: Oliver Brown
-
Although the hardware spec doesn't mention the additional operation to
wait for FrameGen secondary syncup for non-PC cases(FrameGen non-sync mode)
when we enable a display, it turns out it helps avoid content stream(i.e.,
extdst0 or extdst1) shadow load done event missing issue when the first
page flip ocurrs after the display enablement. Black/blanked display
is observed when the issue happens, which means the video signal is likely
totally off. Adding this waiting operation also aligns to the cases
where PC is used.Signed-off-by: Liu Ying
(cherry picked from commit cfedc1269f35054c79d7fd2e2a914e97a4c1a47a)