Quoting Tvrtko Ursulin (2018-04-03 13:38:25)
> From: Tvrtko Ursulin
>
> Realtime scheduling interferes with execlists submission (tasklet) so try
> to simplify the PWM loop in a few ways:
>
> * Drop RT.
> * Longer batches for smaller systematic error.
> * More truthful test duration calculati
== Series Details ==
Series: Add NV12 support (rev7)
URL : https://patchwork.freedesktop.org/series/39670/
State : success
== Summary ==
Series 39670v7 Add NV12 support
https://patchwork.freedesktop.org/api/1.0/series/39670/revisions/7/mbox/
fi-bdw-5557u total:285 pass:264 dwarn:0 dfa
From: Tvrtko Ursulin
Realtime scheduling interferes with execlists submission (tasklet) so try
to simplify the PWM loop in a few ways:
* Drop RT.
* Longer batches for smaller systematic error.
* More truthful test duration calculation.
* Less clock queries.
* No self-adjust - instead just r
== Series Details ==
Series: Add NV12 support (rev7)
URL : https://patchwork.freedesktop.org/series/39670/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
028f935bfc8a drm/i915/skl+: rename skl_wm_values struct to skl_ddb_values
c37c92d65c7c drm/i915/skl+: refactor WM calculation
== Series Details ==
Series: Documentation patch for batchbuffer submission (rev4)
URL : https://patchwork.freedesktop.org/series/38433/
State : failure
== Summary ==
Applying: i915.rst: Narration overview on GEM + minor reorder to improve
narration
error: Failed to merge in the changes.
Usin
Quoting kevin.rogo...@intel.com (2018-04-03 13:52:25)
> From: Kevin Rogovin
>
> Add the documentation of "DOC: User command execution" of
> i915_gem_execbuffer.c into a new section in i915.rst.
>
> Signed-off-by: Kevin Rogovin
Reviewed-by: Joonas Lahtinen
Regards, Joonas
Quoting kevin.rogo...@intel.com (2018-04-03 13:52:24)
> From: Kevin Rogovin
>
> Now that "DOC: User command execution" of i915_gem_execbuffer.c is included
> in the i915.rst, it is benecifial (for new developers) to read what happens
> at the bottom of the driver stack (in terms of bytes written
Quoting Steven Rostedt (2018-04-02 16:17:36)
> On Fri, 30 Mar 2018 16:01:31 +0100
> Chris Wilson wrote:
>
> > Across suspend, we may see a very large drift in timestamps if the sched
> > clock is unstable, prompting the global trace's ringbuffer code to warn
> > and suggest switching to the globa
Quoting kevin.rogo...@intel.com (2018-04-03 13:52:23)
> From: Kevin Rogovin
>
> Add a narration to i915.rst about Intel GEN GPU's: engines,
> driver context and relocation.
>
> Signed-off-by: Kevin Rogovin
I'm still bummed by the long lines in the bulleted list, but regardless:
Reviewed-by: J
Quoting Tvrtko Ursulin (2018-04-03 12:36:44)
> From: Tvrtko Ursulin
>
> Reset and unwedge stress testing is supposed to trigger wedging or resets
> at incovenient times and then re-use the context so either the context or
> driver tracking might get confused and break.
>
> v2:
> * Renamed for m
== Series Details ==
Series: GuC, HuC Loading Support for Cannonlake. (rev2)
URL : https://patchwork.freedesktop.org/series/41031/
State : failure
== Summary ==
Possible new issues:
Test core_auth:
Subgroup basic-auth:
pass -> SKIP (shard-snb)
From: Tvrtko Ursulin
Reset and unwedge stress testing is supposed to trigger wedging or resets
at incovenient times and then re-use the context so either the context or
driver tracking might get confused and break.
v2:
* Renamed for more sensible naming.
* Added some comments to explain what t
Quoting Francisco Jerez (2018-04-02 17:32:20)
> Chris Wilson writes:
>
> > We would like to start doing some bookkeeping at the beginning, between
> > contexts and at the end of execlists submission. We already mark the
> > beginning and end using EXECLISTS_ACTIVE_USER, to provide an indication
>
Chris Wilson writes:
> We would like to start doing some bookkeeping at the beginning, between
> contexts and at the end of execlists submission. We already mark the
> beginning and end using EXECLISTS_ACTIVE_USER, to provide an indication
> when the HW is idle. This give us a pair of sequence po
From: Kevin Rogovin
Note: I want to make a one or two follow-up series that provide
narration and potentially additional documentation for GUC submission
and the breadcrumbs.
v4:
Drop some details from narration to provide better focus.
(suggested/requested by Chris Wilson)
Spelling an
From: Kevin Rogovin
Add documentation to a number of the function pointer fields of
intel_engine_cs.
Signed-off-by: Kevin Rogovin
---
drivers/gpu/drm/i915/intel_ringbuffer.h | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_ringbuffer
From: Kevin Rogovin
Now that "DOC: User command execution" of i915_gem_execbuffer.c is included
in the i915.rst, it is benecifial (for new developers) to read what happens
at the bottom of the driver stack (in terms of bytes written to be read
by the GPU) when processing a user-space batchbuffer.
From: Kevin Rogovin
Add a narration to i915.rst about Intel GEN GPU's: engines,
driver context and relocation.
Signed-off-by: Kevin Rogovin
---
Documentation/gpu/i915.rst | 116
drivers/gpu/drm/i915/i915_vma.h | 10 ++--
2 files changed, 100 inser
From: Kevin Rogovin
Add the documentation of "DOC: User command execution" of
i915_gem_execbuffer.c into a new section in i915.rst.
Signed-off-by: Kevin Rogovin
---
Documentation/gpu/i915.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/gpu/i915.rst b/Documentation/g
From: Kevin Rogovin
Correct documentation of logical ring context implementation to note
that ringbuffer and backing store are created lazily for all context
types (driver global, local default context and local extra context).
Signed-off-by: Kevin Rogovin
---
drivers/gpu/drm/i915/intel_lrc.c
== Series Details ==
Series: YCBCR 4:2:0/4:4:4 output support for LSPCON (rev5)
URL : https://patchwork.freedesktop.org/series/36068/
State : warning
== Summary ==
Series 36068v5 YCBCR 4:2:0/4:4:4 output support for LSPCON
https://patchwork.freedesktop.org/api/1.0/series/36068/revisions/5/mbox
== Series Details ==
Series: YCBCR 4:2:0/4:4:4 output support for LSPCON (rev5)
URL : https://patchwork.freedesktop.org/series/36068/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
093f7ee765f1 drm/i915: Introduce CRTC output format
-:87: CHECK:PARENTHESIS_ALIGNMENT: Alignment s
On 30/03/2018 20:15, Rinat Ibragimov wrote:
Четверг, 29 марта 2018, 21:46 +03:00 от Tvrtko Ursulin :
+#define engine_ptr(engines, n) \
+((struct engine *)((unsigned char *)(&engines->engine) + (n) * sizeof(struct
engine)))
I think (&engines->engine + (n)) is easier to read.
Absolutel
On 29/03/2018 15:30, Eero Tamminen wrote:
Hi,
I tested this on HSW GT2, BYT, BDW GT3, SKL GT2 and KBL GT3e,
with Ubuntu 16.04 and 17.10, using Ubuntu default kernels (4.4 to 4.13)
and latest drm-tip build (4.16.0-rc7).
General comments
This will be used by our customers and
== Series Details ==
Series: GuC, HuC Loading Support for Cannonlake. (rev2)
URL : https://patchwork.freedesktop.org/series/41031/
State : failure
== Summary ==
Series 41031v2 GuC, HuC Loading Support for Cannonlake.
https://patchwork.freedesktop.org/api/1.0/series/41031/revisions/2/mbox/
---
From: Tvrtko Ursulin
intel-gpu-top is a dangerous tool which can hang machines due unsafe mmio
register access. This patch rewrites it to use only PMU.
Only overall command streamer busyness and GPU global data such as power
and frequencies are included in this new version.
For access to more G
This patch adds an enum "intel_output_format" to represent
the output format of a particular CRTC. This enum will be
used to produce a RGB/YCBCR4:4:4/YCBCR4:2:0 output format
during the atomic modeset calculations.
V5:
- Created this separate patch to introduce and init output_format.
- Initialize
From: "Sharma, Shashank"
As LSPCON is a DP branch device, LSPCON vendors define
specific methods to pass AVI infoframes to the the chip.
This patch adds:
- a generic wrapper function for writing AVI infoframes for
all LSPCON devices.
- a vendor specific function to wrire AVI infoframes into
M
Currently, we are using a bool in CRTC state (state->ycbcr420),
to indicate modeset, that the output format is YCBCR 4:2:0. Now in
order to support other YCBCR formats, we will need more such flags.
This patch adds a new enum parameter for YCBCR 4:2:0 outputs, in the
CRTC output formats and then p
This patch adds support for YCBCR 4:4:4 CRTC output format.
To do this, this patch extends the existing YCBCR 4:2:0
framework by:
- Adding new parameter in for YCBCR 4:4:4 enum crtc_iutput_format.
- Adding case for YCBCR 4:4:4 in while setting AVI infoframes.
- Adding necessary checks in modeset se
From: "Sharma, Shashank"
Intel LSPCON chip is provided by 2 vendors:
- Megachips America (MCA)
- Parade technologies (Parade tech)
Its important to know the vendor of this chip, as the address to
write AVI infoframes is different for those two.
This patch reads the vendor OUI signature, and mar
In order to pass AVI infoframes to LSPCON devices, a source has to
write them in a vendor recommended method and location.
This patch series:
- adds generic LSPCON infoframe setup functions.
- registers these functions into existing AVI infoframe framework.
- triggers these functions from modeset
This patch series adds YCBCR 4:2:0 output support for LSPCON displays.
In order to indicate the color format of output, to the LSPCON device,
a source has to set and send proper AVI infoframes to LSPCON. So this
patch series:
- introduces concept of CRTC output format.
- adds AVI infoframes support
Different LSPCON vendors specify their custom methods to pass
AVI infoframes to the LSPCON chip, so does Parade tech.
This patch adds functions to arrange and write AVI infoframes
into Parade LSPCON chips.
V2: rebase
V3: Added r-b from Maarten
V4: rebase
V5: rebase
V6: rebase
V7: Fixed checkpatch
LSPCON chips can generate YCBCR outputs, if asked nicely :).
In order to generate YCBCR 4:2:0 outputs, a source must:
- send YCBCR 4:4:4 signals to LSPCON
- program color space as 4:2:0 in AVI infoframes
Whereas for YCBCR 4:4:4 outputs, the source must:
- send YCBCR 4:4:4 signals to LSPCON
- prog
Hi,
Here's refreshed fixes for 4.17-rc1 with regression one removed,
contains a few fixes for vfio ioctl and dmabuf interface, properly
dma unmap for ggtt, etc.
thanks
--
The following changes since commit d8303075699292008ae5b2c8fc728d455b994c26:
drm/i915/gvt: force to set all context contro
DK, please start stable backport commit messages with:
commit b1e314462bba76660eec62760bb2e87f28f58866 upstream.
Referencing the upstream commit.
BR,
Jani.
On Thu, 29 Mar 2018, Dhinakaran Pandiyan wrote:
> If bios sets up an MST output and hardware state readout code sees this is
> an SST co
101 - 137 of 137 matches
Mail list logo
