Android 14 Protected symbol for driver

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Android 14 Protected symbol for driver

1,117 Views
shiva141
Contributor II

Hi 

We are using imx8mp SOC with imx-android-14.0.0_2.2.0.
We are upgrading from Android 13 to Android 14. 

was able to add the  TPM driver using GKI -imx8mp_gki.fragment and Shareboardconfig.mk to the BSP. 

We observer protected symbol for the TPM driver.Share you input for resolving this in Android 14; same Hardware setup work fine for Android 13 BSP.   

# dmesg | grep tpm
[ 12.845674] tpm: Protected symbol: compat_only_sysfs_link_entry_to_kobj (err -13)
[ 12.854206] tpm: Protected symbol: hash_digest_size (err -13)
[ 12.860854] tpm: Protected symbol: securityfs_create_dir (err -13)
[ 12.867862] tpm: Protected symbol: securityfs_create_file (err -13)
[ 12.874967] tpm: Protected symbol: securityfs_remove (err -13)
[ 12.881627] tpm: Protected symbol: efi_tpm_final_log_size (err -13)
[ 12.891035] tpm: Protected symbol: compat_only_sysfs_link_entry_to_kobj (err -13)
[ 12.899530] tpm: Protected symbol: hash_digest_size (err -13)
[ 12.906097] tpm: Protected symbol: securityfs_create_dir (err -13)
[ 12.913088] tpm: Protected symbol: securityfs_create_file (err -13)
[ 12.920129] tpm: Protected symbol: securityfs_remove (err -13)
 

Please share steps for resolving Protected symbol in Android 14

#Android #imx8mp

 

0 Kudos
Reply
2 Replies

499 Views
Maruti
Contributor III

Dear @shiva141 
Im also facing similar issue while loading RTL ethernet driver as a module in kenel  ini.MX8MQ with Android14

[2025-05-23 13:12:12] 1|iwg33m_8mq:/ # dmesg |grep -i r8169
[2025-05-23 13:12:21] [ 15.742841] r8169: Protected symbol: pcim_set_mwi (err -13)
[2025-05-23 13:12:21] [ 15.749227] r8169: Protected symbol: netdev_sw_irq_coalesce_default_on (err -13)
[2025-05-23 13:12:21] [ 15.757416] r8169: Protected symbol: pci_dev_run_wake (err -13)
[2025-05-23 13:12:21] [ 15.764251] r8169: Protected symbol: pci_reset_bus (err -13)
[2025-05-23 13:12:21] [ 15.770833] r8169: Protected symbol: __devm_mdiobus_register (err -13)
[2025-05-23 13:12:21] [ 15.778358] r8169: Protected symbol: netdev_stats_to_stats64 (err -13)
[2025-05-23 13:12:21] [ 15.785646] r8169: Protected symbol: phy_mac_interrupt (err -13)
[2025-05-23 13:12:21] [ 15.792439] r8169: Protected symbol: phy_resume (err -13)
[2025-05-23 13:12:21] [ 15.798600] r8169: Protected symbol: phy_speed_up (err -13)
[2025-05-23 13:12:21] [ 15.805001] r8169: Protected symbol: pci_status_get_and_clear_errors (err -13)
[2025-05-23 13:12:21] [ 15.813047] r8169: Protected symbol: pcie_set_readrq (err -13)
[2025-05-23 13:12:21] [ 15.819722] r8169: Protected symbol: phy_speed_down (err -13)
[2025-05-23 13:12:21] [ 15.826278] r8169: Protected symbol: phy_get_pause (err -13)

Are you able to resolve this issue ?

Tags (2)
0 Kudos
Reply

1,073 Views
Harvey021
NXP TechSupport
NXP TechSupport

Hi,

Have you tried to upstream symbol to AOSP and then use the boot.img updated by Google? You can refer to the section <9 Generic Kernel Image (GKI) Development> of GUIDE.

If you use boot_imx.img, won't encounter the problem you mentioned.

Can also try to revert this patch in kernel_imx as attached.

 

Regards

Harvey

0 Kudos
Reply