2013/10/28 Sean Paul :
> Hi Inki,
> I noticed that you merged "drm/exynos: change callback argument of sub
> driver with device" to your tree without posting it to me, or
> dri-devel, first. I think it would have been prudent to send for
> review/comments considering th
>
>> to DT nodes, but it isn't essential. So I'd like to move away from the
>> 1:1 DT node/driver
>> model as it seriously over complicates things. We have agreed we
>> should possibly add
>> a display virtual node in the DT bindings for a single driver to use
>> as a binding point.
>
> Got it and
Hi Dave,
2013/10/29 Dave Airlie :
> On Tue, Oct 29, 2013 at 12:56 PM, Inki Dae wrote:
>> Hi,
>>
>> 2013/10/29 Olof Johansson :
>>> On Mon, Oct 28, 2013 at 6:35 AM, Inki Dae wrote:
This patch makes callback funtions of each sub driver to be called
with device object instead of display
On Tue, Oct 29, 2013 at 12:56 PM, Inki Dae wrote:
> Hi,
>
> 2013/10/29 Olof Johansson :
>> On Mon, Oct 28, 2013 at 6:35 AM, Inki Dae wrote:
>>> This patch makes callback funtions of each sub driver to be called
>>> with device object instead of display and manager.
>>>
>>> Exynos drm framework
Hi,
2013/10/29 Olof Johansson :
> On Mon, Oct 28, 2013 at 6:35 AM, Inki Dae wrote:
>> This patch makes callback funtions of each sub driver to be called
>> with device object instead of display and manager.
>>
>> Exynos drm framework doesn't need to pass a manager or a display
>> when calling
2013/10/28 Sean Paul :
> On Mon, Oct 28, 2013 at 9:35 AM, Inki Dae wrote:
>> This patch makes callback funtions of each sub driver to be called
>> with device object instead of display and manager.
>>
>> Exynos drm framework doesn't need to pass a manager or a display
>> when calling callback
On Oct 29, 2013 8:16 AM, "Inki Dae" wrote:
>
> 2013/10/28 Sean Paul :
> > Hi Inki,
> > I noticed that you merged "drm/exynos: change callback argument of sub
> > driver with device" to your tree without posting it to me, or
> > dri-devel,
This patch makes callback funtions of each sub driver to be called
with device object instead of display and manager.
Exynos drm framework doesn't need to pass a manager or a display
when calling callback function of each sub driver, and each sub
driver can get its own context from device object.
On Mon, Oct 28, 2013 at 9:35 AM, Inki Dae wrote:
> This patch makes callback funtions of each sub driver to be called
> with device object instead of display and manager.
>
> Exynos drm framework doesn't need to pass a manager or a display
> when calling callback function of each sub driver, and
Hi Inki,
I noticed that you merged "drm/exynos: change callback argument of sub
driver with device" to your tree without posting it to me, or
dri-devel, first. I think it would have been prudent to send for
review/comments considering that:
a) we don't agree on this, and were in discus
On Mon, Oct 28, 2013 at 6:35 AM, Inki Dae wrote:
> This patch makes callback funtions of each sub driver to be called
> with device object instead of display and manager.
>
> Exynos drm framework doesn't need to pass a manager or a display
> when calling callback function of each sub driver, and
11 matches
Mail list logo
