Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 9 Jan 2019 08:07:46 +0100
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Roman Kiryanov <rkir@google.com>
Cc:     linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] drivers: platform: goldfish: goldfish_sync: add a
 driver
Message-ID: <20190109070746.GA20817@kroah.com>
References: <20190107185039.190919-1-rkir@google.com>
 <20190107185039.190919-3-rkir@google.com>
 <20190108121335.GA3349@kroah.com>
 <CAOGAQepF4R8ry+irPxeL=G0yFqhxRmkMWd_iPGYOTFzdZSj6iQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAOGAQepF4R8ry+irPxeL=G0yFqhxRmkMWd_iPGYOTFzdZSj6iQ@mail.gmail.com>
User-Agent: Mutt/1.11.2 (2019-01-07)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Jan 08, 2019 at 04:48:02PM -0800, Roman Kiryanov wrote:
> > Also, why is this driver needed at all?  Why can't you use the "normal"
> > drm sync api interface?  Why write a custom ioctl driver just for this
> > one kernel interface?
> 
> This driver allows us to talk to host's sync api.

That describes what your code does, yes, but you did not answer my
question at all.  Why do you need this?  What are you trying to do?  And
why is this so different from any other drm driver?

thanks,

greg k-h