From: Sandy Huang <hjc@rock-chips.com>
To: dri-devel@lists.freedesktop.org, Dave Airlie <airlied@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: hjc@rock-chips.com, virtualization@lists.linux-foundation.org,
spice-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 28/36] drm/qxl: use bpp instead of cpp for drm_format_info
Date: Mon, 23 Sep 2019 20:53:01 +0800 [thread overview]
Message-ID: <1569243189-183445-3-git-send-email-hjc@rock-chips.com> (raw)
In-Reply-To: <1569243189-183445-1-git-send-email-hjc@rock-chips.com>
cpp[BytePerPlane] can't describe the 10bit data format correctly,
So we use bpp[BitPerPlane] to instead cpp.
Signed-off-by: Sandy Huang <hjc@rock-chips.com>
---
drivers/gpu/drm/qxl/qxl_draw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/qxl/qxl_draw.c b/drivers/gpu/drm/qxl/qxl_draw.c
index 5bebf1e..71c18e6 100644
--- a/drivers/gpu/drm/qxl/qxl_draw.c
+++ b/drivers/gpu/drm/qxl/qxl_draw.c
@@ -141,7 +141,7 @@ void qxl_draw_dirty_fb(struct qxl_device *qdev,
struct qxl_rect *rects;
int stride = fb->pitches[0];
/* depth is not actually interesting, we don't mask with it */
- int depth = fb->format->cpp[0] * 8;
+ int depth = fb->format->bpp[0];
uint8_t *surface_base;
struct qxl_release *release;
struct qxl_bo *clips_bo;
--
2.7.4
next prev parent reply other threads:[~2019-09-23 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 12:52 [PATCH 26/36] drm/vboxvideo: " Sandy Huang
2019-09-23 12:53 ` [PATCH 27/36] drm/pl111: " Sandy Huang
2019-09-23 12:53 ` Sandy Huang [this message]
2019-09-23 12:53 ` [PATCH 29/36] drm/ingenic: " Sandy Huang
2019-09-25 14:50 ` Paul Cercueil
2019-09-23 12:53 ` [PATCH 30/36] drm/sti: " Sandy Huang
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=1569243189-183445-3-git-send-email-hjc@rock-chips.com \
--to=hjc@rock-chips.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spice-devel@lists.freedesktop.org \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®