Re: [PATCH] USB: quirks: Add USB_QUIRK_DISCONNECT_SUSPEND quirk forLenovo A630Z TIO built-in usb-audio card

[Kai-Heng Feng]

> On Nov 19, 2020, at 22:23, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> 
> On Thu, Nov 19, 2020 at 10:12:02PM +0800, Kai-Heng Feng wrote:
>> 
>> 
>>> On Nov 19, 2020, at 21:59, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>>> 
>>> On Thu, Nov 19, 2020 at 09:41:32PM +0800, Kai-Heng Feng wrote:
>>>> Hi penghao,
>>>> 
>>>>> On Nov 19, 2020, at 20:17, 彭浩 <penghao@xxxxxxxxxxxxx> wrote:
>>>>> 
>>>>> root@uos-PC:/sys/bus/usb/devices/usb7# dmesg
>>>>> [ 0.000000] Linux version 4.19.0-6-amd64 (debian-kernel@xxxxxxxxxxxxxxxx) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Uos 4.19.67-11eagle (2020-03-21)
>>>> 
>>>> Thanks for the dmesg. But would it be possible to use mainline kernel enable dynamic debug?
>>>> 
>>>> But anyway, this is not a regular AMD or Intel platform, so I guess we can merge the quirk as is...
>>>> 
>>>> Kai-Heng
>>>> 
>>>>> [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 root=UUID=e5a40c4f-d88e-4a4d-9414-a27892a31be7 ro splash console=ttyS0,115200n8 loglevel=7 DEEPIN_GFXMODE=0,1920x1080,1600x1200,1280x1024,1024x768
>>>>> [ 0.000000] Zhaoxin Linux Patch Version is V3.0.2 
>>>>> [ 0.000000] With Zhaoxin Shanghai CPU patch V2.0.0
>>> 
>>> What do you mean "not a regular"?  This is an x86-variant chip platform,
>>> but what does that have to do with the USB quirk detection?
>> 
>> USB quirk detection should work fine. I was trying to find the root cause, but seeing it's a Zhaoxin CPU, that could be the reason why mainline kernel, which has many USB power management fixes, wasn't used.
>> 
>> penghao, is it possible to boot mainline kernel on Zhaoxin CPU?
> 
> There have been a number of small patches for this type of CPU merged
> over the past months, so I hope a mainline kernel works here :)
> 
> That being said, why would the platform matter for a USB device quirk?

No, it doesn't matter at all. 
Because I am not sure if it can boot a mainline kernel, and the author doesn't know how to enable dynamic debug to let us understand what really happens here.

Kai-Hen

> 
> thanks,
> 
> greg k-h