From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [Intel-gfx] [RFC PATCH 0/3] i915 writeback private framework
Date: Thu, 28 Apr 2022 15:02:16 +0300 [thread overview]
Message-ID: <YmqCSDYfWawBcOU5@pendragon.ideasonboard.com> (raw)
In-Reply-To: <DM5PR11MB1739991ACAEF173E24B53CCAE3FD9@DM5PR11MB1739.namprd11.prod.outlook.com>
Hi Suraj,
On Thu, Apr 28, 2022 at 05:51:47AM +0000, Kandpal, Suraj wrote:
> ++Laurent ,Dmitry, and Abhinav
>
> Hi,
> Can you have a look at the private implementation i915 is currently going with till
> we can figure out how to work with drm core .
No, sorry, I barely have time to follow up on core DRM changes, I can't
help with private i915 topics in my spare time.
> > 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.
> > [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/
> > This forces us to use a drm_connector which is not embedded in
> > intel_connector the current drm_writeback framework becomes very
> > unfeasible to us as it would mean a lot of checks at a lot of places to take into
> > account the above issue.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
> > [3]https://patchwork.kernel.org/project/dri-devel/list/?series=633565
> > In the meantime for i915 to start using the writeback functionality we came
> > up with a interim solution to own writeback pipeline bypassing one provided
> > by drm which is what these patches do.
> > Note: these are temp patches till we figure out how we can either change
> > drm core writeback to work with our intel_connector structure or find a
> > different solution which allows us to work with the current drm_writeback
> > framework
> >
> > Suraj Kandpal (3):
> > drm/i915: Creating writeback pipeline to bypass drm_writeback
> > framework
> > drm/i915: Define WD trancoder for i915
> > drm/i915: Enabling WD Transcoder
> >
> > drivers/gpu/drm/i915/Makefile | 2 +
> > drivers/gpu/drm/i915/display/intel_acpi.c | 1 +
> > drivers/gpu/drm/i915/display/intel_display.c | 89 +-
> > drivers/gpu/drm/i915/display/intel_display.h | 15 +
> > .../drm/i915/display/intel_display_types.h | 18 +
> > drivers/gpu/drm/i915/display/intel_dpll.c | 3 +
> > drivers/gpu/drm/i915/display/intel_opregion.c | 3 +
> > .../gpu/drm/i915/display/intel_wb_connector.c | 296 ++++++
> > .../gpu/drm/i915/display/intel_wb_connector.h | 99 ++
> > drivers/gpu/drm/i915/display/intel_wd.c | 978 ++++++++++++++++++
> > drivers/gpu/drm/i915/display/intel_wd.h | 82 ++
> > drivers/gpu/drm/i915/i915_drv.h | 5 +
> > drivers/gpu/drm/i915/i915_irq.c | 8 +-
> > drivers/gpu/drm/i915/i915_pci.c | 7 +-
> > drivers/gpu/drm/i915/i915_reg.h | 139 +++
> > 15 files changed, 1742 insertions(+), 3 deletions(-) create mode 100644
> > drivers/gpu/drm/i915/display/intel_wb_connector.c
> > create mode 100644 drivers/gpu/drm/i915/display/intel_wb_connector.h
> > create mode 100644 drivers/gpu/drm/i915/display/intel_wd.c
> > create mode 100644 drivers/gpu/drm/i915/display/intel_wd.h
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-04-28 12:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 5:07 [Intel-gfx] [RFC PATCH 0/3] i915 writeback private framework Suraj Kandpal
2022-04-21 5:07 ` [Intel-gfx] [RFC PATCH 1/3] drm/i915: Creating writeback pipeline to bypass drm_writeback framework Suraj Kandpal
2022-04-28 5:52 ` Kandpal, Suraj
2022-04-21 5:07 ` [Intel-gfx] [RFC PATCH 2/3] drm/i915: Define WD trancoder for i915 Suraj Kandpal
2022-04-28 5:53 ` Kandpal, Suraj
2022-04-21 5:07 ` [Intel-gfx] [RFC PATCH 3/3] drm/i915: Enabling WD Transcoder Suraj Kandpal
2022-04-28 5:53 ` Kandpal, Suraj
2022-04-21 5:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915 writeback private framework (rev5) Patchwork
2022-04-21 5:35 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-04-21 6:00 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-28 5:51 ` [Intel-gfx] [RFC PATCH 0/3] i915 writeback private framework Kandpal, Suraj
2022-04-28 12:02 ` Laurent Pinchart [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-16 9:37 Suraj Kandpal
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=YmqCSDYfWawBcOU5@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=quic_abhinavk@quicinc.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