st to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/intel-lab-lkp/linux/commits/Jos-Roberto-de-Souza/drm-i915-Drop-has_llc-from-device-info/20220507-213117
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: i386-allye
st to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/intel-lab-lkp/linux/commits/Jos-Roberto-de-Souza/drm-i915-Drop-has_llc-from-device-info/20220507-213117
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: i386-
Hello Lucas,
On 5/7/22 18:20, Lucas De Marchi wrote:
> On Fri, May 06, 2022 at 03:22:25PM +0200, Javier Martinez Canillas wrote:
>> Commit d258d00fb9c7 ("fbdev: efifb: Cleanup fb_info in .fb_destroy rather
>> than .remove") attempted to fix a use-after-free error due driver freeing
>> the fb_info
On Fri, May 06, 2022 at 03:22:25PM +0200, Javier Martinez Canillas wrote:
Commit d258d00fb9c7 ("fbdev: efifb: Cleanup fb_info in .fb_destroy rather
than .remove") attempted to fix a use-after-free error due driver freeing
the fb_info in the .remove handler instead of doing it in .fb_destroy.
But
== Series Details ==
Series: series starting with [01/16] drm/i915: Drop has_llc from device info
URL : https://patchwork.freedesktop.org/series/103718/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11620_full -> Patchwork_103718v1_full
== Series Details ==
Series: series starting with [01/16] drm/i915: Drop has_llc from device info
URL : https://patchwork.freedesktop.org/series/103718/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11620 -> Patchwork_103718v1
==
== Series Details ==
Series: series starting with [01/16] drm/i915: Drop has_llc from device info
URL : https://patchwork.freedesktop.org/series/103718/
State : warning
== Summary ==
Error: dim checkpatch failed
749bad5dad9c drm/i915: Drop has_llc from device info
-:48: CHECK:MACRO_ARG_REUSE:
== Series Details ==
Series: series starting with [01/16] drm/i915: Drop has_llc from device info
URL : https://patchwork.freedesktop.org/series/103718/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
No need to have this parameter in intel_device_info struct
as this feature is supported all platforms with graphics version 8 or
newer.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check the macro an
No need to have this parameter in intel_device_info struct
as this feature is supported by Broadwell, Haswell all platforms with
display version 9 or newer.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on
No need to have this parameter in intel_device_info struct
as this feature was only supported in Ivybridge and Haswell.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check the macro and compare with p
No need to have this parameter in intel_device_info struct
as this feature is supported in Haswell, Valleyview and all platforms
with graphics version 8 or newer.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to re
No need to have this parameter in intel_device_info struct
as all discrete platforms supports this feature.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check the macro and compare with platform bein
No need to have this parameter in intel_device_info struct
as all platforms with graphics version 12 or newer has this feature.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check the macro and compar
No need to have this parameter in intel_device_info struct
as all integrated platforms with graphics version 12 or newer supports
this feature.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check the
No need to have this parameter in intel_device_info struct
as all platforms with graphics version 8 or newer have software
support for this feature.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check
No need to have this parameter in intel_device_info struct
as all platforms with graphics version 12.55 or newer has this
feature.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check the macro and com
No need to have this parameter in intel_device_info struct as this
tiling format is supported in platforms with graphics 12.50 or
newer what was missed in xehpsdv.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to r
No need to have this parameter in intel_device_info struct
as this feature was only supported by display 9, 10 and 11, tigerlake
and DG1, no newer platforms will have this feature.
While at it also moving it to intel_psr.c as this is the only place
were it is used.
As a side effect of the of remo
Only four platforms ever support this feature so we can elimitate
this from device info and use platform checks instead.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check the macro and compare with
No need to have this parameter in intel_device_info struct
as it was only supported in sandybridge and ivybridge platforms.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check the macro and compare wi
No need to have this parameter in intel_device_info struct
as all platforms with display version 9 or newer supports this
feature.
As a side effect of the of removal this flag, it will not be printed
in dmesg during driver load anymore and developers will have to rely
on to check the macro and com
Commit 99510e1afb48 ("drm/i915: Disable DSB usage for now") disabled
DSB for all display 12 platforms because it is not properly
programming gamma LUT but left display 13 platforms with it enabled
what I believe is not intentional.
kms_color@pipe-a-gamma test is still passing on TGL with DSB enabl
This feature is supported in graphics version 6 and newer in all
integrated GPUs not including VLC and CHV, so we can drop this flag
for a not so complicated macro check.
For this flag we were lucky as XE_HP_FEATURES was setting it to true
while DGFX_FEATURES was setting it to false and xehpsdv an
On Fri, 06 May 2022, Ville Syrjälä wrote:
> On Fri, May 06, 2022 at 01:10:24PM +0300, Jani Nikula wrote:
>> +int drm_edid_to_sad(const struct edid *edid, struct cea_sad **sads)
>> +{
>> +struct drm_edid drm_edid = {
>> +.edid = edid,
>> +.size = edid_size(edid),
>> +
25 matches
Mail list logo
