From: Swati Sharma <swati2.sharma@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: Re: [Intel-gfx] [PATCH v6 0/3] Enable Pipewriteback
Date: Wed, 28 Sep 2022 18:16:49 +0530 [thread overview]
Message-ID: <d690c52f-edd1-fb19-aad4-ec32ed928dcf@intel.com> (raw)
In-Reply-To: <20220919130505.1984383-1-suraj.kandpal@intel.com>
Hi Suraj,
CI is not green
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107440v9/shards-all.html?testfilter=kms_writeback
2/4 subtests are passing
writeback-fb-id subtest can be fixed by asserting EINVAL for i915
we need to fix writeback-check-output first
On local validation, we were getting CRC mismatch however CI results
show different issue
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107440v9/shard-tglu-4/igt@kms_writeback@writeback-check-output.html#dmesg-warnings575
Please check the same if its relevant.
On 19-Sep-22 6:35 PM, Kandpal, Suraj wrote:
> A patch series was floated in the drm mailing list which aimed to change
> the drm_connector and drm_encoder fields to pointer in the
> drm_connector_writeback structure, this received a huge pushback from
> the community but since i915 expects each connector present in the
> drm_device list to be a intel_connector but drm_writeback framework
> makes us have a connector which cannot be embedded in an intel_connector
> structure.
> [1]
> https://patchwork.kernel.org/project/dri-devel/patch/20220202081702.22119-1-suraj.kandpal@intel.com/
> [2]
> https://patchwork.kernel.org/project/dri-devel/patch/20220202085429.22261-6-suraj.kandpal@intel.com/
> Since no one had an issue with encoder field being changed into a
> pointer it was decided to break the connector and encoder pointer
> changes into two different series.The encoder field changes is
> currently being worked upon by Abhinav Kumar and the changes have been
> merged.
> [3]https://patchwork.kernel.org/project/dri-devel/list/?series=633565
> Going forward we use a drm_connector which is not embedded in
> intel_connector.
> We also create a intel_encoder to avoid changes to many
> iterators but no intel_connector. We also changed all iterators that
>
> ---v2
> solving BAT issues
>
> ---v3
> -removing unecessary comments from i915_reg.h [Arun]
> -moving wd_init into its own if condition [Arun]
> -fixing comment styling and alignment in intel_wd.c [Arun]
> -removing continue from loop and calling function if condition is met
> [Arun]
> -removing useless arguments from intel_queue_writeback_job and
> intel_enabling_capture [Arun]
>
> --v4
> Adding Reviewed-by to patches which were previously reviewd
>
> --v5
> Adding Reviewed-by for patch 3
>
> --v6
> Solving BAT issue
> changes for checkpatch to pass
>
> Suraj Kandpal (3):
> drm/i915: Define WD trancoder for i915
> drm/i915 : Changing intel_connector iterators
> drm/i915: Enabling WD Transcoder
>
> drivers/gpu/drm/i915/Makefile | 1 +
> drivers/gpu/drm/i915/display/intel_acpi.c | 8 +-
> drivers/gpu/drm/i915/display/intel_crtc.c | 6 +
> .../drm/i915/display/intel_crtc_state_dump.c | 1 +
> drivers/gpu/drm/i915/display/intel_ddi.c | 6 +
> drivers/gpu/drm/i915/display/intel_display.c | 68 +-
> drivers/gpu/drm/i915/display/intel_display.h | 18 +-
> .../drm/i915/display/intel_display_debugfs.c | 13 +-
> .../drm/i915/display/intel_display_types.h | 32 +-
> drivers/gpu/drm/i915/display/intel_dpll.c | 6 +
> .../drm/i915/display/intel_modeset_setup.c | 119 ++-
> .../drm/i915/display/intel_modeset_verify.c | 17 +-
> drivers/gpu/drm/i915/display/intel_opregion.c | 3 +
> drivers/gpu/drm/i915/display/intel_wd.c | 694 ++++++++++++++++++
> drivers/gpu/drm/i915/display/intel_wd.h | 48 ++
> drivers/gpu/drm/i915/i915_drv.h | 1 +
> drivers/gpu/drm/i915/i915_irq.c | 8 +-
> drivers/gpu/drm/i915/i915_pci.c | 7 +-
> drivers/gpu/drm/i915/i915_reg.h | 137 ++++
> 19 files changed, 1137 insertions(+), 56 deletions(-)
> create mode 100644 drivers/gpu/drm/i915/display/intel_wd.c
> create mode 100644 drivers/gpu/drm/i915/display/intel_wd.h
>
--
~Swati Sharma
next prev parent reply other threads:[~2022-09-28 12:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 13:05 [Intel-gfx] [PATCH v6 0/3] Enable Pipewriteback Kandpal, Suraj
2022-09-19 13:05 ` [Intel-gfx] [PATCH v6 1/3] drm/i915: Define WD trancoder for i915 Kandpal, Suraj
2022-10-05 9:07 ` Jani Nikula
2022-09-19 13:05 ` [Intel-gfx] [PATCH v6 2/3] drm/i915 : Changing intel_connector iterators Kandpal, Suraj
2022-10-05 10:30 ` Jani Nikula
2022-10-20 8:08 ` Kandpal, Suraj
2022-10-20 8:53 ` Jani Nikula
2022-10-20 8:56 ` Kandpal, Suraj
2022-09-19 13:05 ` [Intel-gfx] [PATCH v6 3/3] drm/i915: Enabling WD Transcoder Kandpal, Suraj
2022-09-28 15:23 ` Swati Sharma
2022-09-19 14:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Enable Pipewriteback (rev6) Patchwork
2022-09-19 14:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-19 14:38 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-09-19 23:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Enable Pipewriteback (rev7) Patchwork
2022-09-19 23:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-20 0:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-20 8:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-09-20 14:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Enable Pipewriteback (rev8) Patchwork
2022-09-20 14:27 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-20 14:51 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-09-20 15:43 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-20 20:09 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-09-21 2:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Enable Pipewriteback (rev9) Patchwork
2022-09-21 2:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-21 2:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-21 3:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-09-21 5:14 ` [Intel-gfx] [PATCH v6 0/3] Enable Pipewriteback Kandpal, Suraj
2022-09-28 12:46 ` Swati Sharma [this message]
2022-09-28 13:55 ` Kandpal, Suraj
2022-09-28 15:15 ` Swati Sharma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d690c52f-edd1-fb19-aad4-ec32ed928dcf@intel.com \
--to=swati2.sharma@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=suraj.kandpal@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox