From: purofle <purofle@gmail.com>
To: linux-fbdev@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org, linux-staging@lists.linux.dev,
gregkh@linuxfoundation.org, purofle <purofle@gmail.com>
Subject: [PATCH] staging: fbtft: fb_st7789v: support setting offset
Date: Sat, 6 Apr 2024 00:57:47 +0800 [thread overview]
Message-ID: <20240405165747.93377-1-purofle@gmail.com> (raw)
Some screen sizes using st7789v chips are different from 240x320,
and offsets need to be set to display all images properly.
Signed-off-by: purofle <purofle@gmail.com>
---
drivers/staging/fbtft/fb_st7789v.c | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/drivers/staging/fbtft/fb_st7789v.c b/drivers/staging/fbtft/fb_st7789v.c
index 861a15414..d47ab4262 100644
--- a/drivers/staging/fbtft/fb_st7789v.c
+++ b/drivers/staging/fbtft/fb_st7789v.c
@@ -30,6 +30,12 @@
#define HSD20_IPS 1
+#define WIDTH 240
+#define HEIGHT 320
+
+#define LEFT_OFFSET 0
+#define TOP_OFFSET 0
+
/**
* enum st7789v_command - ST7789V display controller commands
*
@@ -349,6 +355,21 @@ static int set_gamma(struct fbtft_par *par, u32 *curves)
return 0;
}
+static void set_addr_win(struct fbtft_par *par, int xs, int ys, int xe, int ye)
+{
+ unsigned int x = xs + TOP_OFFSET, y = xe + TOP_OFFSET;
+
+ write_reg(par, MIPI_DCS_SET_COLUMN_ADDRESS, (x >> 8) & 0xFF, xs & 0xFF,
+ (y >> 8) & 0xFF, xe & 0xFF);
+
+ x = ys + LEFT_OFFSET, y = ye + LEFT_OFFSET;
+
+ write_reg(par, MIPI_DCS_SET_PAGE_ADDRESS, (x >> 8) & 0xFF, ys & 0xFF,
+ (y >> 8) & 0xFF, ye & 0xFF);
+
+ write_reg(par, MIPI_DCS_WRITE_MEMORY_START);
+}
+
/**
* blank() - blank the display
*
@@ -379,6 +400,7 @@ static struct fbtft_display display = {
.set_var = set_var,
.set_gamma = set_gamma,
.blank = blank,
+ .set_addr_win = set_addr_win,
},
};
--
2.44.0
next reply other threads:[~2024-04-05 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 16:57 purofle [this message]
2024-04-09 15:49 ` [PATCH] staging: fbtft: fb_st7789v: support setting offset Greg KH
2024-04-09 17:28 ` Yuguo Pei
2024-04-09 17:36 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2024-04-09 16:39 purofle
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=20240405165747.93377-1-purofle@gmail.com \
--to=purofle@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).