This is the question for PINMUX setting for bluedroid_pm pins if I want to disable bluedroid_pm. I originally posted my question in the topic of other user here:
But @WayneWWW told me to file a new topic for my issue. Therefore, I am creating a new topic here.
I am designing my own carrier for Xavier, I want to disable bluedroid_pm. I have commented out the
bluedroid_pm node in device-tree. But how should I set the pinmux for reset-gpio, host-wake-gpio, and ext-wake-gpio in pinmux table? (Note that I copied the devkit schematic for M.2 E key exactly which means those bluedroid_pm pins are copied from devkit schematic as well.)
- reset-gpio connects to W_DISABLE2# (pin 54) of M.2 E. I think it is for enabling BT function of wireless chip on that M.2 E, correct? So, I should set pinmux in GPIO output “drive 1” state, correct?
- ext-wake-gpio connects to VENDOR_DEFINED (pin 38) of M.2 E. Is it for Xavier to wake the wireless chip? Should I set pinmux in GPIO output “drive 1” state? Note that the current Xavier devkit pinmux table already sets it to output “drive 1” state.
- host-wake-gpio connects to UART_WAKE# (pin 20) of M.2 E. Is it for wireless chip to wake Xavier from deep sleep mode? Should I set pinmux in GPIO input with Pull-up state?
- Are most of M.2 E wireless chips compatible with this pin setting on M.2 E? Especially, for ext-wake where it is connected to VENDOR_DEFINED pin on M.2 E, which seems has high chance of vendor dependency.
- I briefly went thru
kernel/nvidia/drivers/misc/bluedroid_pm.cdriver. Is it in standard upstream linux kernel? Or it is something specific in L4T kernel? I couldn’t find the bluedroid_pm driver in upstream kernel. I even couldn’t find the device-tree binding in upstream kernel.