* Hiremath, Vaibhav hvaib...@ti.com [130409 22:16]:
Agreed on making it as a module.
But do you think we should allow it as a loadable module (M) as well,
as user will loose Connectivity to JTAG during boot.
Another perspective here would be, user can insert the module and
Get JTAG
: OMAP2+: Add command line parameter
for debugSS module control
Hi,
* hvaib...@ti.com hvaib...@ti.com [130304 03:40]:
From: Vaibhav Hiremath hvaib...@ti.com
Currently there is no clean mechanism to control debugSS module and
you have to always keep clocks enabled, either
* Hiremath, Vaibhav hvaib...@ti.com [130409 01:12]:
From: Tony Lindgren [mailto:t...@atomide.com]
I suggest you just make this part into a standard DT only
device driver. That way the command line parsing and clock
enabling can happen the normal way.
That’s good idea, as we are
: OMAP2+: Add command line parameter
for debugSS module control
* Hiremath, Vaibhav hvaib...@ti.com [130409 01:12]:
From: Tony Lindgren [mailto:t...@atomide.com]
I suggest you just make this part into a standard DT only
device driver. That way the command line parsing and clock
Hi,
* hvaib...@ti.com hvaib...@ti.com [130304 03:40]:
From: Vaibhav Hiremath hvaib...@ti.com
Currently there is no clean mechanism to control debugSS module and
you have to always keep clocks enabled, either,
- By enabling it during boot as part of clk_init function.
Or
- By
