On 02/24/2011 11:56 AM, Thomas Gleixner wrote: > On Thu, 24 Feb 2011, Stephen Boyd wrote: > >> >> I definitely don't want to do it for every loop. I'm fine with getting >> it every scm_call() invocation though. >> >> For now, I'll pull the end and cacheline_size variables out of the >> do-while loop. > > Why not do it correct right away and retrieve it in an __init > function? That would require an early_initcall, so hopefully that is fine. I wonder why the generic arm v7 cache operations don't do the same thing and store the dcache line size somewhere. Every dma operation is essentially calling dcache_line_size(). Perhaps some generic arm code should be determining the dcache line size really early on and storing it in the proc_info_list? Then both the dma code and scm code could query the processor for the dcache line size with something like cpu_dcache_line_size? -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
