Re: [RFC][DRAFT] TODO list for TI DSP BRIDGE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 18, 2008 at 10:28 PM, Kanigeri, Hari <h-kanigeri2@xxxxxx> wrote:
>> If you mean there is separate clock infrastructure for DSPBridge other
>> than clock framework we have for OMAP, then DSPBridge should convert
>> to the one we have for OMAP. As recent work by Paul for clock
>> framework on OMAP3 and Power domains we need centralized code for clk
>> and power domains not separate clock infrastructure for DSPBridge.
>>
> --- Bridge is not implementing separate clock infrastructure. It is just centralizing the calls to clk_enable in one location as this is called from multiple files in Bridge code. This helps because one can then turn on the traces only for clock module to check if the clocks that were expected to be enabled are enabled or not. As I mentioned before, this helps in debugging.

That only makes the code harder to understand.

#define clk_enable(...) my_debug_function(__VA_ARGS__)

Achieves the same thing.

-- 
Felipe Contreras
--
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

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux