On Mon, Mar 5, 2012 at 6:10 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> * Rob Clark <rob.clark@xxxxxxxxxx> [120305 08:24]:
>> From: Andy Gross <andy.gross@xxxxxx>
>>
>> Register OMAP DRM/KMS platform device, and reserve a CMA region for
>> the device to use for buffer allocation. DMM is split into a
>> separate device using hwmod.
>> --- a/arch/arm/plat-omap/common.c
>> +++ b/arch/arm/plat-omap/common.c
>> @@ -21,10 +21,10 @@
>> #include <plat/board.h>
>> #include <plat/vram.h>
>> #include <plat/dsp.h>
>> +#include <plat/drm.h>
>>
>> #include <plat/omap-secure.h>
>>
>> -
>> #define NO_LENGTH_CHECK 0xffffffff
>>
>> struct omap_board_config_kernel *omap_board_config __initdata;
>> @@ -65,6 +65,7 @@ const void *__init omap_get_var_config(u16 tag, size_t *len)
>>
>> void __init omap_reserve(void)
>> {
>> + omapdrm_reserve_vram();
>> omapfb_reserve_sdram_memblock();
>> omap_vram_reserve_sdram_memblock();
>> omap_dsp_reserve_sdram_memblock();
>
> Tomi needs to look at the vram changes here.
it is just setting up a CMA region (if CMA is enabled.. basically for
once CMA is merged)
after CMA is merged, other drivers should be migrated to use CMA, and
omap_vram removed.. but that is a topic for another patch
>> --- /dev/null
>> +++ b/arch/arm/plat-omap/drm.c
>
> This file would be better in mach-omap2/drm.c. I doubt that this will
> ever be usable for omap1. But other than that, up to Tomi.
I was attempting to copy what omapfb was doing (plat-omap/fb.c)
because I wasn't really sure about plat-omap vs mach-omap2, although
on closer inspection I think the file I was looking at is actually for
the legacy omapdss1.. So I'll move this stuff under mach-omap2 and
resubmit this patch.
BR,
-R
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
