On Thursday 29 August 2013 01:20 PM, Kevin Hilman wrote:
> Rajendra Nayak <rnayak@xxxxxx> writes:
>
>> In order to handle errata I688, a page of sram was reserved by doing a
>> static iotable map. Now that we use gen_pool to manage sram, we can
>> completely remove all of these static mappings and use gen_pool_alloc()
>> to get the one page of sram space needed to implement errata I688.
>>
>> Suggested-by: Sekhar Nori <nsekhar@xxxxxx>
>> Signed-off-by: Rajendra Nayak <rnayak@xxxxxx>
>
> [...]
>
>> @@ -71,6 +72,21 @@ void omap_bus_sync(void)
>> }
>> EXPORT_SYMBOL(omap_bus_sync);
>>
>> +static int __init omap4_sram_init(void)
>> +{
>> + struct device_node *np;
>> + struct gen_pool *sram_pool;
>> +
>> + np = of_find_compatible_node(NULL, NULL, "ti,omap4-mpu");
>> + if (!np)
>> + pr_warn("%s:Unable to allocate sram needed to handle errata I688\n",
>> + __func__);
>> + sram_pool = of_get_named_gen_pool(np, "sram", 0);
>
> I haven't actually tested this, but if there is no 'sram' property defined...
>
If the sram property is not defined, the bus_sync will be just a nop. Below
check will take care of it.
if (dram_sync && sram_sync)
Regards,
Santosh
--
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
