Re: [RFC PATCHv4 2/7] HSI: omap_ssi: Introducing OMAP SSI driver

2010-12-20 Thread Carlos Chinea
Hi Tony,

On Fri, 2010-12-17 at 16:30 -0800, ext Tony Lindgren wrote:
 * Carlos Chinea carlos.chi...@nokia.com [101214 02:13]:
  Introduces the OMAP SSI driver in the kernel.
  
  The Synchronous Serial Interface (SSI) is a legacy version
  of HSI. As in the case of HSI, it is mainly used to connect
  Application engines (APE) with cellular modem engines (CMT)
  in cellular handsets.
  
  It provides a multichannel, full-duplex, multi-core communication
  with no reference clock. The OMAP SSI block is capable of reaching
  speeds of 110 Mbit/s.
 ...
 
  +static int __init ssi_init(void)
  +{
  +   return platform_device_register(ssi_pdev);
  +}
  +subsys_initcall(ssi_init);
 
 Is this safe to do for all omaps2+ machines?
 

Well, I think it is safe. SSI will be only built in, if it is explicitly
configured for that specific machine. And AFAIK, at susbsys initcall
time all other initializations that the OMAP SSI driver may need, will
be already in place.

But I may missed something here ?

Br,
-- 
Carlos Chinea carlos.chi...@nokia.com

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [RFC PATCHv4 2/7] HSI: omap_ssi: Introducing OMAP SSI driver

2010-12-17 Thread Tony Lindgren
* Carlos Chinea carlos.chi...@nokia.com [101214 02:13]:
 Introduces the OMAP SSI driver in the kernel.
 
 The Synchronous Serial Interface (SSI) is a legacy version
 of HSI. As in the case of HSI, it is mainly used to connect
 Application engines (APE) with cellular modem engines (CMT)
 in cellular handsets.
 
 It provides a multichannel, full-duplex, multi-core communication
 with no reference clock. The OMAP SSI block is capable of reaching
 speeds of 110 Mbit/s.
...

 +static int __init ssi_init(void)
 +{
 + return platform_device_register(ssi_pdev);
 +}
 +subsys_initcall(ssi_init);

Is this safe to do for all omaps2+ machines?

Regards,

Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html