Hi
Am 26.02.20 um 12:02 schrieb Icenowy Zheng:
>
>
> 于 2020年2月26日 GMT+08:00 下午6:58:43, Thomas Zimmermann 写到:
>> Hi Iceynow,
>>
>> Torsten asked me to merge your patch via drm-misc-next. I'd add the
>> additional cc and fixes tags that Torsten listed. Are you OK with that?
>
> I think this fixe
于 2020年2月26日 GMT+08:00 下午6:58:43, Thomas Zimmermann 写到:
>Hi Iceynow,
>
>Torsten asked me to merge your patch via drm-misc-next. I'd add the
>additional cc and fixes tags that Torsten listed. Are you OK with that?
I think this fixes a driver (and a board) available in 5.6.
Maybe it should enter
Hi
Am 26.02.20 um 12:02 schrieb Icenowy Zheng:
>
>
> 于 2020年2月26日 GMT+08:00 下午6:58:43, Thomas Zimmermann 写到:
>> Hi Iceynow,
>>
>> Torsten asked me to merge your patch via drm-misc-next. I'd add the
>> additional cc and fixes tags that Torsten listed. Are you OK with that?
>
> I think this fixe
Hi Iceynow,
Torsten asked me to merge your patch via drm-misc-next. I'd add the
additional cc and fixes tags that Torsten listed. Are you OK with that?
Best regards
Thomas
Am 22.02.20 um 03:43 schrieb Icenowy Zheng:
>
>
> 于 2020年2月22日 GMT+08:00 上午1:13:28, Torsten Duwe 写到:
>> On Sat, Feb 22, 2
On Sat, Feb 22, 2020 at 10:43:02AM +0800, Icenowy Zheng wrote:
>
>
> 于 2020年2月22日 GMT+08:00 上午1:13:28, Torsten Duwe 写到:
> >On Sat, Feb 22, 2020 at 12:51:27AM +0800, Icenowy Zheng wrote:
> >> Current code tries to store the link rate (in bps, which is a big
> >> number) in a u8, which surely over
Current code tries to store the link rate (in bps, which is a big
number) in a u8, which surely overflow. Then it's converted back to
bandwidth code (which is thus 0) and written to the chip.
The code sometimes works because the chip will automatically fallback to
the lowest possible DP link rate
于 2020年2月22日 GMT+08:00 上午1:13:28, Torsten Duwe 写到:
>On Sat, Feb 22, 2020 at 12:51:27AM +0800, Icenowy Zheng wrote:
>> Current code tries to store the link rate (in bps, which is a big
>> number) in a u8, which surely overflow. Then it's converted back to
>> bandwidth code (which is thus 0) and w
On Sat, Feb 22, 2020 at 12:51:27AM +0800, Icenowy Zheng wrote:
> Current code tries to store the link rate (in bps, which is a big
> number) in a u8, which surely overflow. Then it's converted back to
> bandwidth code (which is thus 0) and written to the chip.
>
> The code sometimes works because
