Hi Andy,
You memtion that you got PMEM working before. Can you tell me what are your
configurations in the kernel? Do you have the following definitions?
static struct platform_device android_pmem_device = {
.name = "android_pmem",
.id = 0,
.dev = { .platform_data = &android_pmem_pdata },
};
static struct platform_device android_pmem_adsp_device = {
.name = "android_pmem",
.id = 1,
.dev = { .platform_data = &android_pmem_adsp_pdata },
};
static struct platform_device android_pmem_gpu0_device = {
.name = "android_pmem",
.id = 2,
.dev = { .platform_data = &android_pmem_gpu0_pdata },
};
static struct platform_device android_pmem_gpu1_device = {
.name = "android_pmem",
.id = 3,
.dev = { .platform_data = &android_pmem_gpu1_pdata },
};
Just curious, where does the MSM_PMEM_GPU0_BASE address map to in the memory?
Thank you,
Neil
--- On Thu, 7/9/09, Andy Quan <[email protected]> wrote:
> From: Andy Quan <[email protected]>
> Subject: [android-porting] PMEM cache flush operation
> To: [email protected]
> Date: Thursday, July 9, 2009, 9:09 PM
>
> Hi,
> I am working on PMEM sharing between opencore and
> surfaceflinger in Android 1.5. I find that PMEM can be
> configured to be cacheable but there is no corresponding
> cache flush ioctl for this device.
>
> Since PMEM is the dedicated physical memory for
> android, there can be cases that a software video unit wants
> to share YUV buffer without extra copy with hardware GPU
> inside surfaceflinger. For SW video unit, it is unacceptable
> to configure PMEM to be non-cacheable as there would
> definitely be huge performance downgrade.
>
>
> Any thoughts on this?
>
> --
> Thanks,
> Andy
>
>
>
>
> --
> Thanks,
> Andy
>
>
> >
>
>
>
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
