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 20:40:04 +07: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-03 00:01:07 +07: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 20:40:04 +07:00
|
|
|
#include "ast_drv.h"
|
|
|
|
|
|
|
|
|
2012-10-03 00:01:07 +07:00
|
|
|
#include <drm/drm_fb_helper.h>
|
|
|
|
#include <drm/drm_crtc_helper.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 20:40:04 +07:00
|
|
|
|
|
|
|
#include "ast_dram_tables.h"
|
|
|
|
|
|
|
|
void ast_set_index_reg_mask(struct ast_private *ast,
|
|
|
|
uint32_t base, uint8_t index,
|
|
|
|
uint8_t mask, uint8_t val)
|
|
|
|
{
|
|
|
|
u8 tmp;
|
|
|
|
ast_io_write8(ast, base, index);
|
|
|
|
tmp = (ast_io_read8(ast, base + 1) & mask) | val;
|
|
|
|
ast_set_index_reg(ast, base, index, tmp);
|
|
|
|
}
|
|
|
|
|
|
|
|
uint8_t ast_get_index_reg(struct ast_private *ast,
|
|
|
|
uint32_t base, uint8_t index)
|
|
|
|
{
|
|
|
|
uint8_t ret;
|
|
|
|
ast_io_write8(ast, base, index);
|
|
|
|
ret = ast_io_read8(ast, base + 1);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
uint8_t ast_get_index_reg_mask(struct ast_private *ast,
|
|
|
|
uint32_t base, uint8_t index, uint8_t mask)
|
|
|
|
{
|
|
|
|
uint8_t ret;
|
|
|
|
ast_io_write8(ast, base, index);
|
|
|
|
ret = ast_io_read8(ast, base + 1) & mask;
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2014-09-04 14:50:11 +07:00
|
|
|
static int ast_detect_chip(struct drm_device *dev, bool *need_post)
|
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 20:40:04 +07:00
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
2014-01-17 07:56:09 +07:00
|
|
|
uint32_t data, jreg;
|
2014-09-10 11:07:53 +07:00
|
|
|
ast_open_key(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 20:40:04 +07:00
|
|
|
|
|
|
|
if (dev->pdev->device == PCI_CHIP_AST1180) {
|
|
|
|
ast->chip = AST1100;
|
|
|
|
DRM_INFO("AST 1180 detected\n");
|
|
|
|
} else {
|
2014-03-28 06:18:45 +07:00
|
|
|
if (dev->pdev->revision >= 0x30) {
|
|
|
|
ast->chip = AST2400;
|
|
|
|
DRM_INFO("AST 2400 detected\n");
|
|
|
|
} else if (dev->pdev->revision >= 0x20) {
|
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 20:40:04 +07:00
|
|
|
ast->chip = AST2300;
|
|
|
|
DRM_INFO("AST 2300 detected\n");
|
|
|
|
} else if (dev->pdev->revision >= 0x10) {
|
|
|
|
uint32_t data;
|
|
|
|
ast_write32(ast, 0xf004, 0x1e6e0000);
|
|
|
|
ast_write32(ast, 0xf000, 0x1);
|
|
|
|
|
|
|
|
data = ast_read32(ast, 0x1207c);
|
|
|
|
switch (data & 0x0300) {
|
|
|
|
case 0x0200:
|
|
|
|
ast->chip = AST1100;
|
|
|
|
DRM_INFO("AST 1100 detected\n");
|
|
|
|
break;
|
|
|
|
case 0x0100:
|
|
|
|
ast->chip = AST2200;
|
|
|
|
DRM_INFO("AST 2200 detected\n");
|
|
|
|
break;
|
|
|
|
case 0x0000:
|
|
|
|
ast->chip = AST2150;
|
|
|
|
DRM_INFO("AST 2150 detected\n");
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
ast->chip = AST2100;
|
|
|
|
DRM_INFO("AST 2100 detected\n");
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
ast->vga2_clone = false;
|
|
|
|
} else {
|
2014-09-10 11:07:54 +07:00
|
|
|
ast->chip = AST2000;
|
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 20:40:04 +07:00
|
|
|
DRM_INFO("AST 2000 detected\n");
|
|
|
|
}
|
|
|
|
}
|
2014-01-17 07:56:09 +07:00
|
|
|
|
2014-09-04 14:50:11 +07:00
|
|
|
/*
|
|
|
|
* If VGA isn't enabled, we need to enable now or subsequent
|
|
|
|
* access to the scratch registers will fail. We also inform
|
|
|
|
* our caller that it needs to POST the chip
|
|
|
|
* (Assumption: VGA not enabled -> need to POST)
|
|
|
|
*/
|
|
|
|
if (!ast_is_vga_enabled(dev)) {
|
|
|
|
ast_enable_vga(dev);
|
|
|
|
ast_enable_mmio(dev);
|
|
|
|
DRM_INFO("VGA not enabled on entry, requesting chip POST\n");
|
|
|
|
*need_post = true;
|
|
|
|
} else
|
|
|
|
*need_post = false;
|
|
|
|
|
|
|
|
/* Check if we support wide screen */
|
2014-01-17 07:56:09 +07:00
|
|
|
switch (ast->chip) {
|
|
|
|
case AST1180:
|
|
|
|
ast->support_wide_screen = true;
|
|
|
|
break;
|
|
|
|
case AST2000:
|
|
|
|
ast->support_wide_screen = false;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
jreg = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xd0, 0xff);
|
|
|
|
if (!(jreg & 0x80))
|
|
|
|
ast->support_wide_screen = true;
|
|
|
|
else if (jreg & 0x01)
|
|
|
|
ast->support_wide_screen = true;
|
|
|
|
else {
|
|
|
|
ast->support_wide_screen = false;
|
2014-09-04 14:50:11 +07:00
|
|
|
/* Read SCU7c (silicon revision register) */
|
2014-03-28 06:18:45 +07:00
|
|
|
ast_write32(ast, 0xf004, 0x1e6e0000);
|
|
|
|
ast_write32(ast, 0xf000, 0x1);
|
|
|
|
data = ast_read32(ast, 0x1207c);
|
|
|
|
data &= 0x300;
|
|
|
|
if (ast->chip == AST2300 && data == 0x0) /* ast1300 */
|
|
|
|
ast->support_wide_screen = true;
|
|
|
|
if (ast->chip == AST2400 && data == 0x100) /* ast1400 */
|
|
|
|
ast->support_wide_screen = true;
|
2014-01-17 07:56:09 +07:00
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2014-09-04 14:50:11 +07:00
|
|
|
/* Check 3rd Tx option (digital output afaik) */
|
2014-03-28 08:05:12 +07:00
|
|
|
ast->tx_chip_type = AST_TX_NONE;
|
2014-09-04 14:50:11 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* VGACRA3 Enhanced Color Mode Register, check if DVO is already
|
|
|
|
* enabled, in that case, assume we have a SIL164 TMDS transmitter
|
2014-09-04 14:50:21 +07:00
|
|
|
*
|
|
|
|
* Don't make that assumption if we the chip wasn't enabled and
|
|
|
|
* is at power-on reset, otherwise we'll incorrectly "detect" a
|
|
|
|
* SIL164 when there is none.
|
2014-09-04 14:50:11 +07:00
|
|
|
*/
|
2014-09-04 14:50:21 +07:00
|
|
|
if (!*need_post) {
|
|
|
|
jreg = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xa3, 0xff);
|
|
|
|
if (jreg & 0x80)
|
|
|
|
ast->tx_chip_type = AST_TX_SIL164;
|
|
|
|
}
|
2014-09-04 14:50:11 +07:00
|
|
|
|
2014-03-28 08:05:12 +07:00
|
|
|
if ((ast->chip == AST2300) || (ast->chip == AST2400)) {
|
2014-09-04 14:50:11 +07:00
|
|
|
/*
|
|
|
|
* On AST2300 and 2400, look the configuration set by the SoC in
|
|
|
|
* the SOC scratch register #1 bits 11:8 (interestingly marked
|
2014-09-04 14:50:21 +07:00
|
|
|
* as "reserved" in the spec)
|
2014-09-04 14:50:11 +07:00
|
|
|
*/
|
2014-03-28 08:05:12 +07:00
|
|
|
jreg = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xd1, 0xff);
|
|
|
|
switch (jreg) {
|
|
|
|
case 0x04:
|
|
|
|
ast->tx_chip_type = AST_TX_SIL164;
|
|
|
|
break;
|
|
|
|
case 0x08:
|
|
|
|
ast->dp501_fw_addr = kzalloc(32*1024, GFP_KERNEL);
|
|
|
|
if (ast->dp501_fw_addr) {
|
|
|
|
/* backup firmware */
|
|
|
|
if (ast_backup_fw(dev, ast->dp501_fw_addr, 32*1024)) {
|
|
|
|
kfree(ast->dp501_fw_addr);
|
|
|
|
ast->dp501_fw_addr = NULL;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* fallthrough */
|
|
|
|
case 0x0c:
|
|
|
|
ast->tx_chip_type = AST_TX_DP501;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-09-04 14:50:11 +07:00
|
|
|
/* Print stuff for diagnostic purposes */
|
|
|
|
switch(ast->tx_chip_type) {
|
|
|
|
case AST_TX_SIL164:
|
|
|
|
DRM_INFO("Using Sil164 TMDS transmitter\n");
|
|
|
|
break;
|
|
|
|
case AST_TX_DP501:
|
|
|
|
DRM_INFO("Using DP501 DisplayPort transmitter\n");
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
DRM_INFO("Analog VGA only\n");
|
|
|
|
}
|
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 20:40:04 +07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ast_get_dram_info(struct drm_device *dev)
|
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
uint32_t data, data2;
|
|
|
|
uint32_t denum, num, div, ref_pll;
|
|
|
|
|
|
|
|
ast_write32(ast, 0xf004, 0x1e6e0000);
|
|
|
|
ast_write32(ast, 0xf000, 0x1);
|
|
|
|
|
|
|
|
|
|
|
|
ast_write32(ast, 0x10000, 0xfc600309);
|
|
|
|
|
|
|
|
do {
|
|
|
|
;
|
|
|
|
} while (ast_read32(ast, 0x10000) != 0x01);
|
|
|
|
data = ast_read32(ast, 0x10004);
|
|
|
|
|
|
|
|
if (data & 0x400)
|
|
|
|
ast->dram_bus_width = 16;
|
|
|
|
else
|
|
|
|
ast->dram_bus_width = 32;
|
|
|
|
|
2014-03-28 06:18:45 +07: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 20:40:04 +07:00
|
|
|
switch (data & 0x03) {
|
|
|
|
case 0:
|
|
|
|
ast->dram_type = AST_DRAM_512Mx16;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
case 1:
|
|
|
|
ast->dram_type = AST_DRAM_1Gx16;
|
|
|
|
break;
|
|
|
|
case 2:
|
|
|
|
ast->dram_type = AST_DRAM_2Gx16;
|
|
|
|
break;
|
|
|
|
case 3:
|
|
|
|
ast->dram_type = AST_DRAM_4Gx16;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
switch (data & 0x0c) {
|
|
|
|
case 0:
|
|
|
|
case 4:
|
|
|
|
ast->dram_type = AST_DRAM_512Mx16;
|
|
|
|
break;
|
|
|
|
case 8:
|
|
|
|
if (data & 0x40)
|
|
|
|
ast->dram_type = AST_DRAM_1Gx16;
|
|
|
|
else
|
|
|
|
ast->dram_type = AST_DRAM_512Mx32;
|
|
|
|
break;
|
|
|
|
case 0xc:
|
|
|
|
ast->dram_type = AST_DRAM_1Gx32;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
data = ast_read32(ast, 0x10120);
|
|
|
|
data2 = ast_read32(ast, 0x10170);
|
|
|
|
if (data2 & 0x2000)
|
|
|
|
ref_pll = 14318;
|
|
|
|
else
|
|
|
|
ref_pll = 12000;
|
|
|
|
|
|
|
|
denum = data & 0x1f;
|
|
|
|
num = (data & 0x3fe0) >> 5;
|
|
|
|
data = (data & 0xc000) >> 14;
|
|
|
|
switch (data) {
|
|
|
|
case 3:
|
|
|
|
div = 0x4;
|
|
|
|
break;
|
|
|
|
case 2:
|
|
|
|
case 1:
|
|
|
|
div = 0x2;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
div = 0x1;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
ast->mclk = ref_pll * (num + 2) / (denum + 2) * (div * 1000);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ast_user_framebuffer_destroy(struct drm_framebuffer *fb)
|
|
|
|
{
|
|
|
|
struct ast_framebuffer *ast_fb = to_ast_framebuffer(fb);
|
|
|
|
if (ast_fb->obj)
|
|
|
|
drm_gem_object_unreference_unlocked(ast_fb->obj);
|
|
|
|
|
|
|
|
drm_framebuffer_cleanup(fb);
|
|
|
|
kfree(fb);
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct drm_framebuffer_funcs ast_fb_funcs = {
|
|
|
|
.destroy = ast_user_framebuffer_destroy,
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
int ast_framebuffer_init(struct drm_device *dev,
|
|
|
|
struct ast_framebuffer *ast_fb,
|
|
|
|
struct drm_mode_fb_cmd2 *mode_cmd,
|
|
|
|
struct drm_gem_object *obj)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
2012-12-14 05:38:38 +07:00
|
|
|
drm_helper_mode_fill_fb_struct(&ast_fb->base, mode_cmd);
|
|
|
|
ast_fb->obj = obj;
|
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 20:40:04 +07:00
|
|
|
ret = drm_framebuffer_init(dev, &ast_fb->base, &ast_fb_funcs);
|
|
|
|
if (ret) {
|
|
|
|
DRM_ERROR("framebuffer init failed %d\n", ret);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct drm_framebuffer *
|
|
|
|
ast_user_framebuffer_create(struct drm_device *dev,
|
|
|
|
struct drm_file *filp,
|
|
|
|
struct drm_mode_fb_cmd2 *mode_cmd)
|
|
|
|
{
|
|
|
|
struct drm_gem_object *obj;
|
|
|
|
struct ast_framebuffer *ast_fb;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
obj = drm_gem_object_lookup(dev, filp, mode_cmd->handles[0]);
|
|
|
|
if (obj == NULL)
|
|
|
|
return ERR_PTR(-ENOENT);
|
|
|
|
|
|
|
|
ast_fb = kzalloc(sizeof(*ast_fb), GFP_KERNEL);
|
|
|
|
if (!ast_fb) {
|
|
|
|
drm_gem_object_unreference_unlocked(obj);
|
|
|
|
return ERR_PTR(-ENOMEM);
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = ast_framebuffer_init(dev, ast_fb, mode_cmd, obj);
|
|
|
|
if (ret) {
|
|
|
|
drm_gem_object_unreference_unlocked(obj);
|
|
|
|
kfree(ast_fb);
|
|
|
|
return ERR_PTR(ret);
|
|
|
|
}
|
|
|
|
return &ast_fb->base;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct drm_mode_config_funcs ast_mode_funcs = {
|
|
|
|
.fb_create = ast_user_framebuffer_create,
|
|
|
|
};
|
|
|
|
|
|
|
|
static u32 ast_get_vram_info(struct drm_device *dev)
|
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
u8 jreg;
|
2014-03-28 08:05:12 +07:00
|
|
|
u32 vram_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 20:40:04 +07:00
|
|
|
ast_open_key(ast);
|
|
|
|
|
2014-03-28 08:05:12 +07:00
|
|
|
vram_size = AST_VIDMEM_DEFAULT_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 20:40:04 +07:00
|
|
|
jreg = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0xaa, 0xff);
|
|
|
|
switch (jreg & 3) {
|
2014-03-28 08:05:12 +07:00
|
|
|
case 0: vram_size = AST_VIDMEM_SIZE_8M; break;
|
|
|
|
case 1: vram_size = AST_VIDMEM_SIZE_16M; break;
|
|
|
|
case 2: vram_size = AST_VIDMEM_SIZE_32M; break;
|
|
|
|
case 3: vram_size = AST_VIDMEM_SIZE_64M; 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 20:40:04 +07:00
|
|
|
}
|
2014-03-28 08:05:12 +07:00
|
|
|
|
|
|
|
jreg = ast_get_index_reg_mask(ast, AST_IO_CRTC_PORT, 0x99, 0xff);
|
|
|
|
switch (jreg & 0x03) {
|
|
|
|
case 1:
|
|
|
|
vram_size -= 0x100000;
|
|
|
|
break;
|
|
|
|
case 2:
|
|
|
|
vram_size -= 0x200000;
|
|
|
|
break;
|
|
|
|
case 3:
|
|
|
|
vram_size -= 0x400000;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
return vram_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 20:40:04 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
int ast_driver_load(struct drm_device *dev, unsigned long flags)
|
|
|
|
{
|
|
|
|
struct ast_private *ast;
|
2014-09-04 14:50:11 +07:00
|
|
|
bool need_post;
|
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 20:40:04 +07:00
|
|
|
int ret = 0;
|
|
|
|
|
|
|
|
ast = kzalloc(sizeof(struct ast_private), GFP_KERNEL);
|
|
|
|
if (!ast)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
dev->dev_private = ast;
|
|
|
|
ast->dev = dev;
|
|
|
|
|
|
|
|
ast->regs = pci_iomap(dev->pdev, 1, 0);
|
|
|
|
if (!ast->regs) {
|
|
|
|
ret = -EIO;
|
|
|
|
goto out_free;
|
|
|
|
}
|
2014-09-04 14:44:18 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* If we don't have IO space at all, use MMIO now and
|
|
|
|
* assume the chip has MMIO enabled by default (rev 0x20
|
|
|
|
* and higher).
|
|
|
|
*/
|
|
|
|
if (!(pci_resource_flags(dev->pdev, 2) & IORESOURCE_IO)) {
|
|
|
|
DRM_INFO("platform has no IO space, trying MMIO\n");
|
|
|
|
ast->ioregs = ast->regs + AST_IO_MM_OFFSET;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* "map" IO regs if the above hasn't done so already */
|
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 20:40:04 +07:00
|
|
|
if (!ast->ioregs) {
|
2014-09-04 14:44:18 +07:00
|
|
|
ast->ioregs = pci_iomap(dev->pdev, 2, 0);
|
|
|
|
if (!ast->ioregs) {
|
|
|
|
ret = -EIO;
|
|
|
|
goto out_free;
|
|
|
|
}
|
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 20:40:04 +07:00
|
|
|
}
|
|
|
|
|
2014-09-04 14:50:11 +07:00
|
|
|
ast_detect_chip(dev, &need_post);
|
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 20:40:04 +07:00
|
|
|
|
|
|
|
if (ast->chip != AST1180) {
|
|
|
|
ast_get_dram_info(dev);
|
|
|
|
ast->vram_size = ast_get_vram_info(dev);
|
|
|
|
DRM_INFO("dram %d %d %d %08x\n", ast->mclk, ast->dram_type, ast->dram_bus_width, ast->vram_size);
|
|
|
|
}
|
|
|
|
|
2014-09-04 14:50:11 +07:00
|
|
|
if (need_post)
|
|
|
|
ast_post_gpu(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 20:40:04 +07:00
|
|
|
ret = ast_mm_init(ast);
|
|
|
|
if (ret)
|
|
|
|
goto out_free;
|
|
|
|
|
|
|
|
drm_mode_config_init(dev);
|
|
|
|
|
|
|
|
dev->mode_config.funcs = (void *)&ast_mode_funcs;
|
|
|
|
dev->mode_config.min_width = 0;
|
|
|
|
dev->mode_config.min_height = 0;
|
|
|
|
dev->mode_config.preferred_depth = 24;
|
|
|
|
dev->mode_config.prefer_shadow = 1;
|
|
|
|
|
|
|
|
if (ast->chip == AST2100 ||
|
|
|
|
ast->chip == AST2200 ||
|
|
|
|
ast->chip == AST2300 ||
|
2014-03-28 06:18:45 +07:00
|
|
|
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 20:40:04 +07:00
|
|
|
ast->chip == AST1180) {
|
|
|
|
dev->mode_config.max_width = 1920;
|
|
|
|
dev->mode_config.max_height = 2048;
|
|
|
|
} else {
|
|
|
|
dev->mode_config.max_width = 1600;
|
|
|
|
dev->mode_config.max_height = 1200;
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = ast_mode_init(dev);
|
|
|
|
if (ret)
|
|
|
|
goto out_free;
|
|
|
|
|
|
|
|
ret = ast_fbdev_init(dev);
|
|
|
|
if (ret)
|
|
|
|
goto out_free;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
out_free:
|
|
|
|
kfree(ast);
|
|
|
|
dev->dev_private = NULL;
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
int ast_driver_unload(struct drm_device *dev)
|
|
|
|
{
|
|
|
|
struct ast_private *ast = dev->dev_private;
|
|
|
|
|
2014-03-28 08:05:12 +07:00
|
|
|
kfree(ast->dp501_fw_addr);
|
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 20:40:04 +07:00
|
|
|
ast_mode_fini(dev);
|
|
|
|
ast_fbdev_fini(dev);
|
|
|
|
drm_mode_config_cleanup(dev);
|
|
|
|
|
|
|
|
ast_mm_fini(ast);
|
|
|
|
pci_iounmap(dev->pdev, ast->ioregs);
|
|
|
|
pci_iounmap(dev->pdev, ast->regs);
|
|
|
|
kfree(ast);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int ast_gem_create(struct drm_device *dev,
|
|
|
|
u32 size, bool iskernel,
|
|
|
|
struct drm_gem_object **obj)
|
|
|
|
{
|
|
|
|
struct ast_bo *astbo;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
*obj = NULL;
|
|
|
|
|
|
|
|
size = roundup(size, PAGE_SIZE);
|
|
|
|
if (size == 0)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
ret = ast_bo_create(dev, size, 0, 0, &astbo);
|
|
|
|
if (ret) {
|
|
|
|
if (ret != -ERESTARTSYS)
|
|
|
|
DRM_ERROR("failed to allocate GEM object\n");
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
*obj = &astbo->gem;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int ast_dumb_create(struct drm_file *file,
|
|
|
|
struct drm_device *dev,
|
|
|
|
struct drm_mode_create_dumb *args)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
struct drm_gem_object *gobj;
|
|
|
|
u32 handle;
|
|
|
|
|
|
|
|
args->pitch = args->width * ((args->bpp + 7) / 8);
|
|
|
|
args->size = args->pitch * args->height;
|
|
|
|
|
|
|
|
ret = ast_gem_create(dev, args->size, false,
|
|
|
|
&gobj);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
ret = drm_gem_handle_create(file, gobj, &handle);
|
|
|
|
drm_gem_object_unreference_unlocked(gobj);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
args->handle = handle;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2014-01-06 21:30:40 +07:00
|
|
|
static void ast_bo_unref(struct ast_bo **bo)
|
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 20:40:04 +07:00
|
|
|
{
|
|
|
|
struct ttm_buffer_object *tbo;
|
|
|
|
|
|
|
|
if ((*bo) == NULL)
|
|
|
|
return;
|
|
|
|
|
|
|
|
tbo = &((*bo)->bo);
|
|
|
|
ttm_bo_unref(&tbo);
|
2014-04-05 15:10:51 +07:00
|
|
|
*bo = NULL;
|
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 20:40:04 +07:00
|
|
|
}
|
2014-04-05 15:10:51 +07:00
|
|
|
|
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 20:40:04 +07:00
|
|
|
void ast_gem_free_object(struct drm_gem_object *obj)
|
|
|
|
{
|
|
|
|
struct ast_bo *ast_bo = gem_to_ast_bo(obj);
|
|
|
|
|
|
|
|
ast_bo_unref(&ast_bo);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static inline u64 ast_bo_mmap_offset(struct ast_bo *bo)
|
|
|
|
{
|
2013-07-25 02:08:53 +07:00
|
|
|
return drm_vma_node_offset_addr(&bo->bo.vma_node);
|
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 20:40:04 +07:00
|
|
|
}
|
|
|
|
int
|
|
|
|
ast_dumb_mmap_offset(struct drm_file *file,
|
|
|
|
struct drm_device *dev,
|
|
|
|
uint32_t handle,
|
|
|
|
uint64_t *offset)
|
|
|
|
{
|
|
|
|
struct drm_gem_object *obj;
|
|
|
|
int ret;
|
|
|
|
struct ast_bo *bo;
|
|
|
|
|
|
|
|
mutex_lock(&dev->struct_mutex);
|
|
|
|
obj = drm_gem_object_lookup(dev, file, handle);
|
|
|
|
if (obj == NULL) {
|
|
|
|
ret = -ENOENT;
|
|
|
|
goto out_unlock;
|
|
|
|
}
|
|
|
|
|
|
|
|
bo = gem_to_ast_bo(obj);
|
|
|
|
*offset = ast_bo_mmap_offset(bo);
|
|
|
|
|
|
|
|
drm_gem_object_unreference(obj);
|
|
|
|
ret = 0;
|
|
|
|
out_unlock:
|
|
|
|
mutex_unlock(&dev->struct_mutex);
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
}
|
|
|
|
|