From: Harry Wentland <hwentlan@amd.com>
To: Dave Airlie <airlied@gmail.com>,
"Francis, David" <David.Francis@amd.com>
Cc: Manasi Navare <manasi.d.navare@intel.com>,
"Lipski, Mikita" <Mikita.Lipski@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v4 0/5] MST DSC support in drm-mst
Date: Mon, 26 Aug 2019 21:12:56 +0000 [thread overview]
Message-ID: <dee304ae-d674-cc05-d7cb-42433206309d@amd.com> (raw)
In-Reply-To: <CAPM=9tw8501utfWGV6m+kFGTuO4AsKmxZ5bfHi9A_vXmf9_ogg@mail.gmail.com>
On 2019-08-26 3:50 p.m., Dave Airlie wrote:
> On Sat, 24 Aug 2019 at 06:24, Francis, David <David.Francis@amd.com> wrote:
>>
>> Adding DSC functionality to drm_dp_mst_atomic_check() is a good idea.
>> However, until amdgpu switches over to that system, I wouldn't be able
>> to test those changes. Making that switch is on our TODO list, and it would
>> fix a number of problems with our current MST implementation, but
>> it's going to be a major rewrite.
>>
>> MST DSC hardware is already on the market. It would be expedient to
>> merge the patches we need for Navi support sooner and update
>> drm_dp_mst_atomic_check when we're able to test it.
>
> Is there any commitment to rewriting it, a timeline or anything?
>
> The problem with this situation is there is always new hardware coming
> onto the market, and there is always pressure to support all the
> features of that new hardware, and the pressure always comes like this
> and being expedient. However I've found that a lot of the time the
> required refactor or work is never done, because the time is being
> allocated now to the next GPU that is coming on the market, and nobody
> ever cares enough to clean up their technical debt.
>
> How come the needs for MST DSC support wasn't identified earlier,
> blocked on refactoring of the code to use common code, and then that
> task made a higher priority?
>
drm_dp_mst_atomic_check was introduced by Lyude back in January with
https://patchwork.freedesktop.org/patch/276405/ as part of
https://patchwork.freedesktop.org/series/54031/
At the time Lyude updated i915 and nouveau to use these helpers. amdgpu
wasn't updated.
> I'm sorta inclined to say no we shouldn't be merging any driver
> specific code here, because this is the only point we can push
> pressure on to refactor the MST implementation, which I guess
> otherwise we'll just keep avoiding until Lyude ends up doing it for
> you.
>
That's fair. I agree that the refactor should be done and I understand
where you're coming from. Since David is heading back to school in less
than a week I was inclined to see if we can push back a little so he can
get his change in. Other than that I don't mind holding off on the merge
unless the refactor is done.
Adding Mikita who'll pick up DSC stuff from David and will iterate on
these patches if necessary and look at the MST refactor.
Thanks for keeping us honest.
Harry
> Dave.
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-08-26 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 13:57 [PATCH v4 0/5] MST DSC support in drm-mst David Francis
2019-08-22 13:57 ` [PATCH v4 1/5] drm/dp-mst: Add PBN calculation for DSC modes David Francis
2019-08-22 21:42 ` Lyude Paul
2019-08-22 13:57 ` [PATCH v4 2/5] drm/dp-mst: Parse FEC capability on MST ports David Francis
2019-08-22 13:57 ` [PATCH v4 3/5] drm/dp-mst: Add MST support to DP DPCD R/W functions David Francis
2019-08-22 21:54 ` Lyude Paul
2019-08-22 13:57 ` [PATCH v4 4/5] drm/dp-mst: Fill branch->num_ports David Francis
2019-08-22 21:55 ` Lyude Paul
2019-08-22 13:57 ` [PATCH v4 5/5] drm/dp-mst: Add helpers for querying and enabling MST DSC David Francis
2019-08-22 23:49 ` Lyude Paul
2019-08-22 21:39 ` [PATCH v4 0/5] MST DSC support in drm-mst Lyude Paul
2019-08-23 0:03 ` Lyude Paul
2019-08-23 20:24 ` Francis, David
2019-08-26 19:50 ` Dave Airlie
2019-08-26 21:12 ` Harry Wentland [this message]
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=dee304ae-d674-cc05-d7cb-42433206309d@amd.com \
--to=hwentlan@amd.com \
--cc=David.Francis@amd.com \
--cc=Mikita.Lipski@amd.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=manasi.d.navare@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