Re: [PATCH v2 4/7] drivers/base: Add interface framework

2014-05-20 Thread Andrzej Hajda
Hi Thierry, Greg, On 05/15/2014 10:53 AM, Thierry Reding wrote: > On Tue, May 13, 2014 at 05:32:15PM -0700, Greg Kroah-Hartman wrote: >> On Tue, May 13, 2014 at 07:57:13PM +0200, Daniel Vetter wrote: >>> On Tue, May 13, 2014 at 05:30:47PM +0200, Thierry Reding wrote: From: Thierry Reding >>

Re: [PATCH v2 4/7] drivers/base: Add interface framework

2014-05-15 Thread Thierry Reding
On Tue, May 13, 2014 at 05:32:15PM -0700, Greg Kroah-Hartman wrote: > On Tue, May 13, 2014 at 07:57:13PM +0200, Daniel Vetter wrote: > > On Tue, May 13, 2014 at 05:30:47PM +0200, Thierry Reding wrote: > > > From: Thierry Reding > > > > > > Some drivers, such as graphics drivers in the DRM subsyst

Re: [PATCH v2 4/7] drivers/base: Add interface framework

2014-05-14 Thread Greg Kroah-Hartman
On Wed, May 14, 2014 at 04:37:19PM +0200, Daniel Vetter wrote: > On Tue, May 13, 2014 at 05:32:15PM -0700, Greg Kroah-Hartman wrote: > > On Tue, May 13, 2014 at 07:57:13PM +0200, Daniel Vetter wrote: > > > On Tue, May 13, 2014 at 05:30:47PM +0200, Thierry Reding wrote: > > > > From: Thierry Reding

Re: [PATCH v2 4/7] drivers/base: Add interface framework

2014-05-14 Thread Thierry Reding
On Wed, May 14, 2014 at 04:34:21PM +0200, Daniel Vetter wrote: > On Tue, May 13, 2014 at 11:31:07PM +0200, Thierry Reding wrote: > > A different solution, which seems to be fairly common for DRM drivers > > for SoCs, is to instantiate a dummy device so that the DRM driver can > > bind to it. This c

Re: [PATCH v2 4/7] drivers/base: Add interface framework

2014-05-14 Thread Daniel Vetter
On Tue, May 13, 2014 at 05:32:15PM -0700, Greg Kroah-Hartman wrote: > On Tue, May 13, 2014 at 07:57:13PM +0200, Daniel Vetter wrote: > > On Tue, May 13, 2014 at 05:30:47PM +0200, Thierry Reding wrote: > > > From: Thierry Reding > > > > > > Some drivers, such as graphics drivers in the DRM subsyst

Re: [PATCH v2 4/7] drivers/base: Add interface framework

2014-05-14 Thread Daniel Vetter
On Tue, May 13, 2014 at 11:31:07PM +0200, Thierry Reding wrote: > A different solution, which seems to be fairly common for DRM drivers > for SoCs, is to instantiate a dummy device so that the DRM driver can > bind to it. This can happen in two forms: add the dummy device directly > in device tree

Re: [PATCH v2 4/7] drivers/base: Add interface framework

2014-05-13 Thread Greg Kroah-Hartman
On Tue, May 13, 2014 at 07:57:13PM +0200, Daniel Vetter wrote: > On Tue, May 13, 2014 at 05:30:47PM +0200, Thierry Reding wrote: > > From: Thierry Reding > > > > Some drivers, such as graphics drivers in the DRM subsystem, do not have > > a real device that they can bind to. They are often compos

Re: [PATCH v2 4/7] drivers/base: Add interface framework

2014-05-13 Thread Thierry Reding
On Tue, May 13, 2014 at 07:57:13PM +0200, Daniel Vetter wrote: > On Tue, May 13, 2014 at 05:30:47PM +0200, Thierry Reding wrote: > > From: Thierry Reding > > > > Some drivers, such as graphics drivers in the DRM subsystem, do not have > > a real device that they can bind to. They are often compos

Re: [PATCH v2 4/7] drivers/base: Add interface framework

2014-05-13 Thread Daniel Vetter
On Tue, May 13, 2014 at 05:30:47PM +0200, Thierry Reding wrote: > From: Thierry Reding > > Some drivers, such as graphics drivers in the DRM subsystem, do not have > a real device that they can bind to. They are often composed of several > devices, each having their own driver. The master/compone