>-Original Message-
>From: Liu, Yi L
>Sent: Saturday, May 13, 2023 9:28 PM
>To: alex.william...@redhat.com; j...@nvidia.com; Tian, Kevin
>
>Cc: j...@8bytes.org; robin.mur...@arm.com; coh...@redhat.com;
>eric.au...@redhat.com; nicol...@nvidia.com; k...@vger.kernel.org;
>mjros...@linux.ibm
On 22.05.2023 22:23, Matt Roper wrote:
Rather than embeddeding the display's device info within the main device
info structure, just provide a pointer to the display-specific
structure. This is in preparation for moving the display device info
definitions into the display code itself and for eve
On 22.05.2023 22:23, Matt Roper wrote:
Move the runtime info specific to display into display-specific
structures as has already been done with the constant display info.
v2:
- Rename __runtime to __runtime_defaults for more clarity on the
purpose. (Andrzej)
- Move introduction of DISPL
On 22.05.2023 22:23, Matt Roper wrote:
Rather than selecting the display IP and feature flags at the same time
the general PCI probing happens, move this step into the display code
itself so that it can be more easily re-used outside of i915 (i.e., by
the Xe driver).
v2:
- Make intel_display_d
On 22.05.2023 22:23, Matt Roper wrote:
For platforms with GMD_ID support (i.e., everything MTL and beyond),
identification of the display IP present should be based on the contents
of the GMD_ID register rather than a PCI devid match.
Note that since GMD_ID readout requires access to the PCI BAR
On 22.05.2023 22:23, Matt Roper wrote:
It makes sense to keep the display feature test macros centralized
within the display code.
Signed-off-by: Matt Roper
Reviewed-by: Andrzej Hajda
Regards
Andrzej
---
.../drm/i915/display/intel_display_device.h | 40 +
drivers/gpu/drm/i
== Series Details ==
Series: HDCP Cleanup (rev3)
URL : https://patchwork.freedesktop.org/series/117938/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13175_full -> Patchwork_117938v3_full
Summary
---
**SUCCESS**
N
== Series Details ==
Series: drm/i915/perf: Clear out entire reports after reading if not power of 2
size (rev2)
URL : https://patchwork.freedesktop.org/series/118151/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13175 -> Patchwork_118151v2
==
Hi Fei,
finally... pushed in drm-intel-gt-next! :)
Andi
On Thu, May 18, 2023 at 10:11:01PM -0700, fei.y...@intel.com wrote:
> From: Fei Yang
>
> This series introduce a new extension for GEM_CREATE,
> 1. end support for set caching ioctl [PATCH 1/2]
> 2. add set_pat extension for gem_create [P
On Tue, 23 May 2023, Vinod Govindapillai wrote:
> From MTL onwwards, pcode locks the QGV point based on peak BW of
> the intended QGV point passed by the driver. So the peak BW
> calculation must match the value expected by the pcode. Update
> the calculations as per the Bspec.
>
> v2: use DIV_ROU
On Tue, May 16, 2023 at 02:40:27PM +0300, Ville Syrjälä wrote:
> On Tue, May 16, 2023 at 01:43:44PM +0300, Lisovskiy, Stanislav wrote:
> > On Fri, May 12, 2023 at 11:54:16AM +0530, Ankit Nautiyal wrote:
> > > Currently, we take the max lane, rate and pipe bpp, to get the maximum
> > > compressed bp
On Tue, 23 May 2023, Vinod Govindapillai wrote:
> Extract intel_bw_check_qgv_points() from intel_bw_atomic_check
> to facilitate future platform variations in handling SAGV
> configurations.
>
> Signed-off-by: Vinod Govindapillai
> Reviewed-by: Stanislav Lisovskiy
> ---
> drivers/gpu/drm/i915/d
On 23/05/2023 00:09, Andi Shyti wrote:
Hi Tvrtko,
On Mon, May 22, 2023 at 12:59:27PM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
In preparation for exposing via sysfs add helpers for managing rps
thresholds.
v2:
* Force sw and hw re-programming on threshold change.
Signed-off-by:
On 15/05/2023 15:14, Rob Clark wrote:
On Mon, May 15, 2023 at 6:36 AM Tvrtko Ursulin
wrote:
From: Tvrtko Ursulin
Rob,
I thought maybe when you add memory stats the same field order like top(1)
would feel more natural? That is client name comes last and is left justified.
All other stats t
On Wed, 17 May 2023, Jani Nikula wrote:
> On Wed, 17 May 2023, Krzysztof Kozlowski
> wrote:
>> On 17/05/2023 11:28, Jani Nikula wrote:
>>> On Thu, 11 May 2023, Krzysztof Kozlowski
>>> wrote:
Statically allocated array of pointers to hwmon_channel_info can be made
const for safety.
>>
On Thu, 18 May 2023, Arun R Murthy wrote:
> API are added to enable/disable histogram. Upon generation of histogram
> interrupt its notified to the usespace. User can then use this histogram
> and generate a LUT which is then fed back to the enahancement block.
> Histogram is an image statistics b
On Thu, 18 May 2023, Arun R Murthy wrote:
> With the enablement of global histogram, upon generation of histogram,
> an interrupt is triggered. This patch handles the irq.
>
> Reviewed-by: Uma Shankar
> Signed-off-by: Arun R Murthy
This needs a rebase I think.
> ---
> drivers/gpu/drm/i915/i91
On Thu, 18 May 2023, Arun R Murthy wrote:
> For global histogram the panel should be edp and should have pwm based
> backlight controller. Flags are updated accordingly.
>
> Reviewed-by: Uma Shankar
> Signed-off-by: Arun R Murthy
> ---
> drivers/gpu/drm/i915/display/intel_modeset_setup.c | 12 +
Move rc_param calculation for native_420 into calculate_rc_parameter.
Cc: Ankit Nautiyal
Signed-off-by: Suraj Kandpal
---
drivers/gpu/drm/i915/display/intel_vdsc.c | 28 +--
1 file changed, 16 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_vd
Some rc_range_parameter calculations were missed for YCBCR420,
add them to calculate_rc_param()
Cc: Vandita Kulkarni
Cc: Ankit Nautiyal
Cc: Uma Shankar
Signed-off-by: Suraj Kandpal
---
drivers/gpu/drm/i915/display/intel_vdsc.c | 139 --
1 file changed, 102 insertions(+), 3
Calculations for YUV420 were missing from calculate_rc_param,
add them be in line with DSC 1.2a specs.
Signed-off-by: Suraj Kandpal
Suraj Kandpal (2):
drm/i915/dsc: Move rc param calculation for native_420
drm/i915/dsc: Add rc_range_parameter calculation for YCBCR420
drivers/gpu/drm/i915/d
== Series Details ==
Series: drm/i915/perf: Clear out entire reports after reading if not power of 2
size (rev2)
URL : https://patchwork.freedesktop.org/series/118151/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13175_full -> Patchwork_118151v2_full
== Series Details ==
Series: drm/i915/color: register & get config abstractions (rev2)
URL : https://patchwork.freedesktop.org/series/117875/
State : warning
== Summary ==
Error: dim checkpatch failed
930bc469b869 drm/i915/regs: split out intel_color_regs.h
Traceback (most recent call last):
== Series Details ==
Series: drm/i915/color: register & get config abstractions (rev2)
URL : https://patchwork.freedesktop.org/series/117875/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+./arch/x86/inclu
On 2023-05-15 at 14:36:29 +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Move client name to be the right most field which visually aligns better
> with top(1) and prepares for inserting memory usage fields somewhere in
> the middle.
>
> Signed-off-by: Tvrtko Ursulin
> Cc: Rob Clark
From: Tvrtko Ursulin
Exercise a bunch of up and down rps thresholds to verify hardware
is happy with them all.
To limit the overall runtime relies on probability and number of runs
to approach complete coverage.
Signed-off-by: Tvrtko Ursulin
Cc: Rodrigo Vivi
---
tests/i915/i915_pm_rps.c | 23
On 2023-05-15 at 14:36:30 +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Move client name to be the right most field which visually aligns better
> with top(1) and prepares for inserting memory usage fields somewhere in
> the middle.
>
> Signed-off-by: Tvrtko Ursulin
> Cc: Rob Clark
Hi Tvrtko,
> > > + /* Force reset. */
> > > + rps->last_freq = -1;
> > > + mutex_lock(&rps->power.mutex);
> > > + rps->power.mode = -1;
> > > + mutex_unlock(&rps->power.mutex);
> > > +
> > > + intel_rps_set(rps, clamp(rps->cur_freq,
> > > + rps->min_freq_softlimit,
> > > +
On Tue, 23 May 2023, Suraj Kandpal wrote:
> Move rc_param calculation for native_420 into calculate_rc_parameter.
Why?
Please always answer the question "why" in the commit message, even if
briefly.
>
> Cc: Ankit Nautiyal
> Signed-off-by: Suraj Kandpal
> ---
> drivers/gpu/drm/i915/display/in
On Mon, 22 May 2023, "Lisovskiy, Stanislav"
wrote:
> On Fri, May 12, 2023 at 02:17:50AM +0300, Vinod Govindapillai wrote:
>> While configuring pmdemand parameters, there could be
>> intel_get_crtc_new_encoder call where encoders could be 0. To avoid
>> invoking drm_warn in such cases, use a param
Hi,
> -Original Message-
> From: Intel-gfx On Behalf Of Jani
> Nikula
> Sent: Tuesday, May 23, 2023 2:49 PM
> To: Lisovskiy, Stanislav ; Govindapillai, Vinod
>
> Cc: intel-gfx@lists.freedesktop.org; Syrjala, Ville
> Subject: Re: [Intel-gfx] [PATCH v5 8/8] drm/i915/display: provision to
strlcpy() reads the entire source buffer first.
This read may exceed the destination size limit.
This is both inefficient and can lead to linear read
overflows if a source string is not NUL-terminated [1].
In an effort to remove strlcpy() completely [2], replace
strlcpy() here with strscpy().
No re
On Tue, 2023-05-23 at 12:01 +0300, Jani Nikula wrote:
> On Tue, 23 May 2023, Vinod Govindapillai
> wrote:
> > From MTL onwwards, pcode locks the QGV point based on peak BW of
> > the intended QGV point passed by the driver. So the peak BW
> > calculation must match the value expected by the pcode
On Mon, 22 May 2023, Matt Roper wrote:
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 9612c2ac4b00..7a8a12d12790 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -205,6 +205,7 @@ struct drm_i915_private {
>
>
On Mon, 22 May 2023, Matt Roper wrote:
> diff --git a/drivers/gpu/drm/i915/intel_device_info.c
> b/drivers/gpu/drm/i915/intel_device_info.c
> index 4e23be2995bf..d0bf626d0360 100644
> --- a/drivers/gpu/drm/i915/intel_device_info.c
> +++ b/drivers/gpu/drm/i915/intel_device_info.c
> @@ -138,7 +138,
clang with W=1 reports
drivers/gpu/drm/i915/display/intel_display.c:6012:3: error: unannotated
fall-through between switch labels [-Werror,-Wimplicit-fallthrough]
case I915_FORMAT_MOD_X_TILED:
^
Only one case and the default does anything in this switch, so it sho
On Mon, 22 May 2023, Matt Roper wrote:
> +static const struct intel_display_device_info xe_lpdp_display = {
> + XE_LPD_FEATURES,
> + .has_cdclk_crawl = 1,
> + .has_cdclk_squash = 1,
> +
> + .__runtime_defaults.ip.ver = 14,
> + .__runtime_defaults.fbc_mask = BIT(INTEL_FBC_A) | B
On Mon, 22 May 2023, Matt Roper wrote:
> For platforms with GMD_ID support (i.e., everything MTL and beyond),
> identification of the display IP present should be based on the contents
> of the GMD_ID register rather than a PCI devid match.
>
> Note that since GMD_ID readout requires access to the
On Tue, 2023-05-23 at 12:05 +0300, Jani Nikula wrote:
> On Tue, 23 May 2023, Vinod Govindapillai
> wrote:
> > Extract intel_bw_check_qgv_points() from intel_bw_atomic_check
> > to facilitate future platform variations in handling SAGV
> > configurations.
> >
> > Signed-off-by: Vinod Govindapilla
On Mon, 22 May 2023, Matt Roper wrote:
> Since i915's display code will soon be shared by two DRM drivers (i915
> and Xe), it makes sense for the display code itself to be responsible
> for recognizing the platform it's running on rather than relying on the
> making the top-level DRM driver handle
On Tue, 23 May 2023, "Govindapillai, Vinod"
wrote:
> On Tue, 2023-05-23 at 12:01 +0300, Jani Nikula wrote:
>> On Tue, 23 May 2023, Vinod Govindapillai
>> wrote:
>> > From MTL onwwards, pcode locks the QGV point based on peak BW of
>> > the intended QGV point passed by the driver. So the peak BW
On Tue, 23 May 2023, Tom Rix wrote:
> clang with W=1 reports
> drivers/gpu/drm/i915/display/intel_display.c:6012:3: error: unannotated
> fall-through between switch labels [-Werror,-Wimplicit-fallthrough]
> case I915_FORMAT_MOD_X_TILED:
> ^
>
> Only one case and t
On 22/05/2023 23:17, Ashutosh Dixit wrote:
Clearing out report id and timestamp as means to detect unlanded reports
only works if report size is power of 2. That is, only when report size is
a sub-multiple of the OA buffer size can we be certain that reports will
land at the same place each time
On Tue, May 23, 2023 at 04:02:46PM +0300, Jani Nikula wrote:
> On Mon, 22 May 2023, Matt Roper wrote:
> > For platforms with GMD_ID support (i.e., everything MTL and beyond),
> > identification of the display IP present should be based on the contents
> > of the GMD_ID register rather than a PCI d
Quoting Vinod Govindapillai (2023-05-22 20:07:59-03:00)
>From: Mika Kahola
>
>MTL introduces a new way to instruct the PUnit with
>power and bandwidth requirements of DE. Add the functionality
>to program the registers and handle waits using interrupts.
>The current wait time for timeouts is progr
On 5/22/2023 5:13 PM, Teres Alexis, Alan Previn wrote:
On Fri, 2023-05-05 at 09:04 -0700, Ceraolo Spurio, Daniele wrote:
A few fixes/updates are required around the GSC memory allocation and it
is easier to do them all at the same time. The changes are as follows:
alan:snip
@@ -109,38 +11
Ashutosh Dixit (2):
drm/i915/pmu: Turn off the timer to sample frequencies when GT is
parked
drm/i915/pmu: Make PMU sample array two-dimensional
drivers/gpu/drm/i915/i915_pmu.c | 72 +++--
drivers/gpu/drm/i915/i915_pmu.h | 2 +-
2 files changed, 24 insertions(
pmu_needs_timer() keeps the timer running even when GT is parked,
ostensibly to sample requested/actual frequencies. However
frequency_sample() has the following:
/* Report 0/0 (actual/requested) frequency while parked. */
if (!intel_gt_pm_get_if_awake(gt))
return;
No functional changes but we can remove some unsightly index computation
and read/write functions if we convert the PMU sample array from a
one-dimensional to a two-dimensional array.
Suggested-by: Tvrtko Ursulin
Signed-off-by: Ashutosh Dixit
---
drivers/gpu/drm/i915/i915_pmu.c | 60 ++-
From: Tvrtko Ursulin
Need to reset aggregated counters before adding to them otherwise numbers
will grow endlessly.
Signed-off-by: Tvrtko Ursulin
Fixes: 3dadeff69d4a ("intel_gpu_top: Switch pmu_counter to use aggregated
values")
Cc: Umesh Nerlige Ramappa
Cc: Ashutosh Dixit
---
tools/intel_g
On Fri, 12 May 2023 01:59:08 -0700, Tvrtko Ursulin wrote:
>
Hi Tvrtko,
> On 12/05/2023 02:53, Ashutosh Dixit wrote:
> > pmu_needs_timer() keeps the timer running even when GT is parked,
> > ostensibly to sample requested/actual frequencies. However
> > frequency_sample() has the following:
> >
>
On Tue, 23 May 2023 01:20:17 +
"Liu, Yi L" wrote:
> > From: Alex Williamson
> > Sent: Tuesday, May 23, 2023 6:16 AM
> >
> > On Sat, 13 May 2023 06:28:24 -0700
> > Yi Liu wrote:
> >
> > > This adds ioctl for userspace to attach device cdev fd to and detach
> > > from IOAS/hw_pagetable ma
On Tue, 23 May 2023 01:41:36 +
"Liu, Yi L" wrote:
> > From: Alex Williamson
> > Sent: Tuesday, May 23, 2023 6:01 AM
> >
> > On Sat, 13 May 2023 06:28:23 -0700
> > Yi Liu wrote:
> >
> > > This adds ioctl for userspace to bind device cdev fd to iommufd.
> > >
> > > VFIO_DEVICE_BIND_IO
== Series Details ==
Series: drm/i915/pmu: couple of cleanups
URL : https://patchwork.freedesktop.org/series/118225/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
pushed to drm-intel-next with a minor fix (s/References:/Closes:)
On 5/22/2023 2:42 PM, Nirmoy Das wrote:
i915_active_fini() finalizes the debug object, which can occur before
the active retires and deactivates the debug object. Wait for one
final time before calling i915_active_fini();
Referen
On Mon, May 22, 2023 at 02:50:51PM -0700, Dixit, Ashutosh wrote:
On Mon, 22 May 2023 14:34:18 -0700, Umesh Nerlige Ramappa wrote:
On Mon, May 22, 2023 at 01:17:49PM -0700, Ashutosh Dixit wrote:
> Clearing out report id and timestamp as means to detect unlanded reports
> only works if report siz
On Mon, 22 May 2023 15:08:42 -0700, Umesh Nerlige Ramappa wrote:
>
Hi Umesh,
> On Mon, May 22, 2023 at 01:20:12PM -0700, Dixit, Ashutosh wrote:
> > On Fri, 19 May 2023 15:56:42 -0700, Umesh Nerlige Ramappa wrote:
> >>
> >> On DG2, capturing OA reports while running heavy render workloads
> >> som
Am 22.05.23 um 20:46 schrieb Thomas Zimmermann:
[...]
Looking at this patch makes me wonder if we should have implemented
fb_dirty for the MSM driver. We have drm_framebuffer_funcs::dirty()
implemented (by wrapping the drm_atomic_helper_dirtyfb()).
I think so. You'd need something similar to
Moving display-specific substructure definitions will help keep display
more self-contained and make it easier to re-use in other drivers (i.e.,
Xe) in the future.
Signed-off-by: Matt Roper
Reviewed-by: Andrzej Hajda
Reviewed-by: Lucas De Marchi
---
.../drm/i915/display/intel_display_device.h
Rather than embeddeding the display's device info within the main device
info structure, just provide a pointer to the display-specific
structure. This is in preparation for moving the display device info
definitions into the display code itself and for eventually allowing the
pointer to be assign
Since i915's display code will soon be shared by two DRM drivers (i915
and Xe), it makes sense for the display code itself to be responsible
for recognizing the platform it's running on rather than relying on the
making the top-level DRM driver handle this. This also becomes more
important for all
Move the runtime info specific to display into display-specific
structures as has already been done with the constant display info.
v2:
- Rename __runtime to __runtime_defaults for more clarity on the
purpose. (Andrzej)
- Move introduction of DISPLAY_INFO() to previous patch. (Andrzej)
- D
Rather than selecting the display IP and feature flags at the same time
the general PCI probing happens, move this step into the display code
itself so that it can be more easily re-used outside of i915 (i.e., by
the Xe driver).
v2:
- Make intel_display_device_probe() always return a non-NULL poi
For platforms with GMD_ID support (i.e., everything MTL and beyond),
identification of the display IP present should be based on the contents
of the GMD_ID register rather than a PCI devid match.
Note that since GMD_ID readout requires access to the PCI BAR, a slight
change to the driver init sequ
It makes sense to keep the display feature test macros centralized
within the display code.
Signed-off-by: Matt Roper
Reviewed-by: Andrzej Hajda
---
.../drm/i915/display/intel_display_device.h | 39
drivers/gpu/drm/i915/i915_drv.h | 60 ---
2 files c
tree/branch: INFO setup_repo_specs:
/db/releases/20230524001904/lkp-src/repo/*/linux-next
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 9f925874281f7e8855855d6210d6e29d844e4307 Add linux-next specific
files for 20230523
Error/Warning reports:
https
== Series Details ==
Series: i915: Move display identification/probing under display/ (rev3)
URL : https://patchwork.freedesktop.org/series/117931/
State : warning
== Summary ==
Error: dim checkpatch failed
d9e8003baa3d drm/i915/display: Move display device info to header under display/
Traceb
== Series Details ==
Series: i915: Move display identification/probing under display/ (rev3)
URL : https://patchwork.freedesktop.org/series/117931/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Clearing out report id and timestamp as means to detect unlanded reports
only works if report size is power of 2. That is, only when report size is
a sub-multiple of the OA buffer size can we be certain that reports will
land at the same place each time in the OA buffer (after rewind). If report
si
== Series Details ==
Series: drm/i915/color: register & get config abstractions (rev2)
URL : https://patchwork.freedesktop.org/series/117875/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13176 -> Patchwork_117875v2
Summary
== Series Details ==
Series: Add rc_range_params for YUV420
URL : https://patchwork.freedesktop.org/series/118204/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13176 -> Patchwork_118204v1
Summary
---
**SUCCESS**
== Series Details ==
Series: drm/i915: Replace all non-returning strlcpy with strscpy
URL : https://patchwork.freedesktop.org/series/118212/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13176 -> Patchwork_118212v1
Summary
== Series Details ==
Series: drm/i915: simplify switch to if-elseif
URL : https://patchwork.freedesktop.org/series/118216/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13177 -> Patchwork_118216v1
Summary
---
**SUCCE
== Series Details ==
Series: drm/i915/pmu: couple of cleanups
URL : https://patchwork.freedesktop.org/series/118225/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13177 -> Patchwork_118225v1
Summary
---
**SUCCESS**
On Tue, May 23, 2023 at 11:20:54AM -0700, Dixit, Ashutosh wrote:
On Mon, 22 May 2023 15:08:42 -0700, Umesh Nerlige Ramappa wrote:
Hi Umesh,
On Mon, May 22, 2023 at 01:20:12PM -0700, Dixit, Ashutosh wrote:
> On Fri, 19 May 2023 15:56:42 -0700, Umesh Nerlige Ramappa wrote:
>>
>> On DG2, captu
== Series Details ==
Series: i915: Move display identification/probing under display/ (rev3)
URL : https://patchwork.freedesktop.org/series/117931/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13180 -> Patchwork_117931v3
S
== Series Details ==
Series: drm/i915/perf: Clear out entire reports after reading if not power of 2
size (rev3)
URL : https://patchwork.freedesktop.org/series/118151/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13180 -> Patchwork_118151v3
==
== Series Details ==
Series: drm/i915/color: register & get config abstractions (rev2)
URL : https://patchwork.freedesktop.org/series/117875/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13176_full -> Patchwork_117875v2_full
===
== Series Details ==
Series: i915: Move display identification/probing under display/ (rev4)
URL : https://patchwork.freedesktop.org/series/117931/
State : warning
== Summary ==
Error: dim checkpatch failed
7ffe6d000c98 drm/i915/display: Move display device info to header under display/
Traceb
== Series Details ==
Series: i915: Move display identification/probing under display/ (rev4)
URL : https://patchwork.freedesktop.org/series/117931/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: i915: Move display identification/probing under display/ (rev4)
URL : https://patchwork.freedesktop.org/series/117931/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13180 -> Patchwork_117931v4
S
== Series Details ==
Series: Add rc_range_params for YUV420
URL : https://patchwork.freedesktop.org/series/118204/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13176_full -> Patchwork_118204v1_full
Summary
---
**SUC
> From: Alex Williamson
> Sent: Tuesday, May 23, 2023 11:50 PM
>
> On Tue, 23 May 2023 01:20:17 +
> "Liu, Yi L" wrote:
>
> > > From: Alex Williamson
> > > Sent: Tuesday, May 23, 2023 6:16 AM
> > >
> > > On Sat, 13 May 2023 06:28:24 -0700
> > > Yi Liu wrote:
> > >
> > > > This adds ioctl f
== Series Details ==
Series: drm/i915: Replace all non-returning strlcpy with strscpy
URL : https://patchwork.freedesktop.org/series/118212/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13176_full -> Patchwork_118212v1_full
> From: Alex Williamson
> Sent: Tuesday, May 23, 2023 11:51 PM
>
> On Tue, 23 May 2023 01:41:36 +
> "Liu, Yi L" wrote:
>
> > > From: Alex Williamson
> > > Sent: Tuesday, May 23, 2023 6:01 AM
> > >
> > > On Sat, 13 May 2023 06:28:23 -0700
> > > Yi Liu wrote:
> > >
> > > > This adds ioctl f
> From: Liu, Yi L
> Sent: Wednesday, May 24, 2023 10:21 AM
>
> > >
> > > vfio_device_open_file()
> > > {
> > > dev_warn(device->dev, "vfio-noiommu device opened by user "
> > > "(%s:%d)\n", current->comm, task_pid_nr(current));
> > > }
> >
> > There needs to be a taint when VFIO_GR
> From: Tian, Kevin
> Sent: Wednesday, May 24, 2023 10:39 AM
>
> > From: Liu, Yi L
> > Sent: Wednesday, May 24, 2023 10:21 AM
> >
> > > >
> > > > vfio_device_open_file()
> > > > {
> > > > dev_warn(device->dev, "vfio-noiommu device opened by user "
> > > >"(%s:%d)\n",
Move rc_param calculation for native_420 into calculate_rc_parameter.
second_line_bpg_offset and second_line_offset_adj are both rc params
and it would be better to have these calculated where all the other
rc parameters are calculated.
--v2
-Add the reason for commit in commit message [Jani]
Cc:
== Series Details ==
Series: Add rc_range_params for YUV420 (rev2)
URL : https://patchwork.freedesktop.org/series/118204/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13180 -> Patchwork_118204v2
Summary
---
**WARNIN
== Series Details ==
Series: drm/i915: simplify switch to if-elseif
URL : https://patchwork.freedesktop.org/series/118216/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13177_full -> Patchwork_118216v1_full
Summary
---
On Tue, 2023-05-23 at 16:14 +0300, Jani Nikula wrote:
> On Tue, 23 May 2023, "Govindapillai, Vinod"
> wrote:
> > On Tue, 2023-05-23 at 12:01 +0300, Jani Nikula wrote:
> > > On Tue, 23 May 2023, Vinod Govindapillai
> > > wrote:
> > > > From MTL onwwards, pcode locks the QGV point based on peak B
== Series Details ==
Series: drm/i915/pmu: couple of cleanups
URL : https://patchwork.freedesktop.org/series/118225/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13177_full -> Patchwork_118225v1_full
Summary
---
**S
92 matches
Mail list logo
