Hi Philipp,
thanks for the quick reply.
On Wed, 8 Jul 2020 at 10:31, Philipp Zabel wrote:
> Could this be just a panel getting confused because the pixel clock is
> disabled, or is there really an issue with the IPU? Have you tried just
> keeping clk_di_pixel enabled in ipu_di_disable(), but co
Hi Lucas,
> Am Mittwoch, den 20.05.2020, 12:10 +0200 schrieb Martin Fuzzey:
> What's the use-case where you did hit this issue? mmap'ing of imported
> buffers through the etnaviv DRM device is currently not well defined
> and I was pondering the idea of forbidding it completely by not
> returning
On Wed, 13 May 2020 at 08:07, Sascha Hauer wrote:
>
> On Tue, May 12, 2020 at 01:32:26AM +0800, Robin Gong wrote:
> > This reverts commit d288bddd8374e0a043ac9dde64a1ae6a09411d74, since
> > 'context_loaded' finally removed.
> >
> > Signed-off-by: Robin Gong
> > ---
>
> I think this can safely be
On 26 May 2017 at 21:40, Luis R. Rodriguez wrote:
> On Thu, May 25, 2017 at 10:28:38AM +0200, Fuzzey, Martin wrote:
>> On 25 May 2017 at 06:13, Andy Lutomirski wrote:
>> >>>
>> >>> Can you give a simple example of what's going on and why it matters?
&
On 25 May 2017 at 06:13, Andy Lutomirski wrote:
>>>
>>> Can you give a simple example of what's going on and why it matters?
>>>
Here is the use case in which I ran into this problem.
I have a driver which does request_firmware() when a write() is done
to a sysfs file.
The write() was being do
Hi Philipp,
On 10 February 2014 14:16, Philipp Zabel wrote:
> Hi Martin,
>
> Am Montag, den 10.02.2014, 13:54 +0100 schrieb Martin Fuzzey:
>> This driver allows GPIO lines to be used as reset signals.
>> It has two main use cases:
>>
>> 1) Allow drivers to reset their hardware via a GPIO line in
6 matches
Mail list logo