tegra124: move FB_SIZE_MB to a more appropriate location

This just moves FB_SIZE_MB to a more suitable location. It was likely
placed in addressmap.h originally since it was together with some
other constants which relied on config variables. But now those are
determined via helper functions instead.

BUG=none
BRANCH=none
TEST=compiled and booted on nyan
Signed-off-by: David Hendricks <dhendrix@chromium.org>

Change-Id: I9b03839bbe8924c313c45a81af85b3db6f464add
Reviewed-on: https://chromium-review.googlesource.com/184930
Reviewed-by: Julius Werner <jwerner@chromium.org>
Commit-Queue: David Hendricks <dhendrix@chromium.org>
Tested-by: David Hendricks <dhendrix@chromium.org>
This commit is contained in:
David Hendricks 2014-02-03 16:33:45 -08:00 committed by chrome-internal-fetch
commit ddea486fd4
4 changed files with 6 additions and 4 deletions

View file

@ -18,7 +18,7 @@
*/
#include <cbmem.h>
#include <soc/addressmap.h>
#include <soc/display.h>
#include <soc/nvidia/tegra124/sdram.h>
void *cbmem_top(void)

View file

@ -80,6 +80,4 @@ enum {
TEGRA_I2C_BASE_COUNT = 6,
};
#define FB_SIZE_MB (32)
#endif /* __SOC_NVIDIA_TEGRA124_INCLUDE_SOC_ADDRESS_MAP_H__ */

View file

@ -188,6 +188,7 @@
#define COLORDEPTH 0x6
#define COLOR_WHITE 0xFFFFFF
struct soc_nvidia_tegra124_config; /* forward declaration */
void setup_display(struct soc_nvidia_tegra124_config *config);
void init_dca_regs(void);
void dp_io_powerup(void);
@ -195,4 +196,7 @@ u32 dp_setup_timing(u32 width, u32 height);
void dp_misc_setting(u32 panel_bpp, u32 width, u32 height, u32 winb_addr,
u32 lane_count, u32 enhanced_framing, u32 panel_edp,
u32 pclkfreq, u32 linkfreq);
#define FB_SIZE_MB (32)
#endif /* __SOC_NVIDIA_TEGRA124_INCLUDE_SOC_DISPLAY_H__ */

View file

@ -23,7 +23,7 @@
#include <device/device.h>
#include <soc/nvidia/tegra/dc.h>
#include <soc/nvidia/tegra124/sdram.h>
#include <soc/addressmap.h>
#include <soc/display.h>
/* this sucks, but for now, fb size/location are hardcoded.
* Will break if we get 2. Sigh.