Re: [PATCH] Ramoops: use the platform data structure instead ofmodule params

From: Kyungmin Park
Date: Mon Aug 23 2010 - 02:53:58 EST


On Mon, Aug 23, 2010 at 3:48 PM, Marco Stornelli
<marco.stornelli@xxxxxxxxx> wrote:
> 2010/8/18 Kyungmin Park <kmpark@xxxxxxxxxxxxx>:
>> From: Kyungmin Park <kyungmin.park@xxxxxxxxxxx>
>>
>> As each board and system has different memory for ramoops. It's better to define the platform data instead of module params.
>>
>> Signed-off-by: Kyungmin Park <kyungmin.park@xxxxxxxxxxx>
>> ---
>
> It seems good. Currently there isn't any code that register a ramoops
> device, isn't it?

At this time

I wrote it below

static struct ramoops_platform_data goni_ramoops_data = {
.mem_size = SZ_16K,
.mem_address = 0xED000000, /* MODEM SRAM */
};

static struct platform_device goni_ramoops = {
.name = "ramoops",
.dev = {
.platform_data = &goni_ramoops_data,
},
};

Thank you,
Kyungmin Park
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/