29 Jan, 2021
2 commits
-
enable runtime setting gic clk(500M → 100M)
Change-Id: I79e07ffcf645ee7f26ec1fc701d44f3e7502cb62
Signed-off-by: zhipeng.wang -
Under normal circumstances, the ddr frequencies of audio_bus_mode and
low_bus_mode are both 100mts. Now in order to meet Sony’s requirements,
both audio_bus_mode and low_bus_mode are changed to 400mts.Change-Id: I68f878a52069136f4b8ff84b06a55b8ea1eae99d
28 Jan, 2021
8 commits
-
…t to a hotspot and run MM automation test, 4/4
it meet rcu issue within 2 hours when do Apollo stress test(fetch mm streams and play/pause/accelerate play/seek/.. streams)
below is the condition when meet issue:
1. thread A enter the logic which is protected by RCU lock.
2. thread A is schedule out.
3. thread B(it means worker quene xf_proxy_process here) or irq callback funtion call MU_SendMessage
4. MU_SendMessage hang in "while" loop
5. thread A can't been schedule in CONFIG_RCU_CPU_STALL_TIMEOUT seconds(the nice of Thread A is not high than thread B). it cause rcu issue.This patch add 50ms for while logic so that it will not hang in MU_SendMessage.
-------- beginning of crash
04-27 00:36:32.408 F/libc ( 353): crash_dump helper failed to exec
[ 1186.326364] init: Untracked pid 6333 received signal 14
04-27 00:36:37.133 F/libc ( 1389): crash_dump helper failed to exec
[ 1188.676005] rcu: INFO: rcu_preempt self-detected stall on CPU
[ 1188.681753] rcu: 1-....: (99605 ticks this GP) idle=c76/1/0x4000000000000002 softirq=35006/35006 fqs=49746
[ 1188.691575] (t=99768 jiffies g=119805 q=26095)
[ 1188.696103] Task dump for CPU 1:
[ 1188.699325] kworker/1:0 R running task 0 3467 2 0x0000002a
[ 1188.706381] Workqueue: events xf_proxy_process
[ 1188.710817] Call trace:
[ 1188.713262] dump_backtrace+0x0/0x134
[ 1188.716917] show_stack+0x14/0x1c
[ 1188.720227] sched_show_task+0xf8/0x104
[ 1188.724057] dump_cpu_task+0x40/0x4c
[ 1188.727629] rcu_dump_cpu_stacks+0xa0/0xf4
[ 1188.731721] rcu_sched_clock_irq+0x53c/0x98c
[ 1188.735988] update_process_times+0x6c/0x94
[ 1188.740174] tick_sched_timer+0x90/0xf8
[ 1188.744004] __hrtimer_run_queues+0x118/0x1bc
[ 1188.748356] hrtimer_interrupt+0xf4/0x338
[ 1188.752362] arch_timer_handler_phys+0x34/0x40Change-Id: I9d49f0d1f9675129511a1bfc74b2369d99f2d4b9
Signed-off-by: zhang sanshan <pete.zhang@nxp.com> -
add isi and ov5640 dts setting into imx8qm-mek-hdmi.dts.
imx8qm-mek-hdmi.dts is included by md dts.
camera is also is needed by hdmi dts.Change-Id: I51d31bc21a1d1b8af90a0cf0c5b51137773d3c12
Signed-off-by: zhang sanshan -
if clk is build as module, reset-dispmix is set as Y by default.
reset-dispmix will fail when probe, because it is depended on clk which is still not ready.
display driver will failed if reset-dispmix failed.Change-Id: Ib86f71256dcf41924e063e73f94eac4494e41e89
Signed-off-by: zhang sanshan -
below is the scene when meet issue running module CtsCameraTestCases.
1. It will operate list(like list_del) in cap_vb2_stop_streaming.
2. Althrough the list is protected by spin_lock_irqsave step 1 which disable interrupt.
It will also operate list in mxc_isi_cap_frame_write_done, it's in context of interrupt(mxc_isi_irq_handler)
this interrupt is from different cpu compared with step1.this patch use spin_lock_irqsave/spin_unlock_irqrestore in interrupt context to protect the shared
data (out_pending/out_discard/out_pending).Change-Id: I19bab22f9c7c91d791bc5c983ecc8cc6afdeaddc
Signed-off-by: zhang sanshan -
mx6s_capture use vb2_dma_contig_memops as default me_ops.
select VIDEOBUF2_DMA_CONTIG by default.VIDEOBUF2_DMA_CONTIG have no hardware involved, and mx6s_capture.c need
compile as module according gki requirement. so need set VIDEOBUF2_DMA_CONTIG
as y in defconfig, it require add menu item string here for VIDEOBUF2_DMA_CONTIGChange-Id: Ie91093c52af199146b8aae29ea13fa7558e24649
Signed-off-by: zhang sanshan -
This reverts commit 1dee40a806ab5764d2d5b250525a278b53b51b82.
Change-Id: I7bc925ca02fd64b4f79b4d25844374b4d918432b
-
Build nxp mxmwifi driver out of kernel tree on L5.10
Revert "MA-18497 Add initial nxp mxmwifidriver on L5.10"
This reverts commit b5cad372dfbd3f3f72656ba57bb71ac1f4b837d5.Change-Id: I9c7cfe2c8ffbe74defc26570a9222170a76a61bc
Signed-off-by: yang.tian -
Build nxp mxmwifi driver out of kernel tree on L5.10
Revert "MA-18230-2 Enable nxp wifi 88w8997 with mxmdriver"
This reverts commit eb2ca694eb279fa32acf8368120b34b385ba469b.Change-Id: I73da9fc2396a4a16cf7a91de9b2ac2c9f641fe0d
Signed-off-by: yang.tian
27 Jan, 2021
4 commits
-
DMA_VIRTUAL_CHANNELS depends on DMADEVICES and DMA_VIRTUAL_CHANNELS
is selected by GKI_HIDDEN_SND_SOC_CONFIGS.To fix unmet dependency in x86_64, select DMADEVICES under
GKI_HIDDEN_SND_SOC_CONFIGS.Also, drop CONFIG_DMADEVICES=y in arch/arm64/configs/gki_defconfig.
WARNING: unmet direct dependencies detected for DMA_VIRTUAL_CHANNELS
Depends on [n]: DMADEVICES [=n]
Selected by [y]:
- GKI_HIDDEN_SND_SOC_CONFIGS [=y]Bug: 174628645
Signed-off-by: Miles Chen
Change-Id: I1de491c10542f1b7c9c8754c65415b028d3bc922 -
Wire up the splice_read and splice_write methods to the default
helpers using ->read_iter and ->write_iter now that those are
implemented for kernfs. This restores support to use splice and
sendfile on kernfs files.Fixes: 36e2c7421f02 ("fs: don't allow splice read/write without explicit ops")
Reported-by: Siddharth Gupta
Tested-by: Siddharth Gupta
Signed-off-by: Christoph Hellwig
Link: https://lore.kernel.org/r/20210120204631.274206-4-hch@lst.de
Signed-off-by: Greg Kroah-Hartman
(cherry picked from commit f2d6c2708bd84ca953fa6b6ca5717e79eb0140c7)
Bug: 176079972
Signed-off-by: Greg Kroah-Hartman
Change-Id: I80f09db0b8569fa63db59ada9c3d45d6600b2d70 -
Switch kernfs to implement the write_iter method instead of plain old
write to prepare to supporting splice and sendfile again.Signed-off-by: Christoph Hellwig
Link: https://lore.kernel.org/r/20210120204631.274206-3-hch@lst.de
Signed-off-by: Greg Kroah-Hartman
(cherry picked from commit cc099e0b399889c6485c88368b19824b087c9f8c)
Signed-off-by: Greg Kroah-Hartman
Change-Id: I660c93c520169534c874cef2d246fef8c8fe2bbc -
Switch kernfs to implement the read_iter method instead of plain old
read to prepare to supporting splice and sendfile again.Signed-off-by: Christoph Hellwig
Link: https://lore.kernel.org/r/20210120204631.274206-2-hch@lst.de
Signed-off-by: Greg Kroah-Hartman
(cherry picked from commit 4eaad21a6ac9865df7f31983232ed5928450458d)
Signed-off-by: Greg Kroah-Hartman
Change-Id: I75af3b3bae22de7ba46ec38b8182be335d6760e8
26 Jan, 2021
1 commit
-
By modifying /sys/devices/system/cpu/cpufreq/schedutil/up_rate_limit_us or down_rate_limit_us,
change the time of schedutil's low frequency increase or high frequency reduction. The unit of the value is microseconds.Change-Id: I15c06ed92c0ba012a6d79887b3b8f004b5be50fc
Signed-off-by: zhang sanshan
25 Jan, 2021
3 commits
-
Change-Id: I56f21ca5d08858f763395359baedb6f1a3b9066c
-
Change-Id: I173bc0325c93daaf82bb894f77ba35fa827864de
-
HAVE_COMPAT_IOCTL define is removed from include/linux/fs.h
on 5.10 kernel by below kernel patch, driver should remove
HAVE_COMPAT_IOCTL check, other drivers don’t have such check.
Kernel patch:
https://lkml.org/lkml/2020/6/22/218Change-Id: I428f762f929d1689d558b18349dd4ce536ac51f6
Signed-off-by: Richard Liu
22 Jan, 2021
10 commits
-
Remove less-than-zero comparison of an unsigned value
Signed-off-by: Sandor Yu
Reviewed-by: Robby Cai -
Check return value to fix Coverity Issue: 11566403.
Signed-off-by: Sandor Yu
Reviewed-by: Robby Cai -
Check return value to fix coverity Issue: 11566404.
Signed-off-by: Sandor Yu
Reviewed-by: Robby Cai -
Delete unused code to fix coverity Issue: 11566405.
Signed-off-by: Sandor Yu
Reviewed-by: Robby Cai -
Delete dead code to fix Coverity Issue: 11566407.
Signed-off-by: Sandor Yu
Reviewed-by: Robby Cai -
Add default access hdcp bus to fix
Coverity Issue: 11566406 Uninitialized scalar variable.Signed-off-by: Sandor Yu
Reviewed-by: Robby Cai -
With mailbox driver support i.MX8 SCU MU channel, we could
use it to avoid trigger interrupts for each TR/RR registers
in one MU, instead, only one RX interrupt for a recv and
one TX interrupt for a send.Signed-off-by: Nitin Garg
Reviewed-by: Dong Aisheng -
This reverts commit 31997c2be9328bfe82fd7484b8532646de4d4965.
This change isn't needed as the new MU binding is efficient and
can handle messages of any sizes.Signed-off-by: Nitin Garg
Reviewed-by: Dong Aisheng -
This reverts commit 175fe6289fcb7e13cb5add2b80cdc0e5e049fb95.
This change isn't needed as the new MU binding is efficient and
can handle messages of any sizes.Signed-off-by: Nitin Garg
Reviewed-by: Dong Aisheng -
The 'dmt' is duplicated by 'drm_mode_find_dmt()' and it
should be explicitly freed after it has been used to avoid
memory leak.This issue is detected by Coverity with CID 1149970.
Signed-off-by: Fancy Fang
Reviewed-by: Robby Cai
21 Jan, 2021
6 commits
-
In case no job rings are available, secure memory structures are not
initialized, since caam_jr_probe()->init_misc_func()->caam_sm_startup()
is not called.
This could happen if all job ring devices bind to the jr uio driver
instead of the caam/jr driver.
Running sm_test in this case will lead to a crash.Add a check to verify that SM has been initialized - if not the tests
will be skipped.Reported-by: Gaurav Jain
Signed-off-by: Horia Geantă
Reviewed-by: Gaurav Jain -
Introduction
===Currently we are facing some limitations in the caam/jr module lifecycle.
There are some discussion in upstream:
Link: https://lore.kernel.org/linux-crypto/20190904023515.7107-13-andrew.smirnov@gmail.com
Link: https://lore.kernel.org/linux-crypto/20191105151353.6522-1-andrew.smirnov@gmail.com
but in the end it all seems to get down to implementations not being able
to gracefully unregister crypto algorithms from crypto API while there are
users / allocated tfms (cra_refcnt > 1).[*] OTOH functionalities in caam/jr that don't interact with crypto API
(like Secure Memory or black keys / blobs generation) don't face this
limitation.Issue at hand
===When unloading the caam_jr module, the .remove callback for the last JR
device exits with -EBUSY (see "Introduction" above) and doesn't perform
the clean-up (crypto algorithms unregistering etc.).One side effect of this is leeding to an oops, which occurs due to a
corruption in the linked list of "misc devices"
(drivers/char/misc.c - misc_list):
1. caam_jr module is unloaded without calling unregister_algs()->
caam_keygen_exit()->misc_deregister() for the last job ring device;
this leaves a dangling entry in the misc_list double-linked list
2. rng_core module is unloaded and calls misc_deregister(); this implies
removing the corresponding entry in the misc_list; while doing this the
dangling entry is accessed - which leads to an oops since the address is
no longer valid (address points to the caam_jr module address space,
but caam_jr has been previously unloaded).Fix this by moving the clean-up of non-crypto related functionalities [*]
before crypto related ones.Fixes: 3af836d4b311 ("MLK-24420-3 crypto: caam - add ioctl calls for black keys and blobs generation")
Signed-off-by: Horia Geantă
Reviewed-by: Gaurav Jain -
In case of long format of qDMA command descriptor, there are one frame
descriptor, three entries in the frame list and two data entries. So the
size of dma_pool_create for these three fields should be the same with
the total size of entries respectively, or the contents may be overwritten
by the next allocated descriptor.Signed-off-by: Guanhua Gao
-
Add HDMI RX kernel defconfig for android.
Change-Id: Ie7ff7ede71d5d8b489ee33fec8202f0d0c6500ef
Signed-off-by: yang.tian -
Remove all usage for vidioc_int_g_chip_ident
in camera sensor driver to meet GKI requirement.Change-Id: Id808f748913257fe9e3422c50ba54d2506f1506f
Signed-off-by: yang.tian -
Revert "MLK-9662 [V4L2 Capture] Revert patch to
re-add support for _G_CHIP_IDENT"This reverts commit 2c0076d850dc595327f50a292e5ca88452b4217c.
Change-Id: Idc2f61d729b9f289d0c91054dc03794a5e8095d4
Signed-off-by: yang.tian
20 Jan, 2021
6 commits
-
This is the 5.10.9 stable release
* tag 'v5.10.9': (153 commits)
Linux 5.10.9
netfilter: nf_nat: Fix memleak in nf_nat_init
netfilter: conntrack: fix reading nf_conntrack_buckets
...Signed-off-by: Jason Liu
-
This is the 5.10.8 stable release
* tag 'v5.10.8': (104 commits)
Linux 5.10.8
tools headers UAPI: Sync linux/fscrypt.h with the kernel sources
drm/panfrost: Remove unused variables in panfrost_job_close()
...Signed-off-by: Jason Liu
-
This is the 5.10.7 stable release
* tag 'v5.10.7': (144 commits)
Linux 5.10.7
scsi: target: Fix XCOPY NAA identifier lookup
rtlwifi: rise completion at the last step of firmware callback
...Signed-off-by: Jason Liu
-
This is the 5.10.6 stable release
* tag 'v5.10.6': (21 commits)
Linux 5.10.6
mwifiex: Fix possible buffer overflows in mwifiex_cmd_802_11_ad_hoc_start
exec: Transform exec_update_mutex into a rw_semaphore
...Signed-off-by: Jason Liu
Conflicts:
drivers/rtc/rtc-pcf2127.c -
Because the dprc related driver need to probe and init before DPU driver probe
and init. The DPU driver cannot work normally when do defer probe before dprc
driver init. This issue is introduced into car related image because of boot
time optimization patch.
The probe order depends on Makefile order. So change the Makefile order to make
dprc driver init before DPU driver init.Error Log as below and it will reboot:
[ 7.781433] [drm] [CRTC:67:crtc-1] dpu_crtc_atomic_enable: wait for safety shdld done timeout
[ 8.805426] [drm] [CRTC:67:crtc-1] dpu_crtc_atomic_enable: wait for content shdld done timeoutChange-Id: Ib8167bcc92531fd6b906ec4039f40d6989ae3c20
Signed-off-by: Zhang Bo -
This is the 5.10.5 stable release
* tag 'v5.10.5': (63 commits)
Linux 5.10.5
device-dax: Fix range release
ext4: avoid s_mb_prefetch to be zero in individual scenarios
...Signed-off-by: Jason Liu
