Re: [PATCH v4 12/18] usb: typec: qcom: Add Qualcomm PMIC TCPM support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 24, 2023 at 01:25:14PM +0000, Bryan O'Donoghue wrote:
> On 24/03/2023 10:16, Jianhua Lu wrote:
> 
> so that is correct and expected i.e. VSAFE5V it shouldn't matter to the 
> type-c port controller *where* VBUS comes from only that it is within range.
> 
> Could you run again with an unpowered device and post the printout?
Here is output when plugin usb-c device without power supply:

[   45.714005] qcom,pmic-typec c440000.spmi:pmic@2:typec@1500: vbus vsafe5v fail
[   45.714024] qcom,pmic-typec c440000.spmi:pmic@2:typec@1500: 
qcom_pmic_typec_set_vbus sm_stat output 0x00000099
[   45.714043] qcom,pmic-typec c440000.spmi:pmic@2:typec@1500: 
qcom_pmic_typec_set_vbus misc 0x000000c9
[   45.714060] qcom,pmic-typec c440000.spmi:pmic@2:typec@1500:
qcom_pmic_typec_set_vbus sm_status 0x00000099
[   45.714185] qcom,pmic-typec c440000.spmi:pmic@2:typec@1500:
set_cc: currsrc=1 Rp-1.5-180uA mode EN_SRC_ONLY debounce 1 attached 1 cc=cc2
[   45.719505] qcom,pmic-typec c440000.spmi:pmic@2:typec@1500: Debounce cc complete
> 
I get schematics of same vendor's similar device, it shows usb vbus is
connected to charger pump. It can be the main reason that can't detect vbus, but
I don't know why type-c can work normally.
> ---
> bod



[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux