From: Tommy Haung <tommy_huang@aspeedtech.com>
To: <joel@jms.id.au>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<robh+dt@kernel.org>, <andrew@aj.id.au>,
<linux-aspeed@lists.ozlabs.org>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <BMC-SW@aspeedtech.com>
Subject: [PATCH v1 0/2] Add 1024x768 timing for AST2600
Date: Fri, 4 Mar 2022 14:31:35 +0800 [thread overview]
Message-ID: <20220304063137.12970-1-tommy_huang@aspeedtech.com> (raw)
v1:
Add 1024x768@70Hz for AST2600 soc display timing selection.
Add gfx flag for future usage.
Testing steps:
1. Add below config to turn VT and LOGO on.
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
CONFIG_LDISC_AUTOLOAD=y
CONFIG_DEVMEM=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_CLUT224=y
2. The Linux logo will be shown on the screen, when the BMC boot in Linux.
3. Check the display mode is 1024x768@70Hz at AST2600.
4. Check the display mode is 800x600@60Hz at AST2500.
Tommy Haung (2):
drm/aspeed: Add gfx flags and clock selection for AST2600
drm/aspeed: Add 1024x768 mode for AST2600
drivers/gpu/drm/aspeed/aspeed_gfx.h | 15 ++++++++++
drivers/gpu/drm/aspeed/aspeed_gfx_crtc.c | 35 ++++++++++++++++++++++++
drivers/gpu/drm/aspeed/aspeed_gfx_drv.c | 20 ++++++++++++--
drivers/gpu/drm/aspeed/aspeed_gfx_out.c | 14 +++++++++-
4 files changed, 81 insertions(+), 3 deletions(-)
--
2.17.1
next reply other threads:[~2022-03-04 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 6:31 Tommy Haung [this message]
2022-03-04 6:31 ` [PATCH v1 1/2] drm/aspeed: Add gfx flags and clock selection for AST2600 Tommy Haung
2022-03-04 6:31 ` [PATCH v1 2/2] drm/aspeed: Add 1024x768 mode " Tommy Haung
2022-04-26 3:27 ` Joel Stanley
2022-04-26 5:20 ` Tommy Huang
2022-04-26 7:47 ` Joel Stanley
2022-04-26 8:28 ` Tommy Huang
2022-06-07 1:30 ` Tommy 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=20220304063137.12970-1-tommy_huang@aspeedtech.com \
--to=tommy_huang@aspeedtech.com \
--cc=BMC-SW@aspeedtech.com \
--cc=airlied@linux.ie \
--cc=andrew@aj.id.au \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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).