drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
/*
|
|
|
|
* Copyright 2012 Red Hat Inc.
|
|
|
|
*
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a
|
|
|
|
* copy of this software and associated documentation files (the
|
|
|
|
* "Software"), to deal in the Software without restriction, including
|
|
|
|
* without limitation the rights to use, copy, modify, merge, publish,
|
|
|
|
* distribute, sub license, and/or sell copies of the Software, and to
|
|
|
|
* permit persons to whom the Software is furnished to do so, subject to
|
|
|
|
* the following conditions:
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
|
|
|
|
* THE COPYRIGHT HOLDERS, AUTHORS AND/OR ITS SUPPLIERS BE LIABLE FOR ANY CLAIM,
|
|
|
|
* DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
|
|
|
|
* OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
|
|
|
|
* USE OR OTHER DEALINGS IN THE SOFTWARE.
|
|
|
|
*
|
|
|
|
* The above copyright notice and this permission notice (including the
|
|
|
|
* next paragraph) shall be included in all copies or substantial portions
|
|
|
|
* of the Software.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
/*
|
|
|
|
* Authors: Dave Airlie <airlied@redhat.com>
|
|
|
|
*/
|
|
|
|
|
2012-10-02 21:01:07 +04:00
|
|
|
#include <drm/drmP.h>
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
#include "ast_drv.h"
|
|
|
|
|
|
|
|
#include "ast_dram_tables.h"
|
|
|
|
|
|
|
|
static void ast_init_dram_2300(struct drm_device *dev);
|
|
|
|
|
2014-09-04 11:50:11 +04:00
|
|
|
void ast_enable_vga(struct drm_device *dev)
|
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
|
|
|
|
ast_io_write8(ast, AST_IO_VGA_ENABLE_PORT, 0x01);
|
|
|
|
ast_io_write8(ast, AST_IO_MISC_PORT_WRITE, 0x01);
|
|
|
|
}
|
|
|
|
|
|
|
|
void ast_enable_mmio(struct drm_device *dev)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
|
2014-09-04 11:50:11 +04:00
|
|
|
ast_set_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xa1, 0xff, 0x04);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
|
|
|
|
2014-09-04 11:50:11 +04:00
|
|
|
|
|
|
|
bool ast_is_vga_enabled(struct drm_device *dev)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
u8 ch;
|
|
|
|
|
|
|
|
if (ast->chip == AST1180) {
|
|
|
|
/* TODO 1180 */
|
|
|
|
} else {
|
2014-09-04 11:50:11 +04:00
|
|
|
ch = ast_io_read8(ast, AST_IO_VGA_ENABLE_PORT);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (ch) {
|
|
|
|
ast_open_key(ast);
|
|
|
|
ch = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xb6, 0xff);
|
|
|
|
return ch & 0x04;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const u8 extreginfo[] = { 0x0f, 0x04, 0x1c, 0xff };
|
|
|
|
static const u8 extreginfo_ast2300a0[] = { 0x0f, 0x04, 0x1c, 0xff };
|
|
|
|
static const u8 extreginfo_ast2300[] = { 0x0f, 0x04, 0x1f, 0xff };
|
|
|
|
|
|
|
|
static void
|
|
|
|
ast_set_def_ext_reg(struct drm_device *dev)
|
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
u8 i, index, reg;
|
|
|
|
const u8 *ext_reg_info;
|
|
|
|
|
|
|
|
/* reset scratch */
|
|
|
|
for (i = 0x81; i <= 0x8f; i++)
|
|
|
|
ast_set_index_reg(ast, AST_IO_CRTC_PORT, i, 0x00);
|
|
|
|
|
2014-03-28 03:18:45 +04:00
|
|
|
if (ast->chip == AST2300 || ast->chip == AST2400) {
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (dev->pdev->revision >= 0x20)
|
|
|
|
ext_reg_info = extreginfo_ast2300;
|
|
|
|
else
|
|
|
|
ext_reg_info = extreginfo_ast2300a0;
|
|
|
|
} else
|
|
|
|
ext_reg_info = extreginfo;
|
|
|
|
|
|
|
|
index = 0xa0;
|
|
|
|
while (*ext_reg_info != 0xff) {
|
|
|
|
ast_set_index_reg_mask(ast, AST_IO_CRTC_PORT, index, 0x00, *ext_reg_info);
|
|
|
|
index++;
|
|
|
|
ext_reg_info++;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* disable standard IO/MEM decode if secondary */
|
|
|
|
/* ast_set_index_reg-mask(ast, AST_IO_CRTC_PORT, 0xa1, 0xff, 0x3); */
|
|
|
|
|
|
|
|
/* Set Ext. Default */
|
|
|
|
ast_set_index_reg_mask(ast, AST_IO_CRTC_PORT, 0x8c, 0x00, 0x01);
|
|
|
|
ast_set_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xb7, 0x00, 0x00);
|
|
|
|
|
|
|
|
/* Enable RAMDAC for A1 */
|
|
|
|
reg = 0x04;
|
2014-03-28 03:18:45 +04:00
|
|
|
if (ast->chip == AST2300 || ast->chip == AST2400)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
reg |= 0x20;
|
|
|
|
ast_set_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xb6, 0xff, reg);
|
|
|
|
}
|
|
|
|
|
2014-03-28 05:05:12 +04:00
|
|
|
u32 ast_mindwm(struct ast_private *ast, u32 r)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
{
|
2014-01-17 05:36:14 +04:00
|
|
|
uint32_t data;
|
|
|
|
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
ast_write32(ast, 0xf004, r & 0xffff0000);
|
|
|
|
ast_write32(ast, 0xf000, 0x1);
|
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
do {
|
|
|
|
data = ast_read32(ast, 0xf004) & 0xffff0000;
|
|
|
|
} while (data != (r & 0xffff0000));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return ast_read32(ast, 0x10000 + (r & 0x0000ffff));
|
|
|
|
}
|
|
|
|
|
2014-03-28 05:05:12 +04:00
|
|
|
void ast_moutdwm(struct ast_private *ast, u32 r, u32 v)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
{
|
2014-01-17 05:36:14 +04:00
|
|
|
uint32_t data;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
ast_write32(ast, 0xf004, r & 0xffff0000);
|
|
|
|
ast_write32(ast, 0xf000, 0x1);
|
2014-01-17 05:36:14 +04:00
|
|
|
do {
|
|
|
|
data = ast_read32(ast, 0xf004) & 0xffff0000;
|
|
|
|
} while (data != (r & 0xffff0000));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
ast_write32(ast, 0x10000 + (r & 0x0000ffff), v);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* AST2100/2150 DLL CBR Setting
|
|
|
|
*/
|
|
|
|
#define CBR_SIZE_AST2150 ((16 << 10) - 1)
|
|
|
|
#define CBR_PASSNUM_AST2150 5
|
|
|
|
#define CBR_THRESHOLD_AST2150 10
|
|
|
|
#define CBR_THRESHOLD2_AST2150 10
|
|
|
|
#define TIMEOUT_AST2150 5000000
|
|
|
|
|
|
|
|
#define CBR_PATNUM_AST2150 8
|
|
|
|
|
|
|
|
static const u32 pattern_AST2150[14] = {
|
|
|
|
0xFF00FF00,
|
|
|
|
0xCC33CC33,
|
|
|
|
0xAA55AA55,
|
|
|
|
0xFFFE0001,
|
|
|
|
0x683501FE,
|
|
|
|
0x0F1929B0,
|
|
|
|
0x2D0B4346,
|
|
|
|
0x60767F02,
|
|
|
|
0x6FBE36A6,
|
|
|
|
0x3A253035,
|
|
|
|
0x3019686D,
|
|
|
|
0x41C6167E,
|
|
|
|
0x620152BF,
|
|
|
|
0x20F050E0
|
|
|
|
};
|
|
|
|
|
|
|
|
static u32 mmctestburst2_ast2150(struct ast_private *ast, u32 datagen)
|
|
|
|
{
|
|
|
|
u32 data, timeout;
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000001 | (datagen << 3));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
timeout = 0;
|
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1e6e0070) & 0x40;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (++timeout > TIMEOUT_AST2150) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return 0xffffffff;
|
|
|
|
}
|
|
|
|
} while (!data);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000003 | (datagen << 3));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
timeout = 0;
|
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1e6e0070) & 0x40;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (++timeout > TIMEOUT_AST2150) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return 0xffffffff;
|
|
|
|
}
|
|
|
|
} while (!data);
|
2014-03-28 04:22:41 +04:00
|
|
|
data = (ast_mindwm(ast, 0x1e6e0070) & 0x80) >> 7;
|
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return data;
|
|
|
|
}
|
|
|
|
|
|
|
|
#if 0 /* unused in DDX driver - here for completeness */
|
|
|
|
static u32 mmctestsingle2_ast2150(struct ast_private *ast, u32 datagen)
|
|
|
|
{
|
|
|
|
u32 data, timeout;
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000005 | (datagen << 3));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
timeout = 0;
|
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1e6e0070) & 0x40;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (++timeout > TIMEOUT_AST2150) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return 0xffffffff;
|
|
|
|
}
|
|
|
|
} while (!data);
|
2014-03-28 04:22:41 +04:00
|
|
|
data = (ast_mindwm(ast, 0x1e6e0070) & 0x80) >> 7;
|
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return data;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
static int cbrtest_ast2150(struct ast_private *ast)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < 8; i++)
|
|
|
|
if (mmctestburst2_ast2150(ast, i))
|
|
|
|
return 0;
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int cbrscan_ast2150(struct ast_private *ast, int busw)
|
|
|
|
{
|
|
|
|
u32 patcnt, loop;
|
|
|
|
|
|
|
|
for (patcnt = 0; patcnt < CBR_PATNUM_AST2150; patcnt++) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e007c, pattern_AST2150[patcnt]);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
for (loop = 0; loop < CBR_PASSNUM_AST2150; loop++) {
|
|
|
|
if (cbrtest_ast2150(ast))
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
if (loop == CBR_PASSNUM_AST2150)
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static void cbrdlli_ast2150(struct ast_private *ast, int busw)
|
|
|
|
{
|
|
|
|
u32 dll_min[4], dll_max[4], dlli, data, passcnt;
|
|
|
|
|
|
|
|
cbr_start:
|
|
|
|
dll_min[0] = dll_min[1] = dll_min[2] = dll_min[3] = 0xff;
|
|
|
|
dll_max[0] = dll_max[1] = dll_max[2] = dll_max[3] = 0x0;
|
|
|
|
passcnt = 0;
|
|
|
|
|
|
|
|
for (dlli = 0; dlli < 100; dlli++) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0068, dlli | (dlli << 8) | (dlli << 16) | (dlli << 24));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = cbrscan_ast2150(ast, busw);
|
|
|
|
if (data != 0) {
|
|
|
|
if (data & 0x1) {
|
|
|
|
if (dll_min[0] > dlli)
|
|
|
|
dll_min[0] = dlli;
|
|
|
|
if (dll_max[0] < dlli)
|
|
|
|
dll_max[0] = dlli;
|
|
|
|
}
|
|
|
|
passcnt++;
|
|
|
|
} else if (passcnt >= CBR_THRESHOLD_AST2150)
|
|
|
|
goto cbr_start;
|
|
|
|
}
|
|
|
|
if (dll_max[0] == 0 || (dll_max[0]-dll_min[0]) < CBR_THRESHOLD_AST2150)
|
|
|
|
goto cbr_start;
|
|
|
|
|
|
|
|
dlli = dll_min[0] + (((dll_max[0] - dll_min[0]) * 7) >> 4);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0068, dlli | (dlli << 8) | (dlli << 16) | (dlli << 24));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
static void ast_init_dram_reg(struct drm_device *dev)
|
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
u8 j;
|
|
|
|
u32 data, temp, i;
|
|
|
|
const struct ast_dramstruct *dram_reg_info;
|
|
|
|
|
|
|
|
j = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xd0, 0xff);
|
|
|
|
|
|
|
|
if ((j & 0x80) == 0) { /* VGA only */
|
|
|
|
if (ast->chip == AST2000) {
|
|
|
|
dram_reg_info = ast2000_dram_table_data;
|
|
|
|
ast_write32(ast, 0xf004, 0x1e6e0000);
|
|
|
|
ast_write32(ast, 0xf000, 0x1);
|
|
|
|
ast_write32(ast, 0x10100, 0xa8);
|
|
|
|
|
|
|
|
do {
|
|
|
|
;
|
|
|
|
} while (ast_read32(ast, 0x10100) != 0xa8);
|
|
|
|
} else {/* AST2100/1100 */
|
|
|
|
if (ast->chip == AST2100 || ast->chip == 2200)
|
|
|
|
dram_reg_info = ast2100_dram_table_data;
|
|
|
|
else
|
|
|
|
dram_reg_info = ast1100_dram_table_data;
|
|
|
|
|
|
|
|
ast_write32(ast, 0xf004, 0x1e6e0000);
|
|
|
|
ast_write32(ast, 0xf000, 0x1);
|
|
|
|
ast_write32(ast, 0x12000, 0x1688A8A8);
|
|
|
|
do {
|
|
|
|
;
|
|
|
|
} while (ast_read32(ast, 0x12000) != 0x01);
|
|
|
|
|
|
|
|
ast_write32(ast, 0x10000, 0xfc600309);
|
|
|
|
do {
|
|
|
|
;
|
|
|
|
} while (ast_read32(ast, 0x10000) != 0x01);
|
|
|
|
}
|
|
|
|
|
|
|
|
while (dram_reg_info->index != 0xffff) {
|
|
|
|
if (dram_reg_info->index == 0xff00) {/* delay fn */
|
|
|
|
for (i = 0; i < 15; i++)
|
|
|
|
udelay(dram_reg_info->data);
|
|
|
|
} else if (dram_reg_info->index == 0x4 && ast->chip != AST2000) {
|
|
|
|
data = dram_reg_info->data;
|
|
|
|
if (ast->dram_type == AST_DRAM_1Gx16)
|
|
|
|
data = 0x00000d89;
|
|
|
|
else if (ast->dram_type == AST_DRAM_1Gx32)
|
|
|
|
data = 0x00000c8d;
|
|
|
|
|
|
|
|
temp = ast_read32(ast, 0x12070);
|
|
|
|
temp &= 0xc;
|
|
|
|
temp <<= 2;
|
|
|
|
ast_write32(ast, 0x10000 + dram_reg_info->index, data | temp);
|
|
|
|
} else
|
|
|
|
ast_write32(ast, 0x10000 + dram_reg_info->index, dram_reg_info->data);
|
|
|
|
dram_reg_info++;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* AST 2100/2150 DRAM calibration */
|
|
|
|
data = ast_read32(ast, 0x10120);
|
|
|
|
if (data == 0x5061) { /* 266Mhz */
|
|
|
|
data = ast_read32(ast, 0x10004);
|
|
|
|
if (data & 0x40)
|
|
|
|
cbrdlli_ast2150(ast, 16); /* 16 bits */
|
|
|
|
else
|
|
|
|
cbrdlli_ast2150(ast, 32); /* 32 bits */
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (ast->chip) {
|
|
|
|
case AST2000:
|
|
|
|
temp = ast_read32(ast, 0x10140);
|
|
|
|
ast_write32(ast, 0x10140, temp | 0x40);
|
|
|
|
break;
|
|
|
|
case AST1100:
|
|
|
|
case AST2100:
|
|
|
|
case AST2200:
|
|
|
|
case AST2150:
|
|
|
|
temp = ast_read32(ast, 0x1200c);
|
|
|
|
ast_write32(ast, 0x1200c, temp & 0xfffffffd);
|
|
|
|
temp = ast_read32(ast, 0x12040);
|
|
|
|
ast_write32(ast, 0x12040, temp | 0x40);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* wait ready */
|
|
|
|
do {
|
|
|
|
j = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xd0, 0xff);
|
|
|
|
} while ((j & 0x40) == 0);
|
|
|
|
}
|
|
|
|
|
|
|
|
void ast_post_gpu(struct drm_device *dev)
|
|
|
|
{
|
|
|
|
u32 reg;
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
|
|
|
|
pci_read_config_dword(ast->dev->pdev, 0x04, ®);
|
|
|
|
reg |= 0x3;
|
|
|
|
pci_write_config_dword(ast->dev->pdev, 0x04, reg);
|
|
|
|
|
|
|
|
ast_enable_vga(dev);
|
2014-09-04 11:50:11 +04:00
|
|
|
ast_enable_mmio(dev);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
ast_open_key(ast);
|
|
|
|
ast_set_def_ext_reg(dev);
|
|
|
|
|
2014-03-28 03:18:45 +04:00
|
|
|
if (ast->chip == AST2300 || ast->chip == AST2400)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
ast_init_dram_2300(dev);
|
|
|
|
else
|
|
|
|
ast_init_dram_reg(dev);
|
2014-03-28 05:05:12 +04:00
|
|
|
|
|
|
|
ast_init_3rdtx(dev);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
/* AST 2300 DRAM settings */
|
|
|
|
#define AST_DDR3 0
|
|
|
|
#define AST_DDR2 1
|
|
|
|
|
|
|
|
struct ast2300_dram_param {
|
|
|
|
u32 dram_type;
|
|
|
|
u32 dram_chipid;
|
|
|
|
u32 dram_freq;
|
|
|
|
u32 vram_size;
|
|
|
|
u32 odt;
|
|
|
|
u32 wodt;
|
|
|
|
u32 rodt;
|
|
|
|
u32 dram_config;
|
|
|
|
u32 reg_PERIOD;
|
|
|
|
u32 reg_MADJ;
|
|
|
|
u32 reg_SADJ;
|
|
|
|
u32 reg_MRS;
|
|
|
|
u32 reg_EMRS;
|
|
|
|
u32 reg_AC1;
|
|
|
|
u32 reg_AC2;
|
|
|
|
u32 reg_DQSIC;
|
|
|
|
u32 reg_DRV;
|
|
|
|
u32 reg_IOZ;
|
|
|
|
u32 reg_DQIDLY;
|
|
|
|
u32 reg_FREQ;
|
|
|
|
u32 madj_max;
|
|
|
|
u32 dll2_finetune_step;
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* DQSI DLL CBR Setting
|
|
|
|
*/
|
2014-01-17 05:36:14 +04:00
|
|
|
#define CBR_SIZE0 ((1 << 10) - 1)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
#define CBR_SIZE1 ((4 << 10) - 1)
|
|
|
|
#define CBR_SIZE2 ((64 << 10) - 1)
|
|
|
|
#define CBR_PASSNUM 5
|
|
|
|
#define CBR_PASSNUM2 5
|
|
|
|
#define CBR_THRESHOLD 10
|
|
|
|
#define CBR_THRESHOLD2 10
|
|
|
|
#define TIMEOUT 5000000
|
|
|
|
#define CBR_PATNUM 8
|
|
|
|
|
|
|
|
static const u32 pattern[8] = {
|
|
|
|
0xFF00FF00,
|
|
|
|
0xCC33CC33,
|
|
|
|
0xAA55AA55,
|
|
|
|
0x88778877,
|
|
|
|
0x92CC4D6E,
|
|
|
|
0x543D3CDE,
|
|
|
|
0xF1E843C7,
|
|
|
|
0x7C61D253
|
|
|
|
};
|
|
|
|
|
|
|
|
static int mmc_test_burst(struct ast_private *ast, u32 datagen)
|
|
|
|
{
|
|
|
|
u32 data, timeout;
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x000000c1 | (datagen << 3));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
timeout = 0;
|
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1e6e0070) & 0x3000;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (data & 0x2000) {
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
if (++timeout > TIMEOUT) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
} while (!data);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mmc_test_burst2(struct ast_private *ast, u32 datagen)
|
|
|
|
{
|
|
|
|
u32 data, timeout;
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000041 | (datagen << 3));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
timeout = 0;
|
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1e6e0070) & 0x1000;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (++timeout > TIMEOUT) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x0);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
} while (!data);
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1e6e0078);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = (data | (data >> 16)) & 0xffff;
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x0);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return data;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mmc_test_single(struct ast_private *ast, u32 datagen)
|
|
|
|
{
|
|
|
|
u32 data, timeout;
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x000000c5 | (datagen << 3));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
timeout = 0;
|
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1e6e0070) & 0x3000;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (data & 0x2000)
|
|
|
|
return 0;
|
|
|
|
if (++timeout > TIMEOUT) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x0);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
} while (!data);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x0);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mmc_test_single2(struct ast_private *ast, u32 datagen)
|
|
|
|
{
|
|
|
|
u32 data, timeout;
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x00000005 | (datagen << 3));
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
timeout = 0;
|
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1e6e0070) & 0x1000;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (++timeout > TIMEOUT) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x0);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
} while (!data);
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1e6e0078);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = (data | (data >> 16)) & 0xffff;
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e0070, 0x0);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return data;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int cbr_test(struct ast_private *ast)
|
|
|
|
{
|
|
|
|
u32 data;
|
|
|
|
int i;
|
|
|
|
data = mmc_test_single2(ast, 0);
|
|
|
|
if ((data & 0xff) && (data & 0xff00))
|
|
|
|
return 0;
|
|
|
|
for (i = 0; i < 8; i++) {
|
|
|
|
data = mmc_test_burst2(ast, i);
|
|
|
|
if ((data & 0xff) && (data & 0xff00))
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
if (!data)
|
|
|
|
return 3;
|
|
|
|
else if (data & 0xff)
|
|
|
|
return 2;
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int cbr_scan(struct ast_private *ast)
|
|
|
|
{
|
|
|
|
u32 data, data2, patcnt, loop;
|
|
|
|
|
|
|
|
data2 = 3;
|
|
|
|
for (patcnt = 0; patcnt < CBR_PATNUM; patcnt++) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e007c, pattern[patcnt]);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
for (loop = 0; loop < CBR_PASSNUM2; loop++) {
|
|
|
|
if ((data = cbr_test(ast)) != 0) {
|
|
|
|
data2 &= data;
|
|
|
|
if (!data2)
|
|
|
|
return 0;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (loop == CBR_PASSNUM2)
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
return data2;
|
|
|
|
}
|
|
|
|
|
|
|
|
static u32 cbr_test2(struct ast_private *ast)
|
|
|
|
{
|
|
|
|
u32 data;
|
|
|
|
|
|
|
|
data = mmc_test_burst2(ast, 0);
|
|
|
|
if (data == 0xffff)
|
|
|
|
return 0;
|
|
|
|
data |= mmc_test_single2(ast, 0);
|
|
|
|
if (data == 0xffff)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
return ~data & 0xffff;
|
|
|
|
}
|
|
|
|
|
|
|
|
static u32 cbr_scan2(struct ast_private *ast)
|
|
|
|
{
|
|
|
|
u32 data, data2, patcnt, loop;
|
|
|
|
|
|
|
|
data2 = 0xffff;
|
|
|
|
for (patcnt = 0; patcnt < CBR_PATNUM; patcnt++) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e007c, pattern[patcnt]);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
for (loop = 0; loop < CBR_PASSNUM2; loop++) {
|
|
|
|
if ((data = cbr_test2(ast)) != 0) {
|
|
|
|
data2 &= data;
|
2014-04-16 13:42:24 +04:00
|
|
|
if (!data2)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
return 0;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (loop == CBR_PASSNUM2)
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
return data2;
|
|
|
|
}
|
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
static u32 cbr_test3(struct ast_private *ast)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
{
|
2014-01-17 05:36:14 +04:00
|
|
|
if (!mmc_test_burst(ast, 0))
|
|
|
|
return 0;
|
|
|
|
if (!mmc_test_single(ast, 0))
|
|
|
|
return 0;
|
|
|
|
return 1;
|
|
|
|
}
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
static u32 cbr_scan3(struct ast_private *ast)
|
|
|
|
{
|
|
|
|
u32 patcnt, loop;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
for (patcnt = 0; patcnt < CBR_PATNUM; patcnt++) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1e6e007c, pattern[patcnt]);
|
2014-01-17 05:36:14 +04:00
|
|
|
for (loop = 0; loop < 2; loop++) {
|
|
|
|
if (cbr_test3(ast))
|
|
|
|
break;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
if (loop == 2)
|
|
|
|
return 0;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
return 1;
|
|
|
|
}
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
static bool finetuneDQI_L(struct ast_private *ast, struct ast2300_dram_param *param)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
{
|
2014-01-17 05:36:14 +04:00
|
|
|
u32 gold_sadj[2], dllmin[16], dllmax[16], dlli, data, cnt, mask, passcnt, retry = 0;
|
|
|
|
bool status = false;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
FINETUNE_START:
|
|
|
|
for (cnt = 0; cnt < 16; cnt++) {
|
|
|
|
dllmin[cnt] = 0xff;
|
|
|
|
dllmax[cnt] = 0x0;
|
|
|
|
}
|
|
|
|
passcnt = 0;
|
|
|
|
for (dlli = 0; dlli < 76; dlli++) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0068, 0x00001400 | (dlli << 16) | (dlli << 24));
|
|
|
|
ast_moutdwm(ast, 0x1E6E0074, CBR_SIZE1);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = cbr_scan2(ast);
|
|
|
|
if (data != 0) {
|
|
|
|
mask = 0x00010001;
|
|
|
|
for (cnt = 0; cnt < 16; cnt++) {
|
|
|
|
if (data & mask) {
|
|
|
|
if (dllmin[cnt] > dlli) {
|
|
|
|
dllmin[cnt] = dlli;
|
|
|
|
}
|
|
|
|
if (dllmax[cnt] < dlli) {
|
|
|
|
dllmax[cnt] = dlli;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
mask <<= 1;
|
|
|
|
}
|
|
|
|
passcnt++;
|
|
|
|
} else if (passcnt >= CBR_THRESHOLD2) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
gold_sadj[0] = 0x0;
|
|
|
|
passcnt = 0;
|
|
|
|
for (cnt = 0; cnt < 16; cnt++) {
|
|
|
|
if ((dllmax[cnt] > dllmin[cnt]) && ((dllmax[cnt] - dllmin[cnt]) >= CBR_THRESHOLD2)) {
|
|
|
|
gold_sadj[0] += dllmin[cnt];
|
|
|
|
passcnt++;
|
|
|
|
}
|
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
if (retry++ > 10)
|
|
|
|
goto FINETUNE_DONE;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (passcnt != 16) {
|
|
|
|
goto FINETUNE_START;
|
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
status = true;
|
|
|
|
FINETUNE_DONE:
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
gold_sadj[0] = gold_sadj[0] >> 4;
|
|
|
|
gold_sadj[1] = gold_sadj[0];
|
|
|
|
|
|
|
|
data = 0;
|
|
|
|
for (cnt = 0; cnt < 8; cnt++) {
|
|
|
|
data >>= 3;
|
|
|
|
if ((dllmax[cnt] > dllmin[cnt]) && ((dllmax[cnt] - dllmin[cnt]) >= CBR_THRESHOLD2)) {
|
|
|
|
dlli = dllmin[cnt];
|
|
|
|
if (gold_sadj[0] >= dlli) {
|
|
|
|
dlli = ((gold_sadj[0] - dlli) * 19) >> 5;
|
|
|
|
if (dlli > 3) {
|
|
|
|
dlli = 3;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
dlli = ((dlli - gold_sadj[0]) * 19) >> 5;
|
|
|
|
if (dlli > 4) {
|
|
|
|
dlli = 4;
|
|
|
|
}
|
|
|
|
dlli = (8 - dlli) & 0x7;
|
|
|
|
}
|
|
|
|
data |= dlli << 21;
|
|
|
|
}
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0080, data);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
data = 0;
|
|
|
|
for (cnt = 8; cnt < 16; cnt++) {
|
|
|
|
data >>= 3;
|
|
|
|
if ((dllmax[cnt] > dllmin[cnt]) && ((dllmax[cnt] - dllmin[cnt]) >= CBR_THRESHOLD2)) {
|
|
|
|
dlli = dllmin[cnt];
|
|
|
|
if (gold_sadj[1] >= dlli) {
|
|
|
|
dlli = ((gold_sadj[1] - dlli) * 19) >> 5;
|
|
|
|
if (dlli > 3) {
|
|
|
|
dlli = 3;
|
|
|
|
} else {
|
|
|
|
dlli = (dlli - 1) & 0x7;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
dlli = ((dlli - gold_sadj[1]) * 19) >> 5;
|
|
|
|
dlli += 1;
|
|
|
|
if (dlli > 4) {
|
|
|
|
dlli = 4;
|
|
|
|
}
|
|
|
|
dlli = (8 - dlli) & 0x7;
|
|
|
|
}
|
|
|
|
data |= dlli << 21;
|
|
|
|
}
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0084, data);
|
2014-01-17 05:36:14 +04:00
|
|
|
return status;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
} /* finetuneDQI_L */
|
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
static void finetuneDQSI(struct ast_private *ast)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
{
|
2014-01-17 05:36:14 +04:00
|
|
|
u32 dlli, dqsip, dqidly;
|
|
|
|
u32 reg_mcr18, reg_mcr0c, passcnt[2], diff;
|
|
|
|
u32 g_dqidly, g_dqsip, g_margin, g_side;
|
|
|
|
u16 pass[32][2][2];
|
|
|
|
char tag[2][76];
|
|
|
|
|
|
|
|
/* Disable DQI CBR */
|
2014-03-28 04:22:41 +04:00
|
|
|
reg_mcr0c = ast_mindwm(ast, 0x1E6E000C);
|
|
|
|
reg_mcr18 = ast_mindwm(ast, 0x1E6E0018);
|
2014-01-17 05:36:14 +04:00
|
|
|
reg_mcr18 &= 0x0000ffff;
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0018, reg_mcr18);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
for (dlli = 0; dlli < 76; dlli++) {
|
2014-01-17 05:36:14 +04:00
|
|
|
tag[0][dlli] = 0x0;
|
|
|
|
tag[1][dlli] = 0x0;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
for (dqidly = 0; dqidly < 32; dqidly++) {
|
|
|
|
pass[dqidly][0][0] = 0xff;
|
|
|
|
pass[dqidly][0][1] = 0x0;
|
|
|
|
pass[dqidly][1][0] = 0xff;
|
|
|
|
pass[dqidly][1][1] = 0x0;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
for (dqidly = 0; dqidly < 32; dqidly++) {
|
|
|
|
passcnt[0] = passcnt[1] = 0;
|
|
|
|
for (dqsip = 0; dqsip < 2; dqsip++) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E000C, 0);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, reg_mcr18 | (dqidly << 16) | (dqsip << 23));
|
|
|
|
ast_moutdwm(ast, 0x1E6E000C, reg_mcr0c);
|
2014-01-17 05:36:14 +04:00
|
|
|
for (dlli = 0; dlli < 76; dlli++) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0068, 0x00001300 | (dlli << 16) | (dlli << 24));
|
|
|
|
ast_moutdwm(ast, 0x1E6E0070, 0);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0074, CBR_SIZE0);
|
2014-01-17 05:36:14 +04:00
|
|
|
if (cbr_scan3(ast)) {
|
|
|
|
if (dlli == 0)
|
|
|
|
break;
|
|
|
|
passcnt[dqsip]++;
|
|
|
|
tag[dqsip][dlli] = 'P';
|
|
|
|
if (dlli < pass[dqidly][dqsip][0])
|
|
|
|
pass[dqidly][dqsip][0] = (u16) dlli;
|
|
|
|
if (dlli > pass[dqidly][dqsip][1])
|
|
|
|
pass[dqidly][dqsip][1] = (u16) dlli;
|
|
|
|
} else if (passcnt[dqsip] >= 5)
|
|
|
|
break;
|
|
|
|
else {
|
|
|
|
pass[dqidly][dqsip][0] = 0xff;
|
|
|
|
pass[dqidly][dqsip][1] = 0x0;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
if (passcnt[0] == 0 && passcnt[1] == 0)
|
|
|
|
dqidly++;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
/* Search margin */
|
|
|
|
g_dqidly = g_dqsip = g_margin = g_side = 0;
|
|
|
|
|
|
|
|
for (dqidly = 0; dqidly < 32; dqidly++) {
|
|
|
|
for (dqsip = 0; dqsip < 2; dqsip++) {
|
|
|
|
if (pass[dqidly][dqsip][0] > pass[dqidly][dqsip][1])
|
|
|
|
continue;
|
|
|
|
diff = pass[dqidly][dqsip][1] - pass[dqidly][dqsip][0];
|
|
|
|
if ((diff+2) < g_margin)
|
|
|
|
continue;
|
|
|
|
passcnt[0] = passcnt[1] = 0;
|
|
|
|
for (dlli = pass[dqidly][dqsip][0]; dlli > 0 && tag[dqsip][dlli] != 0; dlli--, passcnt[0]++);
|
|
|
|
for (dlli = pass[dqidly][dqsip][1]; dlli < 76 && tag[dqsip][dlli] != 0; dlli++, passcnt[1]++);
|
|
|
|
if (passcnt[0] > passcnt[1])
|
|
|
|
passcnt[0] = passcnt[1];
|
|
|
|
passcnt[1] = 0;
|
|
|
|
if (passcnt[0] > g_side)
|
|
|
|
passcnt[1] = passcnt[0] - g_side;
|
|
|
|
if (diff > (g_margin+1) && (passcnt[1] > 0 || passcnt[0] > 8)) {
|
|
|
|
g_margin = diff;
|
|
|
|
g_dqidly = dqidly;
|
|
|
|
g_dqsip = dqsip;
|
|
|
|
g_side = passcnt[0];
|
|
|
|
} else if (passcnt[1] > 1 && g_side < 8) {
|
|
|
|
if (diff > g_margin)
|
|
|
|
g_margin = diff;
|
|
|
|
g_dqidly = dqidly;
|
|
|
|
g_dqsip = dqsip;
|
|
|
|
g_side = passcnt[0];
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
reg_mcr18 = reg_mcr18 | (g_dqidly << 16) | (g_dqsip << 23);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0018, reg_mcr18);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
}
|
|
|
|
static bool cbr_dll2(struct ast_private *ast, struct ast2300_dram_param *param)
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
{
|
2014-01-17 05:36:14 +04:00
|
|
|
u32 dllmin[2], dllmax[2], dlli, data, passcnt, retry = 0;
|
|
|
|
bool status = false;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
finetuneDQSI(ast);
|
|
|
|
if (finetuneDQI_L(ast, param) == false)
|
|
|
|
return status;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
CBR_START2:
|
|
|
|
dllmin[0] = dllmin[1] = 0xff;
|
|
|
|
dllmax[0] = dllmax[1] = 0x0;
|
|
|
|
passcnt = 0;
|
|
|
|
for (dlli = 0; dlli < 76; dlli++) {
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0068, 0x00001300 | (dlli << 16) | (dlli << 24));
|
|
|
|
ast_moutdwm(ast, 0x1E6E0074, CBR_SIZE2);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = cbr_scan(ast);
|
|
|
|
if (data != 0) {
|
|
|
|
if (data & 0x1) {
|
|
|
|
if (dllmin[0] > dlli) {
|
|
|
|
dllmin[0] = dlli;
|
|
|
|
}
|
|
|
|
if (dllmax[0] < dlli) {
|
|
|
|
dllmax[0] = dlli;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (data & 0x2) {
|
|
|
|
if (dllmin[1] > dlli) {
|
|
|
|
dllmin[1] = dlli;
|
|
|
|
}
|
|
|
|
if (dllmax[1] < dlli) {
|
|
|
|
dllmax[1] = dlli;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
passcnt++;
|
|
|
|
} else if (passcnt >= CBR_THRESHOLD) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
if (retry++ > 10)
|
|
|
|
goto CBR_DONE2;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (dllmax[0] == 0 || (dllmax[0]-dllmin[0]) < CBR_THRESHOLD) {
|
|
|
|
goto CBR_START2;
|
|
|
|
}
|
|
|
|
if (dllmax[1] == 0 || (dllmax[1]-dllmin[1]) < CBR_THRESHOLD) {
|
|
|
|
goto CBR_START2;
|
|
|
|
}
|
2014-01-17 05:36:14 +04:00
|
|
|
status = true;
|
|
|
|
CBR_DONE2:
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
dlli = (dllmin[1] + dllmax[1]) >> 1;
|
|
|
|
dlli <<= 8;
|
|
|
|
dlli += (dllmin[0] + dllmax[0]) >> 1;
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0068, ast_mindwm(ast, 0x1E720058) | (dlli << 16));
|
2014-01-17 05:36:14 +04:00
|
|
|
return status;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
} /* CBRDLL2 */
|
|
|
|
|
|
|
|
static void get_ddr3_info(struct ast_private *ast, struct ast2300_dram_param *param)
|
|
|
|
{
|
|
|
|
u32 trap, trap_AC2, trap_MRS;
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2000, 0x1688A8A8);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
/* Ger trap info */
|
2014-03-28 04:22:41 +04:00
|
|
|
trap = (ast_mindwm(ast, 0x1E6E2070) >> 25) & 0x3;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
trap_AC2 = 0x00020000 + (trap << 16);
|
|
|
|
trap_AC2 |= 0x00300000 + ((trap & 0x2) << 19);
|
|
|
|
trap_MRS = 0x00000010 + (trap << 4);
|
|
|
|
trap_MRS |= ((trap & 0x2) << 18);
|
|
|
|
|
|
|
|
param->reg_MADJ = 0x00034C4C;
|
|
|
|
param->reg_SADJ = 0x00001800;
|
|
|
|
param->reg_DRV = 0x000000F0;
|
|
|
|
param->reg_PERIOD = param->dram_freq;
|
|
|
|
param->rodt = 0;
|
|
|
|
|
|
|
|
switch (param->dram_freq) {
|
|
|
|
case 336:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0190);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 0;
|
|
|
|
param->reg_AC1 = 0x22202725;
|
|
|
|
param->reg_AC2 = 0xAA007613 | trap_AC2;
|
|
|
|
param->reg_DQSIC = 0x000000BA;
|
|
|
|
param->reg_MRS = 0x04001400 | trap_MRS;
|
|
|
|
param->reg_EMRS = 0x00000000;
|
2014-01-17 05:36:14 +04:00
|
|
|
param->reg_IOZ = 0x00000023;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->reg_DQIDLY = 0x00000074;
|
|
|
|
param->reg_FREQ = 0x00004DC0;
|
|
|
|
param->madj_max = 96;
|
|
|
|
param->dll2_finetune_step = 3;
|
2014-01-17 05:36:14 +04:00
|
|
|
switch (param->dram_chipid) {
|
|
|
|
default:
|
|
|
|
case AST_DRAM_512Mx16:
|
|
|
|
case AST_DRAM_1Gx16:
|
|
|
|
param->reg_AC2 = 0xAA007613 | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_2Gx16:
|
|
|
|
param->reg_AC2 = 0xAA00761C | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_4Gx16:
|
|
|
|
param->reg_AC2 = 0xAA007636 | trap_AC2;
|
|
|
|
break;
|
|
|
|
}
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
break;
|
|
|
|
default:
|
|
|
|
case 396:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x03F1);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->reg_AC1 = 0x33302825;
|
|
|
|
param->reg_AC2 = 0xCC009617 | trap_AC2;
|
|
|
|
param->reg_DQSIC = 0x000000E2;
|
|
|
|
param->reg_MRS = 0x04001600 | trap_MRS;
|
|
|
|
param->reg_EMRS = 0x00000000;
|
|
|
|
param->reg_IOZ = 0x00000034;
|
|
|
|
param->reg_DRV = 0x000000FA;
|
|
|
|
param->reg_DQIDLY = 0x00000089;
|
2014-01-17 05:36:14 +04:00
|
|
|
param->reg_FREQ = 0x00005040;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->madj_max = 96;
|
|
|
|
param->dll2_finetune_step = 4;
|
|
|
|
|
|
|
|
switch (param->dram_chipid) {
|
|
|
|
default:
|
|
|
|
case AST_DRAM_512Mx16:
|
|
|
|
case AST_DRAM_1Gx16:
|
|
|
|
param->reg_AC2 = 0xCC009617 | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_2Gx16:
|
|
|
|
param->reg_AC2 = 0xCC009622 | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_4Gx16:
|
|
|
|
param->reg_AC2 = 0xCC00963F | trap_AC2;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 408:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x01F0);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->reg_AC1 = 0x33302825;
|
|
|
|
param->reg_AC2 = 0xCC009617 | trap_AC2;
|
|
|
|
param->reg_DQSIC = 0x000000E2;
|
|
|
|
param->reg_MRS = 0x04001600 | trap_MRS;
|
|
|
|
param->reg_EMRS = 0x00000000;
|
2014-01-17 05:36:14 +04:00
|
|
|
param->reg_IOZ = 0x00000023;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->reg_DRV = 0x000000FA;
|
|
|
|
param->reg_DQIDLY = 0x00000089;
|
|
|
|
param->reg_FREQ = 0x000050C0;
|
|
|
|
param->madj_max = 96;
|
|
|
|
param->dll2_finetune_step = 4;
|
|
|
|
|
|
|
|
switch (param->dram_chipid) {
|
|
|
|
default:
|
|
|
|
case AST_DRAM_512Mx16:
|
|
|
|
case AST_DRAM_1Gx16:
|
|
|
|
param->reg_AC2 = 0xCC009617 | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_2Gx16:
|
|
|
|
param->reg_AC2 = 0xCC009622 | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_4Gx16:
|
|
|
|
param->reg_AC2 = 0xCC00963F | trap_AC2;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
break;
|
|
|
|
case 456:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0230);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 0;
|
|
|
|
param->reg_AC1 = 0x33302926;
|
|
|
|
param->reg_AC2 = 0xCD44961A;
|
|
|
|
param->reg_DQSIC = 0x000000FC;
|
|
|
|
param->reg_MRS = 0x00081830;
|
|
|
|
param->reg_EMRS = 0x00000000;
|
|
|
|
param->reg_IOZ = 0x00000045;
|
|
|
|
param->reg_DQIDLY = 0x00000097;
|
|
|
|
param->reg_FREQ = 0x000052C0;
|
|
|
|
param->madj_max = 88;
|
|
|
|
param->dll2_finetune_step = 4;
|
|
|
|
break;
|
|
|
|
case 504:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0270);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->reg_AC1 = 0x33302926;
|
|
|
|
param->reg_AC2 = 0xDE44A61D;
|
|
|
|
param->reg_DQSIC = 0x00000117;
|
|
|
|
param->reg_MRS = 0x00081A30;
|
|
|
|
param->reg_EMRS = 0x00000000;
|
|
|
|
param->reg_IOZ = 0x070000BB;
|
|
|
|
param->reg_DQIDLY = 0x000000A0;
|
|
|
|
param->reg_FREQ = 0x000054C0;
|
|
|
|
param->madj_max = 79;
|
|
|
|
param->dll2_finetune_step = 4;
|
|
|
|
break;
|
|
|
|
case 528:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0290);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 1;
|
|
|
|
param->reg_AC1 = 0x33302926;
|
|
|
|
param->reg_AC2 = 0xEF44B61E;
|
|
|
|
param->reg_DQSIC = 0x00000125;
|
|
|
|
param->reg_MRS = 0x00081A30;
|
|
|
|
param->reg_EMRS = 0x00000040;
|
|
|
|
param->reg_DRV = 0x000000F5;
|
|
|
|
param->reg_IOZ = 0x00000023;
|
|
|
|
param->reg_DQIDLY = 0x00000088;
|
|
|
|
param->reg_FREQ = 0x000055C0;
|
|
|
|
param->madj_max = 76;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
case 576:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0140);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->reg_MADJ = 0x00136868;
|
|
|
|
param->reg_SADJ = 0x00004534;
|
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 1;
|
|
|
|
param->reg_AC1 = 0x33302A37;
|
|
|
|
param->reg_AC2 = 0xEF56B61E;
|
|
|
|
param->reg_DQSIC = 0x0000013F;
|
|
|
|
param->reg_MRS = 0x00101A50;
|
|
|
|
param->reg_EMRS = 0x00000040;
|
|
|
|
param->reg_DRV = 0x000000FA;
|
|
|
|
param->reg_IOZ = 0x00000023;
|
|
|
|
param->reg_DQIDLY = 0x00000078;
|
|
|
|
param->reg_FREQ = 0x000057C0;
|
|
|
|
param->madj_max = 136;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
case 600:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x02E1);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->reg_MADJ = 0x00136868;
|
|
|
|
param->reg_SADJ = 0x00004534;
|
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 1;
|
|
|
|
param->reg_AC1 = 0x32302A37;
|
|
|
|
param->reg_AC2 = 0xDF56B61F;
|
|
|
|
param->reg_DQSIC = 0x0000014D;
|
|
|
|
param->reg_MRS = 0x00101A50;
|
|
|
|
param->reg_EMRS = 0x00000004;
|
|
|
|
param->reg_DRV = 0x000000F5;
|
|
|
|
param->reg_IOZ = 0x00000023;
|
|
|
|
param->reg_DQIDLY = 0x00000078;
|
|
|
|
param->reg_FREQ = 0x000058C0;
|
|
|
|
param->madj_max = 132;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
case 624:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0160);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->reg_MADJ = 0x00136868;
|
|
|
|
param->reg_SADJ = 0x00004534;
|
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 1;
|
|
|
|
param->reg_AC1 = 0x32302A37;
|
|
|
|
param->reg_AC2 = 0xEF56B621;
|
|
|
|
param->reg_DQSIC = 0x0000015A;
|
|
|
|
param->reg_MRS = 0x02101A50;
|
|
|
|
param->reg_EMRS = 0x00000004;
|
|
|
|
param->reg_DRV = 0x000000F5;
|
|
|
|
param->reg_IOZ = 0x00000034;
|
|
|
|
param->reg_DQIDLY = 0x00000078;
|
|
|
|
param->reg_FREQ = 0x000059C0;
|
|
|
|
param->madj_max = 128;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
} /* switch freq */
|
|
|
|
|
|
|
|
switch (param->dram_chipid) {
|
|
|
|
case AST_DRAM_512Mx16:
|
|
|
|
param->dram_config = 0x130;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
case AST_DRAM_1Gx16:
|
|
|
|
param->dram_config = 0x131;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_2Gx16:
|
|
|
|
param->dram_config = 0x132;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_4Gx16:
|
|
|
|
param->dram_config = 0x133;
|
|
|
|
break;
|
2014-06-09 17:21:08 +04:00
|
|
|
} /* switch size */
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
switch (param->vram_size) {
|
|
|
|
default:
|
|
|
|
case AST_VIDMEM_SIZE_8M:
|
|
|
|
param->dram_config |= 0x00;
|
|
|
|
break;
|
|
|
|
case AST_VIDMEM_SIZE_16M:
|
|
|
|
param->dram_config |= 0x04;
|
|
|
|
break;
|
|
|
|
case AST_VIDMEM_SIZE_32M:
|
|
|
|
param->dram_config |= 0x08;
|
|
|
|
break;
|
|
|
|
case AST_VIDMEM_SIZE_64M:
|
|
|
|
param->dram_config |= 0x0c;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ddr3_init(struct ast_private *ast, struct ast2300_dram_param *param)
|
|
|
|
{
|
2014-01-17 05:36:14 +04:00
|
|
|
u32 data, data2, retry = 0;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
ddr3_init_start:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0000, 0xFC600309);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, 0x00000100);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0024, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0034, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(10);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0064, param->reg_MADJ);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0068, param->reg_SADJ);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(10);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0064, param->reg_MADJ | 0xC0000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(10);
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0004, param->dram_config);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0008, 0x90040f);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0010, param->reg_AC1);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0014, param->reg_AC2);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0020, param->reg_DQSIC);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0080, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0084, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0088, param->reg_DQIDLY);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, 0x4000A170);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, 0x00002370);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0038, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0040, 0xFF444444);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0044, 0x22222222);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0048, 0x22222222);
|
|
|
|
ast_moutdwm(ast, 0x1E6E004C, 0x00000002);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0050, 0x80000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0050, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0054, 0);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0060, param->reg_DRV);
|
|
|
|
ast_moutdwm(ast, 0x1E6E006C, param->reg_IOZ);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0074, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0078, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E007C, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
/* Wait MCLK2X lock to MCLK */
|
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E001C);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
} while (!(data & 0x08000000));
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E001C);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = (data >> 8) & 0xff;
|
|
|
|
while ((data & 0x08) || ((data & 0x7) < 2) || (data < 4)) {
|
2014-03-28 04:22:41 +04:00
|
|
|
data2 = (ast_mindwm(ast, 0x1E6E0064) & 0xfff3ffff) + 4;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if ((data2 & 0xff) > param->madj_max) {
|
|
|
|
break;
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0064, data2);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (data2 & 0x00100000) {
|
|
|
|
data2 = ((data2 & 0xff) >> 3) + 3;
|
|
|
|
} else {
|
|
|
|
data2 = ((data2 & 0xff) >> 2) + 5;
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E0068) & 0xffff00ff;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data2 += data & 0xff;
|
|
|
|
data = data | (data2 << 8);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0068, data);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(10);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0064, ast_mindwm(ast, 0x1E6E0064) | 0xC0000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(10);
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E0018) & 0xfffff1ff;
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, data);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = data | 0x200;
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0018, data);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E001C);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
} while (!(data & 0x08000000));
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E001C);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = (data >> 8) & 0xff;
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E720058, ast_mindwm(ast, 0x1E6E0068) & 0xffff);
|
|
|
|
data = ast_mindwm(ast, 0x1E6E0018) | 0xC00;
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, data);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0034, 0x00000001);
|
|
|
|
ast_moutdwm(ast, 0x1E6E000C, 0x00000040);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(50);
|
|
|
|
/* Mode Register Setting */
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E002C, param->reg_MRS | 0x100);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0030, param->reg_EMRS);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000005);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000007);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000003);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000001);
|
|
|
|
ast_moutdwm(ast, 0x1E6E002C, param->reg_MRS);
|
|
|
|
ast_moutdwm(ast, 0x1E6E000C, 0x00005C08);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000001);
|
|
|
|
|
|
|
|
ast_moutdwm(ast, 0x1E6E000C, 0x00005C01);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = 0;
|
|
|
|
if (param->wodt) {
|
|
|
|
data = 0x300;
|
|
|
|
}
|
|
|
|
if (param->rodt) {
|
|
|
|
data = data | 0x3000 | ((param->reg_AC2 & 0x60000) >> 3);
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0034, data | 0x3);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
/* Calibrate the DQSI delay */
|
2014-01-17 05:36:14 +04:00
|
|
|
if ((cbr_dll2(ast, param) == false) && (retry++ < 10))
|
|
|
|
goto ddr3_init_start;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0120, param->reg_FREQ);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
/* ECC Memory Initialization */
|
|
|
|
#ifdef ECC
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E007C, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0070, 0x221);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E0070);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
} while (!(data & 0x00001000));
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0050, 0x80000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0050, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
static void get_ddr2_info(struct ast_private *ast, struct ast2300_dram_param *param)
|
|
|
|
{
|
|
|
|
u32 trap, trap_AC2, trap_MRS;
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2000, 0x1688A8A8);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
/* Ger trap info */
|
2014-03-28 04:22:41 +04:00
|
|
|
trap = (ast_mindwm(ast, 0x1E6E2070) >> 25) & 0x3;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
trap_AC2 = (trap << 20) | (trap << 16);
|
|
|
|
trap_AC2 += 0x00110000;
|
|
|
|
trap_MRS = 0x00000040 | (trap << 4);
|
|
|
|
|
|
|
|
|
|
|
|
param->reg_MADJ = 0x00034C4C;
|
|
|
|
param->reg_SADJ = 0x00001800;
|
|
|
|
param->reg_DRV = 0x000000F0;
|
|
|
|
param->reg_PERIOD = param->dram_freq;
|
|
|
|
param->rodt = 0;
|
|
|
|
|
|
|
|
switch (param->dram_freq) {
|
|
|
|
case 264:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0130);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 0;
|
|
|
|
param->reg_AC1 = 0x11101513;
|
|
|
|
param->reg_AC2 = 0x78117011;
|
|
|
|
param->reg_DQSIC = 0x00000092;
|
|
|
|
param->reg_MRS = 0x00000842;
|
|
|
|
param->reg_EMRS = 0x00000000;
|
|
|
|
param->reg_DRV = 0x000000F0;
|
|
|
|
param->reg_IOZ = 0x00000034;
|
|
|
|
param->reg_DQIDLY = 0x0000005A;
|
|
|
|
param->reg_FREQ = 0x00004AC0;
|
|
|
|
param->madj_max = 138;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
case 336:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0190);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->reg_AC1 = 0x22202613;
|
|
|
|
param->reg_AC2 = 0xAA009016 | trap_AC2;
|
|
|
|
param->reg_DQSIC = 0x000000BA;
|
|
|
|
param->reg_MRS = 0x00000A02 | trap_MRS;
|
|
|
|
param->reg_EMRS = 0x00000040;
|
|
|
|
param->reg_DRV = 0x000000FA;
|
|
|
|
param->reg_IOZ = 0x00000034;
|
|
|
|
param->reg_DQIDLY = 0x00000074;
|
|
|
|
param->reg_FREQ = 0x00004DC0;
|
|
|
|
param->madj_max = 96;
|
|
|
|
param->dll2_finetune_step = 3;
|
2014-01-17 05:36:14 +04:00
|
|
|
switch (param->dram_chipid) {
|
|
|
|
default:
|
|
|
|
case AST_DRAM_512Mx16:
|
|
|
|
param->reg_AC2 = 0xAA009012 | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_1Gx16:
|
|
|
|
param->reg_AC2 = 0xAA009016 | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_2Gx16:
|
|
|
|
param->reg_AC2 = 0xAA009023 | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_4Gx16:
|
|
|
|
param->reg_AC2 = 0xAA00903B | trap_AC2;
|
|
|
|
break;
|
|
|
|
}
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
break;
|
|
|
|
default:
|
|
|
|
case 396:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x03F1);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 0;
|
|
|
|
param->reg_AC1 = 0x33302714;
|
|
|
|
param->reg_AC2 = 0xCC00B01B | trap_AC2;
|
|
|
|
param->reg_DQSIC = 0x000000E2;
|
|
|
|
param->reg_MRS = 0x00000C02 | trap_MRS;
|
|
|
|
param->reg_EMRS = 0x00000040;
|
|
|
|
param->reg_DRV = 0x000000FA;
|
|
|
|
param->reg_IOZ = 0x00000034;
|
|
|
|
param->reg_DQIDLY = 0x00000089;
|
2014-01-17 05:36:14 +04:00
|
|
|
param->reg_FREQ = 0x00005040;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->madj_max = 96;
|
|
|
|
param->dll2_finetune_step = 4;
|
|
|
|
|
|
|
|
switch (param->dram_chipid) {
|
|
|
|
case AST_DRAM_512Mx16:
|
|
|
|
param->reg_AC2 = 0xCC00B016 | trap_AC2;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
case AST_DRAM_1Gx16:
|
|
|
|
param->reg_AC2 = 0xCC00B01B | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_2Gx16:
|
|
|
|
param->reg_AC2 = 0xCC00B02B | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_4Gx16:
|
|
|
|
param->reg_AC2 = 0xCC00B03F | trap_AC2;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 408:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x01F0);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 0;
|
|
|
|
param->reg_AC1 = 0x33302714;
|
|
|
|
param->reg_AC2 = 0xCC00B01B | trap_AC2;
|
|
|
|
param->reg_DQSIC = 0x000000E2;
|
|
|
|
param->reg_MRS = 0x00000C02 | trap_MRS;
|
|
|
|
param->reg_EMRS = 0x00000040;
|
|
|
|
param->reg_DRV = 0x000000FA;
|
|
|
|
param->reg_IOZ = 0x00000034;
|
|
|
|
param->reg_DQIDLY = 0x00000089;
|
|
|
|
param->reg_FREQ = 0x000050C0;
|
|
|
|
param->madj_max = 96;
|
|
|
|
param->dll2_finetune_step = 4;
|
|
|
|
|
|
|
|
switch (param->dram_chipid) {
|
|
|
|
case AST_DRAM_512Mx16:
|
|
|
|
param->reg_AC2 = 0xCC00B016 | trap_AC2;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
case AST_DRAM_1Gx16:
|
|
|
|
param->reg_AC2 = 0xCC00B01B | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_2Gx16:
|
|
|
|
param->reg_AC2 = 0xCC00B02B | trap_AC2;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_4Gx16:
|
|
|
|
param->reg_AC2 = 0xCC00B03F | trap_AC2;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
break;
|
|
|
|
case 456:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0230);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 0;
|
|
|
|
param->reg_AC1 = 0x33302815;
|
|
|
|
param->reg_AC2 = 0xCD44B01E;
|
|
|
|
param->reg_DQSIC = 0x000000FC;
|
|
|
|
param->reg_MRS = 0x00000E72;
|
|
|
|
param->reg_EMRS = 0x00000000;
|
|
|
|
param->reg_DRV = 0x00000000;
|
|
|
|
param->reg_IOZ = 0x00000034;
|
|
|
|
param->reg_DQIDLY = 0x00000097;
|
|
|
|
param->reg_FREQ = 0x000052C0;
|
|
|
|
param->madj_max = 88;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
case 504:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0261);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 1;
|
|
|
|
param->reg_AC1 = 0x33302815;
|
|
|
|
param->reg_AC2 = 0xDE44C022;
|
|
|
|
param->reg_DQSIC = 0x00000117;
|
|
|
|
param->reg_MRS = 0x00000E72;
|
|
|
|
param->reg_EMRS = 0x00000040;
|
|
|
|
param->reg_DRV = 0x0000000A;
|
|
|
|
param->reg_IOZ = 0x00000045;
|
|
|
|
param->reg_DQIDLY = 0x000000A0;
|
|
|
|
param->reg_FREQ = 0x000054C0;
|
|
|
|
param->madj_max = 79;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
case 528:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0120);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 1;
|
|
|
|
param->reg_AC1 = 0x33302815;
|
|
|
|
param->reg_AC2 = 0xEF44D024;
|
|
|
|
param->reg_DQSIC = 0x00000125;
|
|
|
|
param->reg_MRS = 0x00000E72;
|
|
|
|
param->reg_EMRS = 0x00000004;
|
|
|
|
param->reg_DRV = 0x000000F9;
|
|
|
|
param->reg_IOZ = 0x00000045;
|
|
|
|
param->reg_DQIDLY = 0x000000A7;
|
|
|
|
param->reg_FREQ = 0x000055C0;
|
|
|
|
param->madj_max = 76;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
case 552:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x02A1);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 1;
|
|
|
|
param->reg_AC1 = 0x43402915;
|
|
|
|
param->reg_AC2 = 0xFF44E025;
|
|
|
|
param->reg_DQSIC = 0x00000132;
|
|
|
|
param->reg_MRS = 0x00000E72;
|
|
|
|
param->reg_EMRS = 0x00000040;
|
|
|
|
param->reg_DRV = 0x0000000A;
|
|
|
|
param->reg_IOZ = 0x00000045;
|
|
|
|
param->reg_DQIDLY = 0x000000AD;
|
|
|
|
param->reg_FREQ = 0x000056C0;
|
|
|
|
param->madj_max = 76;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
case 576:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E2020, 0x0140);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
param->wodt = 1;
|
|
|
|
param->rodt = 1;
|
|
|
|
param->reg_AC1 = 0x43402915;
|
|
|
|
param->reg_AC2 = 0xFF44E027;
|
|
|
|
param->reg_DQSIC = 0x0000013F;
|
|
|
|
param->reg_MRS = 0x00000E72;
|
|
|
|
param->reg_EMRS = 0x00000004;
|
|
|
|
param->reg_DRV = 0x000000F5;
|
|
|
|
param->reg_IOZ = 0x00000045;
|
|
|
|
param->reg_DQIDLY = 0x000000B3;
|
|
|
|
param->reg_FREQ = 0x000057C0;
|
|
|
|
param->madj_max = 76;
|
|
|
|
param->dll2_finetune_step = 3;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (param->dram_chipid) {
|
|
|
|
case AST_DRAM_512Mx16:
|
|
|
|
param->dram_config = 0x100;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
case AST_DRAM_1Gx16:
|
|
|
|
param->dram_config = 0x121;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_2Gx16:
|
|
|
|
param->dram_config = 0x122;
|
|
|
|
break;
|
|
|
|
case AST_DRAM_4Gx16:
|
|
|
|
param->dram_config = 0x123;
|
|
|
|
break;
|
2014-06-09 17:21:08 +04:00
|
|
|
} /* switch size */
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
switch (param->vram_size) {
|
|
|
|
default:
|
|
|
|
case AST_VIDMEM_SIZE_8M:
|
|
|
|
param->dram_config |= 0x00;
|
|
|
|
break;
|
|
|
|
case AST_VIDMEM_SIZE_16M:
|
|
|
|
param->dram_config |= 0x04;
|
|
|
|
break;
|
|
|
|
case AST_VIDMEM_SIZE_32M:
|
|
|
|
param->dram_config |= 0x08;
|
|
|
|
break;
|
|
|
|
case AST_VIDMEM_SIZE_64M:
|
|
|
|
param->dram_config |= 0x0c;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ddr2_init(struct ast_private *ast, struct ast2300_dram_param *param)
|
|
|
|
{
|
2014-01-17 05:36:14 +04:00
|
|
|
u32 data, data2, retry = 0;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-01-17 05:36:14 +04:00
|
|
|
ddr2_init_start:
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0000, 0xFC600309);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, 0x00000100);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0024, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0064, param->reg_MADJ);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0068, param->reg_SADJ);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(10);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0064, param->reg_MADJ | 0xC0000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(10);
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0004, param->dram_config);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0008, 0x90040f);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0010, param->reg_AC1);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0014, param->reg_AC2);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0020, param->reg_DQSIC);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0080, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0084, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0088, param->reg_DQIDLY);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, 0x4000A130);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, 0x00002330);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0038, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0040, 0xFF808000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0044, 0x88848466);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0048, 0x44440008);
|
|
|
|
ast_moutdwm(ast, 0x1E6E004C, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0050, 0x80000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0050, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0054, 0);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0060, param->reg_DRV);
|
|
|
|
ast_moutdwm(ast, 0x1E6E006C, param->reg_IOZ);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0074, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0078, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E007C, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
/* Wait MCLK2X lock to MCLK */
|
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E001C);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
} while (!(data & 0x08000000));
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E001C);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = (data >> 8) & 0xff;
|
|
|
|
while ((data & 0x08) || ((data & 0x7) < 2) || (data < 4)) {
|
2014-03-28 04:22:41 +04:00
|
|
|
data2 = (ast_mindwm(ast, 0x1E6E0064) & 0xfff3ffff) + 4;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if ((data2 & 0xff) > param->madj_max) {
|
|
|
|
break;
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0064, data2);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
if (data2 & 0x00100000) {
|
|
|
|
data2 = ((data2 & 0xff) >> 3) + 3;
|
|
|
|
} else {
|
|
|
|
data2 = ((data2 & 0xff) >> 2) + 5;
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E0068) & 0xffff00ff;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data2 += data & 0xff;
|
|
|
|
data = data | (data2 << 8);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0068, data);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(10);
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0064, ast_mindwm(ast, 0x1E6E0064) | 0xC0000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(10);
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E0018) & 0xfffff1ff;
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, data);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = data | 0x200;
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0018, data);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E001C);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
} while (!(data & 0x08000000));
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E001C);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = (data >> 8) & 0xff;
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E720058, ast_mindwm(ast, 0x1E6E0008) & 0xffff);
|
|
|
|
data = ast_mindwm(ast, 0x1E6E0018) | 0xC00;
|
|
|
|
ast_moutdwm(ast, 0x1E6E0018, data);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0034, 0x00000001);
|
|
|
|
ast_moutdwm(ast, 0x1E6E000C, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
udelay(50);
|
|
|
|
/* Mode Register Setting */
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E002C, param->reg_MRS | 0x100);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0030, param->reg_EMRS);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000005);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000007);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000003);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000001);
|
|
|
|
|
|
|
|
ast_moutdwm(ast, 0x1E6E000C, 0x00005C08);
|
|
|
|
ast_moutdwm(ast, 0x1E6E002C, param->reg_MRS);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000001);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0030, param->reg_EMRS | 0x380);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000003);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0030, param->reg_EMRS);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0028, 0x00000003);
|
|
|
|
|
|
|
|
ast_moutdwm(ast, 0x1E6E000C, 0x7FFF5C01);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
data = 0;
|
|
|
|
if (param->wodt) {
|
|
|
|
data = 0x500;
|
|
|
|
}
|
|
|
|
if (param->rodt) {
|
|
|
|
data = data | 0x3000 | ((param->reg_AC2 & 0x60000) >> 3);
|
|
|
|
}
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0034, data | 0x3);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0120, param->reg_FREQ);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
/* Calibrate the DQSI delay */
|
2014-01-17 05:36:14 +04:00
|
|
|
if ((cbr_dll2(ast, param) == false) && (retry++ < 10))
|
|
|
|
goto ddr2_init_start;
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
|
|
|
|
/* ECC Memory Initialization */
|
|
|
|
#ifdef ECC
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E007C, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0070, 0x221);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
do {
|
2014-03-28 04:22:41 +04:00
|
|
|
data = ast_mindwm(ast, 0x1E6E0070);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
} while (!(data & 0x00001000));
|
2014-03-28 04:22:41 +04:00
|
|
|
ast_moutdwm(ast, 0x1E6E0070, 0x00000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0050, 0x80000000);
|
|
|
|
ast_moutdwm(ast, 0x1E6E0050, 0x00000000);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
#endif
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ast_init_dram_2300(struct drm_device *dev)
|
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
struct ast2300_dram_param param;
|
|
|
|
u32 temp;
|
|
|
|
u8 reg;
|
|
|
|
|
|
|
|
reg = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xd0, 0xff);
|
|
|
|
if ((reg & 0x80) == 0) {/* vga only */
|
|
|
|
ast_write32(ast, 0xf004, 0x1e6e0000);
|
|
|
|
ast_write32(ast, 0xf000, 0x1);
|
|
|
|
ast_write32(ast, 0x12000, 0x1688a8a8);
|
|
|
|
do {
|
|
|
|
;
|
|
|
|
} while (ast_read32(ast, 0x12000) != 0x1);
|
|
|
|
|
|
|
|
ast_write32(ast, 0x10000, 0xfc600309);
|
|
|
|
do {
|
|
|
|
;
|
|
|
|
} while (ast_read32(ast, 0x10000) != 0x1);
|
|
|
|
|
|
|
|
/* Slow down CPU/AHB CLK in VGA only mode */
|
|
|
|
temp = ast_read32(ast, 0x12008);
|
|
|
|
temp |= 0x73;
|
|
|
|
ast_write32(ast, 0x12008, temp);
|
|
|
|
|
|
|
|
param.dram_type = AST_DDR3;
|
|
|
|
if (temp & 0x01000000)
|
|
|
|
param.dram_type = AST_DDR2;
|
|
|
|
param.dram_chipid = ast->dram_type;
|
|
|
|
param.dram_freq = ast->mclk;
|
|
|
|
param.vram_size = ast->vram_size;
|
|
|
|
|
|
|
|
if (param.dram_type == AST_DDR3) {
|
|
|
|
get_ddr3_info(ast, ¶m);
|
|
|
|
ddr3_init(ast, ¶m);
|
|
|
|
} else {
|
|
|
|
get_ddr2_info(ast, ¶m);
|
|
|
|
ddr2_init(ast, ¶m);
|
|
|
|
}
|
|
|
|
|
2014-03-28 04:22:41 +04:00
|
|
|
temp = ast_mindwm(ast, 0x1e6e2040);
|
|
|
|
ast_moutdwm(ast, 0x1e6e2040, temp | 0x40);
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 17:40:04 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
/* wait ready */
|
|
|
|
do {
|
|
|
|
reg = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xd0, 0xff);
|
|
|
|
} while ((reg & 0x40) == 0);
|
|
|
|
}
|
|
|
|
|