On 2013年09月30日 17:25, amit daniel kachhap wrote:
Hi Hanjun,
I was on leave last week so not much progress happened. However I am still working on modifying the timer and updating the GTDT table to add new fields like frequency. Also I checked some of your work in converting to platform driver. I guess it is not possible to convert timer driver to platform driver as it is called much before ACPI namespaces are initialised.
Yes, for arch timer, it is impossible to convert to platform driver. actually, I was working on the fixed clock converting to ACPI and I found out that fixed clock can be converted to platform driver, that's why I was sending some clean up patches for platform driver.
So I am thinking of converting GTDT(generic timer description) table to TDT(timer description) table. Arm internal timer(as generic timer) will be one of the entry in TDT table. My idea is similar to MADT table where different types of IOAPIC entry exists in the same table.
Good idea.
The new TDT table may look something like,
struct acpi_table_tdt { u64 address; u32 size; u32 flags;// MEMORY_MAPPED, TDT_GENERIC, TDT_OTHERS u8 id[10]; // like "ARMv8", "MCT"(for andale), etc.. u32 interrupt_count; // between 1-8 u32 interrupt_num[8] ;// each timer assumed to have max 8 interrupt lines u32 interrupt_flags[8]; // INTERRUPT MODE, POLARITY u32 freq;
};
Any comment about this?
This idea looks good to me, and we should work out some thing more specific and detail. and a question, can we add the fixed clock to the table? this clock is also initialized early, but with no interrupts.
On Thu, Sep 26, 2013 at 2:57 PM, Hanjun Guo hanjun.guo@linaro.org wrote:
Hi Amit,
Any updates to this patch set?
if not, I will modify your patch to convert arch_timer :)
Certainly if you have any ideas please go ahead and modify this patch. No issue :)
I will still work on the fixed clock before I can back to arch timer, so if any updates from you, send them out :)
Thanks Hanjun