On Fri, Feb 23, 2018 at 5:31 PM, wrote:
> The bitmaps in drm_hdmi_info dont seem to be exposed to userspace.
>
> Our mode selection logic is in userspace at the moment which means its
> better userspace knows which modes support what.
>
> If we decide to move mode
Alright, found it
https://cgit.freedesktop.org/~seanpaul/dpu-staging/commit/?h=mtp-testing=34906195473f9e04601c49a45e3fedce0132eb7e
Thanks
Abhinav
On 2018-02-23 07:06, Sean Paul wrote:
On Thu, Feb 22, 2018 at 9:28 PM, Abhinav Kumar
wrote:
Looks good. Can you point us
I am OK with removing some parts of the parser but not entirely.
Fundamentally, we went ahead with the parser for a couple of reasons:
-> We would like to be able to associate the color format with the mode.
This helps us decide that if the same mode supports both RGB/YUV then
which one we
The bitmaps in drm_hdmi_info dont seem to be exposed to userspace.
Our mode selection logic is in userspace at the moment which means its
better userspace knows which modes support what.
If we decide to move mode validation entirely to the driver, we can use
these bitmaps to validate.
But
On Fri, Feb 23, 2018 at 01:29:03PM -0800, abhin...@codeaurora.org wrote:
> I am OK with removing some parts of the parser but not entirely.
>
> Fundamentally, we went ahead with the parser for a couple of reasons:
>
> -> We would like to be able to associate the color format with the mode.
>
Use drm_edid to parse the edid instead of the hand rolled dpu version.
Signed-off-by: Sean Paul
---
drivers/gpu/drm/msm/Makefile | 1 -
drivers/gpu/drm/msm/dp/dp_audio.c | 22 +-
drivers/gpu/drm/msm/dp/dp_display.c | 7 -
On Fri, Feb 23, 2018 at 11:30 AM, Sean Paul wrote:
> On Fri, Feb 23, 2018 at 08:17:54AM -0500, Rob Clark wrote:
>> In a way, based on the original writeback patch from Jilai Wang, but a
>> lot has shifted around since then.
>>
>> Signed-off-by: Rob Clark
On Fri, Feb 23, 2018 at 9:10 PM, Jordan Crouse wrote:
> On Fri, Feb 23, 2018 at 04:06:39PM +0530, Vivek Gautam wrote:
>> On Fri, Feb 23, 2018 at 5:22 AM, Jordan Crouse
>> wrote:
>> > On Wed, Feb 07, 2018 at 04:01:19PM +0530, Vivek Gautam wrote:
>>
On Fri, Feb 23, 2018 at 04:48:58PM +, Liviu Dudau wrote:
> On Fri, Feb 23, 2018 at 11:43:29AM -0500, Sean Paul wrote:
> > On Fri, Feb 23, 2018 at 11:25:11AM -0500, Rob Clark wrote:
> > > On Fri, Feb 23, 2018 at 10:59 AM, Sean Paul wrote:
> > > >
> > > > Have we
On Fri, Feb 23, 2018 at 11:39:06AM -0500, Sean Paul wrote:
> On Fri, Feb 23, 2018 at 04:21:05PM +, Liviu Dudau wrote:
> > On Fri, Feb 23, 2018 at 10:59:35AM -0500, Sean Paul wrote:
> > > On Fri, Feb 23, 2018 at 08:17:51AM -0500, Rob Clark wrote:
> > > > From: Brian Starkey
On Fri, Feb 23, 2018 at 11:43:29AM -0500, Sean Paul wrote:
> On Fri, Feb 23, 2018 at 11:25:11AM -0500, Rob Clark wrote:
> > On Fri, Feb 23, 2018 at 10:59 AM, Sean Paul wrote:
> > >
> > > Have we considered hiding writeback behind a client cap instead?
> >
> > It is kinda
On Fri, Feb 23, 2018 at 11:25:11AM -0500, Rob Clark wrote:
> On Fri, Feb 23, 2018 at 10:59 AM, Sean Paul wrote:
> >
> > Have we considered hiding writeback behind a client cap instead?
>
> It is kinda *almost* unneeded, since the connector reports itself as
> disconnected.
On Fri, Feb 23, 2018 at 08:17:54AM -0500, Rob Clark wrote:
> In a way, based on the original writeback patch from Jilai Wang, but a
> lot has shifted around since then.
>
> Signed-off-by: Rob Clark
> ---
> drivers/gpu/drm/msm/Makefile | 1 +
>
On Fri, Feb 23, 2018 at 10:59 AM, Sean Paul wrote:
>
> Have we considered hiding writeback behind a client cap instead?
It is kinda *almost* unneeded, since the connector reports itself as
disconnected.
I'm not sure what the reason was to drop the cap, but I think it
On Fri, Feb 23, 2018 at 10:59:35AM -0500, Sean Paul wrote:
> On Fri, Feb 23, 2018 at 08:17:51AM -0500, Rob Clark wrote:
> > From: Brian Starkey
> >
> > Writeback connectors represent writeback engines which can write the
> > CRTC output to a memory framebuffer. Add a
On Fri, Feb 23, 2018 at 08:17:52AM -0500, Rob Clark wrote:
> From: Brian Starkey
>
> Add the WRITEBACK_OUT_FENCE_PTR property to writeback connectors, to
> enable userspace to get a fence which will signal once the writeback is
> complete. It is not allowed to request an
On Fri, Feb 23, 2018 at 04:06:39PM +0530, Vivek Gautam wrote:
> On Fri, Feb 23, 2018 at 5:22 AM, Jordan Crouse wrote:
> > On Wed, Feb 07, 2018 at 04:01:19PM +0530, Vivek Gautam wrote:
> >> From: Sricharan R
> >>
> >> The smmu device probe/remove
On Thu, Feb 22, 2018 at 9:28 PM, Abhinav Kumar wrote:
> Looks good. Can you point us to the fix done in the dsi-staging driver.
>
All of the downstream changes are in the mtp-testing branch of the
dpu-staging tree. The on-list patches are in the for-next-staging, and
the
On Fri, Feb 23, 2018 at 09:24:10AM -0500, Rob Clark wrote:
> On Fri, Feb 23, 2018 at 9:00 AM, Liviu Dudau wrote:
> > Hi Rob,
> >
> > On Fri, Feb 23, 2018 at 08:17:51AM -0500, Rob Clark wrote:
> >> From: Brian Starkey
> >>
> >> Writeback connectors
On Fri, Feb 23, 2018 at 9:00 AM, Liviu Dudau wrote:
> Hi Rob,
>
> On Fri, Feb 23, 2018 at 08:17:51AM -0500, Rob Clark wrote:
>> From: Brian Starkey
>>
>> Writeback connectors represent writeback engines which can write the
>> CRTC output to a memory
In a way, based on the original writeback patch from Jilai Wang, but a
lot has shifted around since then.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/Makefile | 1 +
drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c | 23 +-
(Sorry, meant to send this earlier, but got distracted on other things)
The first two patches are Brian Starkey's earlier writeback-connector
patches, with very minor rebasing to drm-next/v4.16-rc1, plus one small
addition to add atomic_commit() vfunc to the connector helpers, so that
writeback
Looks good. Can you point us to the fix done in the dsi-staging driver.
Thanks
Abhinav
-Original Message-
From: Rob Clark [mailto:robdcl...@gmail.com]
Sent: Thursday, February 22, 2018 11:49 AM
To: Sean Paul
Cc: freedreno ;
23 matches
Mail list logo