The following print appears for dmesg on the Tx2 Nx：”[ 0.470284] tegra-pmc c360000.pmc: WARNING: IO pad defaults is supported via pinctrl“

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Hello, everyone:
I’m currently debugging a custom kernel on a Tx2Nx board, and I found the following message when I was looking at the kernel print from dmesg, and I was wondering if this is problematic and what I should do to fix it, and I’m currently using version 32.7.3, 4.9.299-rt191+.
[ 0.470029] tegra-pmc c360000.pmc: scratch reg offset dts data not present
[ 0.470093] tegra-pmc: get_secure_pmc_setting: done secure_pmc=0
[ 0.470106] tegra-pmc: ### PMC reset source: TEGRA_POWER_ON_RESET
[ 0.470108] tegra-pmc: ### PMC reset level: TEGRA_RESET_LEVEL_L0
[ 0.470111] tegra-pmc: ### PMC reset status reg: 0x0
[ 0.470273] padctrl padctrl.0: Pad control driver tegra-pmc-padctrl registered
[ 0.470284] tegra-pmc c360000.pmc: WARNING: IO pad defaults is supported via pinctrl
[ 0.470319] ------------[ cut here ]------------
[ 0.470331] WARNING: CPU: 0 PID: 1 at /home/huanglielie/Jetson/JetsonLinux32.7.3/kernel/nvidia/drivers/padctrl/padctrl-tegra-io-pads.c:247 tegra_io_pads_padctrl_init+0xb4/0x110
[ 0.470333] Modules linked in:

[ 0.470343] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.299-rt191+ #493
[ 0.470346] Hardware name: lanai-3636 (DT)
[ 0.470349] task: ffffffc0f0f18000 task.stack: ffffffc0f0e34000
[ 0.470353] PC is at tegra_io_pads_padctrl_init+0xb4/0x110
[ 0.470356] LR is at tegra_io_pads_padctrl_init+0xb4/0x110
[ 0.470360] pc : [] lr : [] pstate: 40400045
[ 0.470362] sp : ffffffc0f0e379e0
[ 0.470364] x29: ffffffc0f0e379e0 x28: ffffff8009848890
[ 0.470370] x27: ffffff800a1a75f0 x26: ffffff8009008a08
[ 0.470376] x25: 0000000000000000 x24: 0000000000000000
[ 0.470381] x23: ffffff8009f4c000 x22: ffffffc0ef8e0c10
[ 0.470386] x21: ffffffc0efe5c000 x20: ffffffc0efe5d058
[ 0.470391] x19: ffffffc0ef8e0c10 x18: 0000000000000000
[ 0.470396] x17: 0000000000000002 x16: 0000000000000000
[ 0.470401] x15: ffffffffffffffff x14: 6169762064657472
[ 0.470406] x13: 6f70707573207369 x12: 0000000000000000
[ 0.470410] x11: 0000000000000004 x10: 0000000000000089
[ 0.470415] x9 : 57203a636d702e30 x8 : ffffffc0f704494b
[ 0.470420] x7 : 0000000000000000 x6 : 0000000000000001
[ 0.470425] x5 : 0000000000000000 x4 : 0000000000000000
[ 0.470430] x3 : ffffffffffffffff x2 : ffffff8009e93388
[ 0.470434] x1 : ffffffc0f0f18000 x0 : 0000000000000048

[ 0.470441] —[ end trace 0000000000000001 ]—
[ 0.470443] Call trace:
[ 0.470448] [] tegra_io_pads_padctrl_init+0xb4/0x110
[ 0.470453] [] tegra_pmc_probe+0x764/0xc30
[ 0.470460] [] platform_drv_probe+0x60/0xc0
[ 0.470464] [] driver_probe_device+0x29c/0x450
[ 0.470468] [] __device_attach_driver+0xa8/0x148
[ 0.470472] [] bus_for_each_drv+0x58/0xa8
[ 0.470476] [] __device_attach+0xc8/0x158
[ 0.470480] [] device_initial_probe+0x24/0x30
[ 0.470484] [] bus_probe_device+0x9c/0xa8
[ 0.470487] [] device_add+0x3d0/0x5d8
[ 0.470493] [] of_device_add+0x40/0x50
[ 0.470496] [] of_platform_device_create_pdata+0x9c/0x100
[ 0.470499] [] of_platform_bus_create+0x104/0x468
[ 0.470503] [] of_platform_populate+0x8c/0x140
[ 0.470510] [] of_platform_default_populate_init+0x68/0x7c
[ 0.470515] [] do_one_initcall+0x44/0x130
[ 0.470520] [] kernel_init_freeable+0x1e8/0x28c
[ 0.470525] [] kernel_init+0x18/0x108
[ 0.470529] [] ret_from_fork+0x10/0x30

In the meantime, I’ll provide the full log in the attachment.

3

log (2).txt (78.1 KB)

5

What’s do you add for the kernel?

6

We have programmed mcp2515, pca9555, es8388 and other drivers into the kernel, and at the same time, we have adapted the pin functions based on our own carrier board.
At the same time, we use the real-time kernel patch

7

dts.txt (8.9 KB)

8

You may need to narrow down which one cause the problem.

9

I’ve tried it and blocked all the back-added drivers inside the device tree, but it’s still there, what is this related to? I’ll try again.

10

dts.txt (9.0 KB)