From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5 v2] drm/pl111: Support variants with broken VBLANK
Date: Sat, 03 Feb 2018 15:44:26 -0800 [thread overview]
Message-ID: <87efm1bput.fsf@anholt.net> (raw)
In-Reply-To: <20180201125513.5482-5-linus.walleij@linaro.org>
Linus Walleij <linus.walleij@linaro.org> writes:
> The early Integrator CLCD synthesized in the Integrator CP and
> IM-PD1 FPGAs are broken: their vertical and next base interrupts
> are not functional. Support these variants by simply disabling
> the use of the vblank interrupt on these variants.
I do wonder if we just have the vblank interrupt number wrong or
something for Integrator. However, let's get to at least functional
parity with fbdev before we worry too much about the new features that
DRM can bring us.
The remainder of this series is also:
Reviewed-by: Eric Anholt <eric@anholt.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180203/1d6c2089/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Eric Anholt <eric@anholt.net>
To: Linus Walleij <linus.walleij@linaro.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>
Cc: linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/5 v2] drm/pl111: Support variants with broken VBLANK
Date: Sat, 03 Feb 2018 15:44:26 -0800 [thread overview]
Message-ID: <87efm1bput.fsf@anholt.net> (raw)
In-Reply-To: <20180201125513.5482-5-linus.walleij@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 607 bytes --]
Linus Walleij <linus.walleij@linaro.org> writes:
> The early Integrator CLCD synthesized in the Integrator CP and
> IM-PD1 FPGAs are broken: their vertical and next base interrupts
> are not functional. Support these variants by simply disabling
> the use of the vblank interrupt on these variants.
I do wonder if we just have the vblank interrupt number wrong or
something for Integrator. However, let's get to at least functional
parity with fbdev before we worry too much about the new features that
DRM can bring us.
The remainder of this series is also:
Reviewed-by: Eric Anholt <eric@anholt.net>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-02-03 23:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 12:55 [PATCH 0/5 v2] PL111 Integrator and Versatile support Linus Walleij
2018-02-01 12:55 ` Linus Walleij
2018-02-01 12:55 ` [PATCH 1/5 v2] drm/pl111: Properly detect the ARM PL110 variants Linus Walleij
2018-02-01 12:55 ` Linus Walleij
2018-02-02 20:51 ` Eric Anholt
2018-02-02 20:51 ` Eric Anholt
2018-02-01 12:55 ` [PATCH 2/5 v2] drm/pl111: Handle the Versatile RGB/BGR565 mode Linus Walleij
2018-02-01 12:55 ` Linus Walleij
2018-02-01 12:55 ` [PATCH 3/5 v2] drm/pl111: Support variants with broken clock divider Linus Walleij
2018-02-01 12:55 ` Linus Walleij
2018-02-01 12:55 ` [PATCH 4/5 v2] drm/pl111: Support variants with broken VBLANK Linus Walleij
2018-02-01 12:55 ` Linus Walleij
2018-02-03 23:44 ` Eric Anholt [this message]
2018-02-03 23:44 ` Eric Anholt
2018-02-06 9:37 ` Linus Walleij
2018-02-06 9:37 ` Linus Walleij
2018-02-01 12:55 ` [PATCH 5/5 v2] drm/pl111: Support multiple endpoints on the CLCD Linus Walleij
2018-02-01 12:55 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efm1bput.fsf@anholt.net \
--to=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.