On Tuesday 31 August 2010 09:46 PM, Cousson, Benoit wrote:
On 8/31/2010 4:41 PM, ABRAHAM, KISHON VIJAY wrote:
On Tuesday 31 August 2010 01:43 PM, Felipe Balbi wrote:
On Tue, 31 Aug 2010 10:53:36 +0530, kishonwrote:
Though driver shouldn't be using hwmod direct
On 8/31/2010 4:41 PM, ABRAHAM, KISHON VIJAY wrote:
On Tuesday 31 August 2010 01:43 PM, Felipe Balbi wrote:
On Tue, 31 Aug 2010 10:53:36 +0530, kishon wrote:
Though driver shouldn't be using hwmod directly, there is no
corresponding API in omap_device to do the same. So we are planni
On Tuesday 31 August 2010 01:43 PM, Felipe Balbi wrote:
On Tue, 31 Aug 2010 10:53:36 +0530, kishon wrote:
Though driver shouldn't be using hwmod directly, there is no
corresponding API in omap_device to do the same. So we are planning to
store the omap_hwmod structure in platf
On Tue, 31 Aug 2010 10:53:36 +0530, kishon wrote:
> Though driver shouldn't be using hwmod directly, there is no
> corresponding API in omap_device to do the same. So we are planning to
> store the omap_hwmod structure in platform_data during
> arch_initcall (in the callback to omap_hw
On Monday 30 August 2010 08:56 PM, Kevin Hilman wrote:
Kishon Vijay Abraham I writes:
Though the sysconfig register values shouldn't be modified directly by
the driver, MCBSP should be considered a special case where sysconfig
registers need to be modified dynamically by the driver.
For
