From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/display: plane property for async supported modifiers
Date: Fri, 25 Oct 2024 09:03:49 +0300 [thread overview]
Message-ID: <Zxs0xT1tp9ToPDoo@intel.com> (raw)
In-Reply-To: <IA0PR11MB7307CD2E8E7D15D982662127BA4F2@IA0PR11MB7307.namprd11.prod.outlook.com>
On Fri, Oct 25, 2024 at 04:28:18AM +0000, Murthy, Arun R wrote:
> > > Subject: Re: [PATCH] drm/i915/display: plane property for async
> > > supported modifiers
> > >
> > > On Wed, Oct 16, 2024 at 04:54:09PM +0300, Ville Syrjälä wrote:
> > > > On Wed, Oct 16, 2024 at 04:30:19PM +0300, Ville Syrjälä wrote:
> > > > > On Wed, Oct 16, 2024 at 11:06:26AM +0530, Arun R Murthy wrote:
> > > > > > Create a i915 private plane property for sharing the async
> > > > > > supported modifiers to the user.
> > > > > > UMD related discussion requesting the same
> > > > > > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29618#
> > > > > > no
> > > > > > te_2487123
> > > > > >
> > > > > > Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> > > > > > ---
> > > > > > .../gpu/drm/i915/display/intel_atomic_plane.c | 6 +++
> > > > > > .../drm/i915/display/intel_display_types.h | 4 ++
> > > > > > .../drm/i915/display/skl_universal_plane.c | 49
> > ++++++++++++++++++-
> > > > >
> > > > > This whole thing belongs in the drm core.
> > > >
> > > > And I don't even see an actual implementation of anything here.
> > > > Why did you even post this when it doesn't do anything?
> > > >
> > > > Anyways, thinking about how we might actually implement this, we can
> > > > probably leverage
> > > > https://patchwork.freedesktop.org/patch/619047/?series=139807&rev=3
> > >
> > > Although we should probably pass the format to that as well...
> > >
> > The blob points to the struct with elements, modifier and formats.
> > The main intention of this patch to get the i915 plane private property.
> > The reason for not having this as drm property is we are the only user for this
> > and no other vendor has this restriction.
> >
>
> Any comments on this?
Seeinag as the patch does nothing so there is nothing to
comment beyond what I already said.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-10-25 6:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 5:36 [PATCH] drm/i915/display: plane property for async supported modifiers Arun R Murthy
2024-10-16 7:52 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-16 7:52 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-16 7:53 ` ✓ CI.KUnit: success " Patchwork
2024-10-16 8:05 ` ✓ CI.Build: " Patchwork
2024-10-16 8:07 ` ✓ CI.Hooks: " Patchwork
2024-10-16 8:08 ` ✗ CI.checksparse: warning " Patchwork
2024-10-16 8:38 ` ✓ CI.BAT: success " Patchwork
2024-10-16 13:30 ` [PATCH] " Ville Syrjälä
2024-10-16 13:54 ` Ville Syrjälä
2024-10-16 14:01 ` Ville Syrjälä
2024-10-17 4:07 ` Murthy, Arun R
2024-10-25 4:28 ` Murthy, Arun R
2024-10-25 6:03 ` Ville Syrjälä [this message]
2024-10-16 18:20 ` ✗ CI.FULL: failure for " Patchwork
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=Zxs0xT1tp9ToPDoo@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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