From: Adam Jackson <ajax@redhat.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Daniel Tang <dt.tangr@gmail.com>,
Fabian Vogt <fabian@ritter-vogt.de>
Cc: linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] RFT: drm/pl111: Support grayscale
Date: Tue, 23 Jul 2019 13:25:35 -0400 [thread overview]
Message-ID: <9c9b77b3b76e7a7e87c7c3d9076a8339362157bd.camel@redhat.com> (raw)
In-Reply-To: <20190723133755.22677-2-linus.walleij@linaro.org>
On Tue, 2019-07-23 at 15:37 +0200, Linus Walleij wrote:
> Migrating the TI nspire calculators to use the PL111 driver for
> framebuffer requires grayscale support for the elder panel
> which uses 8bit grayscale only.
>
> DRM does not support 8bit grayscale framebuffers in memory,
> but by defining the bus format to be MEDIA_BUS_FMT_Y8_1X8 we
> can get the hardware to turn on a grayscaling feature and
> convert the RGB framebuffer to grayscale for us.
What's wrong with DRM_FORMAT_R8? Yes the hardware is not really
"redscale", but it's still a single color channel and there's not
really any ambiguity.
- ajax
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-23 17:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 13:37 [PATCH 0/3] RFT: PL111 DRM conversion of nspire Linus Walleij
2019-07-23 13:37 ` [PATCH 1/3] RFT: drm/pl111: Support grayscale Linus Walleij
2019-07-23 15:19 ` Fabian Vogt
2019-07-24 12:33 ` Linus Walleij
2019-07-25 19:26 ` Fabian Vogt
2019-08-03 9:51 ` Linus Walleij
2019-08-04 20:13 ` Fabian Vogt
2019-07-23 16:22 ` [1/3] " David Lechner
2019-07-23 17:25 ` Adam Jackson [this message]
2019-07-23 21:06 ` [PATCH 1/3] " Daniel Vetter
2019-07-24 12:52 ` Linus Walleij
2019-07-24 14:06 ` Daniel Vetter
2019-07-23 13:37 ` [PATCH 2/3] RTF: drm/panel: simple: Add TI nspire panels Linus Walleij
2019-07-23 17:54 ` Sam Ravnborg
2019-07-24 13:58 ` Linus Walleij
2019-07-24 18:53 ` Sam Ravnborg
2019-07-23 13:37 ` [PATCH 3/3] RFT: ARM: nspire: Move CLCD set-up to device tree Linus Walleij
2019-07-23 18:10 ` [PATCH 0/3] RFT: PL111 DRM conversion of nspire Sam Ravnborg
2019-07-24 12:28 ` Linus Walleij
2019-07-24 12:47 ` Pawel Moll
2019-07-24 12:53 ` 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=9c9b77b3b76e7a7e87c7c3d9076a8339362157bd.camel@redhat.com \
--to=ajax@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dt.tangr@gmail.com \
--cc=fabian@ritter-vogt.de \
--cc=linus.walleij@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).