arm64: dts: rockchip: update LED definitions for ROCK 5A/B #19
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
no functional change ref: kernel/Documentation/devicetree/bindings/leds/common.yaml Signed-off-by: FUKAUMI Naoki <[email protected]>
RadxaStephen
pushed a commit
that referenced
this pull request
Oct 27, 2022
Since the dma iommu iova maybe deinit, the iova procfs lack of a deinit operation, driver will complain such as: [ 3.143475] ------------[ cut here ]------------ [ 3.143501] proc_dir_entry 'iova/ff920000.rkisp1' already registered [ 3.143545] WARNING: CPU: 1 PID: 154 at fs/proc/generic.c:381 proc_register+0x104/0x128 [ 3.143552] Modules linked in: [ 3.143567] CPU: 1 PID: 154 Comm: kworker/u12:2 Not tainted 5.10.66 #19 [ 3.143573] Hardware name: Rockchip RK3399 EVB IND LPDDR4 Board edp (Linux) (DT) [ 3.143586] Workqueue: events_unbound deferred_probe_work_func [ 3.143598] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3.143606] pc : proc_register+0x104/0x128 [ 3.143614] lr : proc_register+0x104/0x128 [ 3.143620] sp : ffffffc0128bb9c0 [ 3.143625] x29: ffffffc0128bb9c0 x28: 0000000000000000 [ 3.143637] x27: ffffffc011cd40e0 x26: 0000000000000000 [ 3.143648] x25: 0000000000000000 x24: ffffff8002aaf690 [ 3.143658] x23: ffffff8002fd14bc x22: ffffffc011b65820 [ 3.143669] x21: ffffff8004050298 x20: ffffff8002aaf600 [ 3.143680] x19: ffffff8002fd1400 x18: 0000000000000000 [ 3.143690] x17: 0000000000000000 x16: 0000000000000000 [ 3.143701] x15: 000000000000000a x14: 6465726574736967 [ 3.143711] x13: 6572207964616572 x12: 6c61202731707369 [ 3.143722] x11: 6b722e3030303032 x10: 3966662f61766f69 [ 3.143733] x9 : ffffffc01009fe50 x8 : 7269645f636f7270 Fixes: 4fe5523 ("iommu/iova: add iova procfs for each dma iommu") Signed-off-by: Jianqun Xu <[email protected]> Change-Id: If8aa00bacd13f72efda266632d06ef6899776f5f
RadxaStephen
pushed a commit
that referenced
this pull request
Oct 28, 2022
no functional change ref: kernel/Documentation/devicetree/bindings/leds/common.yaml Signed-off-by: FUKAUMI Naoki <[email protected]>
stvhay
pushed a commit
to stvhay/kernel
that referenced
this pull request
Feb 1, 2023
no functional change ref: kernel/Documentation/devicetree/bindings/leds/common.yaml Signed-off-by: FUKAUMI Naoki <[email protected]>
stvhay
pushed a commit
to stvhay/kernel
that referenced
this pull request
Feb 12, 2023
no functional change ref: kernel/Documentation/devicetree/bindings/leds/common.yaml Signed-off-by: FUKAUMI Naoki <[email protected]>
stvhay
pushed a commit
to stvhay/kernel
that referenced
this pull request
Feb 26, 2023
no functional change ref: kernel/Documentation/devicetree/bindings/leds/common.yaml Signed-off-by: FUKAUMI Naoki <[email protected]>
RadxaStephen
pushed a commit
to RadxaStephen/kernel
that referenced
this pull request
Mar 3, 2023
no functional change ref: kernel/Documentation/devicetree/bindings/leds/common.yaml Signed-off-by: FUKAUMI Naoki <[email protected]>
RadxaStephen
pushed a commit
that referenced
this pull request
Jul 3, 2023
no functional change ref: kernel/Documentation/devicetree/bindings/leds/common.yaml Signed-off-by: FUKAUMI Naoki <[email protected]>
RadxaStephen
pushed a commit
that referenced
this pull request
Aug 3, 2024
[ Upstream commit afadb04 ] Do what is done in other DMA-enabled MMC host drivers (cf. host/mmci.c) and limit the maximum segment size based on the DMA engine's capabilities. This is needed to avoid warnings like the following with CONFIG_DMA_API_DEBUG=y. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 21 at kernel/dma/debug.c:1162 debug_dma_map_sg+0x2f4/0x39c DMA-API: jz4780-dma 13420000.dma-controller: mapping sg segment longer than device claims to support [len=98304] [max=65536] CPU: 0 PID: 21 Comm: kworker/0:1H Not tainted 5.18.0-rc1 #19 Workqueue: kblockd blk_mq_run_work_fn Stack : 81575aec 00000004 80620000 80620000 80620000 805e7358 00000009 801537ac 814c832c 806276e3 806e34b4 80620000 81575aec 00000001 81575ab8 09291444 00000000 00000000 805e7358 81575958 ffffffea 8157596c 00000000 636f6c62 6220646b 80387a70 0000000f 6d5f6b6c 80620000 00000000 81575ba4 00000009 805e170c 80896640 00000001 00010000 00000000 00000000 00006098 806e0000 ... Call Trace: [<80107670>] show_stack+0x84/0x120 [<80528cd8>] __warn+0xb8/0xec [<80528d78>] warn_slowpath_fmt+0x6c/0xb8 [<8016f1d4>] debug_dma_map_sg+0x2f4/0x39c [<80169d4c>] __dma_map_sg_attrs+0xf0/0x118 [<8016a27c>] dma_map_sg_attrs+0x14/0x28 [<804f66b4>] jz4740_mmc_prepare_dma_data+0x74/0xa4 [<804f6714>] jz4740_mmc_pre_request+0x30/0x54 [<804f4ff4>] mmc_blk_mq_issue_rq+0x6e0/0x7bc [<804f5590>] mmc_mq_queue_rq+0x220/0x2d4 [<8038b2c0>] blk_mq_dispatch_rq_list+0x480/0x664 [<80391040>] blk_mq_do_dispatch_sched+0x2dc/0x370 [<80391468>] __blk_mq_sched_dispatch_requests+0xec/0x164 [<80391540>] blk_mq_sched_dispatch_requests+0x44/0x94 [<80387900>] __blk_mq_run_hw_queue+0xb0/0xcc [<80134c14>] process_one_work+0x1b8/0x264 [<80134ff8>] worker_thread+0x2ec/0x3b8 [<8013b13c>] kthread+0x104/0x10c [<80101dcc>] ret_from_kernel_thread+0x14/0x1c ---[ end trace 0000000000000000 ]--- Signed-off-by: Aidan MacDonald <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Ulf Hansson <[email protected]> Signed-off-by: Sasha Levin <[email protected]>
RadxaStephen
pushed a commit
that referenced
this pull request
Aug 3, 2024
[ Upstream commit 12025ab ] When setting bootparams="trace_event=initcall:initcall_start tp_printk=1" in the cmdline, the output_printk() was called, and the spin_lock_irqsave() was called in the atomic and irq disable interrupt context suitation. On the PREEMPT_RT kernel, these locks are replaced with sleepable rt-spinlock, so the stack calltrace will be triggered. Fix it by raw_spin_lock_irqsave when PREEMPT_RT and "trace_event=initcall:initcall_start tp_printk=1" enabled. BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0 preempt_count: 2, expected: 0 RCU nest depth: 0, expected: 0 Preemption disabled at: [<ffffffff8992303e>] try_to_wake_up+0x7e/0xba0 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.17.1-rt17+ #19 34c5812404187a875f32bee7977f7367f9679ea7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x60/0x8c dump_stack+0x10/0x12 __might_resched.cold+0x11d/0x155 rt_spin_lock+0x40/0x70 trace_event_buffer_commit+0x2fa/0x4c0 ? map_vsyscall+0x93/0x93 trace_event_raw_event_initcall_start+0xbe/0x110 ? perf_trace_initcall_finish+0x210/0x210 ? probe_sched_wakeup+0x34/0x40 ? ttwu_do_wakeup+0xda/0x310 ? trace_hardirqs_on+0x35/0x170 ? map_vsyscall+0x93/0x93 do_one_initcall+0x217/0x3c0 ? trace_event_raw_event_initcall_level+0x170/0x170 ? push_cpu_stop+0x400/0x400 ? cblist_init_generic+0x241/0x290 kernel_init_freeable+0x1ac/0x347 ? _raw_spin_unlock_irq+0x65/0x80 ? rest_init+0xf0/0xf0 kernel_init+0x1e/0x150 ret_from_fork+0x22/0x30 </TASK> Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Jun Miao <[email protected]> Signed-off-by: Steven Rostedt (Google) <[email protected]> Signed-off-by: Sasha Levin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.