Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IIC4下面挂RX8010SJ 一直匹配不上 #10

Open
zwjin1210 opened this issue May 30, 2024 · 2 comments
Open

IIC4下面挂RX8010SJ 一直匹配不上 #10

zwjin1210 opened this issue May 30, 2024 · 2 comments

Comments

@zwjin1210
Copy link

zwjin1210 commented May 30, 2024 •
edited
Loading

No description provided.

@ychuang3
Copy link
Contributor 

adc0 {
	pinctrl_adc0: adc0grp {
		nuvoton,pins =
			<SYS_GPB_MFPH_PB12MFP_ADC0_CH4   &pcfg_default>,
			<SYS_GPB_MFPH_PB13MFP_ADC0_CH5   &pcfg_default>,
			<SYS_GPB_MFPH_PB14MFP_ADC0_CH6   &pcfg_default>,
			<SYS_GPB_MFPH_PB15MFP_ADC0_CH7   &pcfg_default>;
	};
};

請先確認 PB.14 與 PB.15 是否有 multi-function pin 衝突
PB.14, PB.15 default 被 ADC touch 使用

devmem 0x4046008c 32

==> 是甚麼值?

@zwjin1210
Copy link
Author

好了 是我CLK上没有接上拉电阻

jserv pushed a commit to jserv/linux-ma35d1 that referenced this issue Sep 23, 2024
@lclaudio
drm/i915: disable tracing on -RT
f87623d 
Luca Abeni reported this:
| BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003
| CPU: 1 PID: 15203 Comm: kworker/u8:2 Not tainted 4.19.1-rt3 OpenNuvoton#10
| Call Trace:
|  rt_spin_lock+0x3f/0x50
|  gen6_read32+0x45/0x1d0 [i915]
|  g4x_get_vblank_counter+0x36/0x40 [i915]
|  trace_event_raw_event_i915_pipe_update_start+0x7d/0xf0 [i915]

The tracing events use trace_i915_pipe_update_start() among other events
use functions acquire spin locks. A few trace points use
intel_get_crtc_scanline(), others use ->get_vblank_counter() wich also
might acquire a sleeping lock.

Based on this I don't see any other way than disable trace points on RT.

Cc: [email protected]
Reported-by: Luca Abeni <[email protected]>
Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
jserv pushed a commit to jserv/linux-ma35d1 that referenced this issue Sep 23, 2024
@lclaudio
drm/i915: disable tracing on -RT
26be632 
Luca Abeni reported this:
| BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003
| CPU: 1 PID: 15203 Comm: kworker/u8:2 Not tainted 4.19.1-rt3 OpenNuvoton#10
| Call Trace:
|  rt_spin_lock+0x3f/0x50
|  gen6_read32+0x45/0x1d0 [i915]
|  g4x_get_vblank_counter+0x36/0x40 [i915]
|  trace_event_raw_event_i915_pipe_update_start+0x7d/0xf0 [i915]

The tracing events use trace_i915_pipe_update_start() among other events
use functions acquire spin locks. A few trace points use
intel_get_crtc_scanline(), others use ->get_vblank_counter() wich also
might acquire a sleeping lock.

Based on this I don't see any other way than disable trace points on RT.

Cc: [email protected]
Reported-by: Luca Abeni <[email protected]>
Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
jserv pushed a commit to jserv/linux-ma35d1 that referenced this issue Nov 15, 2024
@jserv
drm/i915: disable tracing on -RT
4ccf77b 
Luca Abeni reported this:
| BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003
| CPU: 1 PID: 15203 Comm: kworker/u8:2 Not tainted 4.19.1-rt3 OpenNuvoton#10
| Call Trace:
|  rt_spin_lock+0x3f/0x50
|  gen6_read32+0x45/0x1d0 [i915]
|  g4x_get_vblank_counter+0x36/0x40 [i915]
|  trace_event_raw_event_i915_pipe_update_start+0x7d/0xf0 [i915]

The tracing events use trace_i915_pipe_update_start() among other events
use functions acquire spin locks. A few trace points use
intel_get_crtc_scanline(), others use ->get_vblank_counter() wich also
might acquire a sleeping lock.

Based on this I don't see any other way than disable trace points on RT.

Cc: [email protected]
Reported-by: Luca Abeni <[email protected]>
Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
jserv pushed a commit to jserv/linux-ma35d1 that referenced this issue Nov 27, 2024
@jserv
drm/i915: disable tracing on -RT
e06a97a 
Luca Abeni reported this:
| BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003
| CPU: 1 PID: 15203 Comm: kworker/u8:2 Not tainted 4.19.1-rt3 OpenNuvoton#10
| Call Trace:
|  rt_spin_lock+0x3f/0x50
|  gen6_read32+0x45/0x1d0 [i915]
|  g4x_get_vblank_counter+0x36/0x40 [i915]
|  trace_event_raw_event_i915_pipe_update_start+0x7d/0xf0 [i915]

The tracing events use trace_i915_pipe_update_start() among other events
use functions acquire spin locks. A few trace points use
intel_get_crtc_scanline(), others use ->get_vblank_counter() wich also
might acquire a sleeping lock.

Based on this I don't see any other way than disable trace points on RT.

Cc: [email protected]
Reported-by: Luca Abeni <[email protected]>
Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
jserv pushed a commit to jserv/linux-ma35d1 that referenced this issue Nov 27, 2024
@jserv
drm/i915: disable tracing on -RT
46ca476 
Luca Abeni reported this:
| BUG: scheduling while atomic: kworker/u8:2/15203/0x00000003
| CPU: 1 PID: 15203 Comm: kworker/u8:2 Not tainted 4.19.1-rt3 OpenNuvoton#10
| Call Trace:
|  rt_spin_lock+0x3f/0x50
|  gen6_read32+0x45/0x1d0 [i915]
|  g4x_get_vblank_counter+0x36/0x40 [i915]
|  trace_event_raw_event_i915_pipe_update_start+0x7d/0xf0 [i915]

The tracing events use trace_i915_pipe_update_start() among other events
use functions acquire spin locks. A few trace points use
intel_get_crtc_scanline(), others use ->get_vblank_counter() wich also
might acquire a sleeping lock.

Based on this I don't see any other way than disable trace points on RT.

Cc: [email protected]
Reported-by: Luca Abeni <[email protected]>
Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zwjin1210 @ychuang3