Re: [RFC PULL] Add Display Support for Qualcomm SDM845

On Wed, Feb 14, 2018 at 2:08 PM, Rob Clark wrote: > On Wed, Feb 14, 2018 at 1:17 PM, jsanka wrote: >> On 2/13/2018 12:00 PM, Rob Clark wrote: >>> >>> - It looks like, as was the case with mdp4/mdp5 (and really most other >>> hw) >>> there are

Re: [RFC PULL] Add Display Support for Qualcomm SDM845

On Tue, Feb 13, 2018 at 03:00:09PM -0500, Rob Clark wrote: > On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote: > > Hi dri-devel, > > Qualcomm has been working for the past few weeks on forward porting their > > downstream drm driver from 4.14 to mainline. Please consider

Re: [RFC PULL] Add Display Support for Qualcomm SDM845

On Tue, Feb 13, 2018 at 1:18 PM, Sean Paul wrote: > Hi dri-devel, > Qualcomm has been working for the past few weeks on forward porting their > downstream drm driver from 4.14 to mainline. Please consider this PR as a > request for review, rather than an attempt at

Re: [Freedreno] [RFC PULL] Add Display Support for Qualcomm SDM845

On Tue, Feb 13, 2018 at 02:18:13PM -0500, Sean Paul wrote: > Hi dri-devel, > Qualcomm has been working for the past few weeks on forward porting their > downstream drm driver from 4.14 to mainline. Please consider this PR as a > request for review, rather than an attempt at mainlining the code as

Re: [RFC PULL] Add Display Support for Qualcomm SDM845

On 2/13/2018 12:00 PM, Rob Clark wrote: On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote: Hi dri-devel, Qualcomm has been working for the past few weeks on forward porting their downstream drm driver from 4.14 to mainline. Please consider this PR as a request for

Re: [RFC PULL] Add Display Support for Qualcomm SDM845

On Tue, Feb 13, 2018 at 3:00 PM, Rob Clark wrote: > On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote: >> Hi dri-devel, >> Qualcomm has been working for the past few weeks on forward porting their >> downstream drm driver from 4.14 to mainline. Please

Re: [RFC PULL] Add Display Support for Qualcomm SDM845

Hi, On 14 February 2018 at 13:50, Sean Paul wrote: > On Wed, Feb 14, 2018 at 07:22:53AM -0500, Rob Clark wrote: >> On Wed, Feb 14, 2018 at 3:30 AM, Daniel Stone wrote: >> > This one I guess you can't get around though. Can they still run from >> >

Re: [RFC PULL] Add Display Support for Qualcomm SDM845

On Wed, Feb 14, 2018 at 3:30 AM, Daniel Stone wrote: > Hi Rob, > > On 13 February 2018 at 20:00, Rob Clark wrote: >> On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote: >>> Qualcomm has been working for the past few weeks on

Re: [RFC PULL] Add Display Support for Qualcomm SDM845

Hi Rob, On 13 February 2018 at 20:00, Rob Clark wrote: > On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote: >> Qualcomm has been working for the past few weeks on forward porting their >> downstream drm driver from 4.14 to mainline. Please consider

Re: [Freedreno] [RFC PULL] Add Display Support for Qualcomm SDM845

On Tue, Feb 13, 2018 at 7:02 PM, Jordan Crouse wrote: > On Tue, Feb 13, 2018 at 02:18:13PM -0500, Sean Paul wrote: >> Hi dri-devel, >> Qualcomm has been working for the past few weeks on forward porting their >> downstream drm driver from 4.14 to mainline. Please consider

Re: [Freedreno] [RFC PULL] Add Display Support for Qualcomm SDM845

On Tue, Feb 13, 2018 at 02:18:13PM -0500, Sean Paul wrote: > Hi dri-devel, > Qualcomm has been working for the past few weeks on forward porting their > downstream drm driver from 4.14 to mainline. Please consider this PR as a > request for review, rather than an attempt at mainlining the code as

Re: [RFC PULL] Add Display Support for Qualcomm SDM845

On Tue, Feb 13, 2018 at 2:18 PM, Sean Paul wrote: > Hi dri-devel, > Qualcomm has been working for the past few weeks on forward porting their > downstream drm driver from 4.14 to mainline. Please consider this PR as a > request for review, rather than an attempt at

[RFC PULL] Add Display Support for Qualcomm SDM845

Hi dri-devel, Qualcomm has been working for the past few weeks on forward porting their downstream drm driver from 4.14 to mainline. Please consider this PR as a request for review, rather than an attempt at mainlining the code as it currently stands. The goal is get this driver in shape over the