On Wed, Jul 23, 2014 at 11:18 AM, Ajay kumar wrote:
> On Wed, Jul 23, 2014 at 8:12 PM, Sean Paul wrote:
>> On Wed, Jul 23, 2014 at 7:22 AM, Ajay kumar wrote:
>>> Sean,
>>>
>>> On Tue, Jul 22, 2014 at 8:29 PM, Sean Paul wrote:
On Thu, Jul 17, 2014 at 4:43 PM, Ajay Kumar
wrote:
>
On Wed, Jul 23, 2014 at 8:12 PM, Sean Paul wrote:
> On Wed, Jul 23, 2014 at 7:22 AM, Ajay kumar wrote:
>> Sean,
>>
>> On Tue, Jul 22, 2014 at 8:29 PM, Sean Paul wrote:
>>> On Thu, Jul 17, 2014 at 4:43 PM, Ajay Kumar
>>> wrote:
Move the DP training and video enable from the hotplug handler
Sean,
On Tue, Jul 22, 2014 at 8:29 PM, Sean Paul wrote:
> On Thu, Jul 17, 2014 at 4:43 PM, Ajay Kumar
> wrote:
>> Move the DP training and video enable from the hotplug handler into
>> a seperate function and call the same during dpms ON.
>>
>> With existing code, DP HPD should be generated jus
On Wed, Jul 23, 2014 at 7:22 AM, Ajay kumar wrote:
> Sean,
>
> On Tue, Jul 22, 2014 at 8:29 PM, Sean Paul wrote:
>> On Thu, Jul 17, 2014 at 4:43 PM, Ajay Kumar
>> wrote:
>>> Move the DP training and video enable from the hotplug handler into
>>> a seperate function and call the same during dpms
On Thu, Jul 17, 2014 at 4:43 PM, Ajay Kumar wrote:
> Move the DP training and video enable from the hotplug handler into
> a seperate function and call the same during dpms ON.
>
> With existing code, DP HPD should be generated just few ms before
> calling enable_irq in dp_poweron.
>
> This patch
Move the DP training and video enable from the hotplug handler into
a seperate function and call the same during dpms ON.
With existing code, DP HPD should be generated just few ms before
calling enable_irq in dp_poweron.
This patch removes that stringent time constraint.
Signed-off-by: Ajay Kum