lkml.org 
[lkml]   [2012]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2 3/3] ARM: OMAP: ocp2scp: create omap device for ocp2scp
On Fri, Oct 26, 2012 at 10:21:41AM -0700, Tony Lindgren wrote:
> * Arnd Bergmann <arnd@arndb.de> [121026 00:48]:
> > On Friday 26 October 2012, Felipe Balbi wrote:
> > > > +static void omap_init_ocp2scp(void)
> > > > +{
> > > > + struct omap_hwmod *oh;
> > > > + struct platform_device *pdev;
> > > > + int bus_id = -1, dev_cnt = 0, i;
> > > > + struct omap_ocp2scp_dev *ocp2scp_dev;
> > > > + const char *oh_name, *name;
> > > > + struct omap_ocp2scp_platform_data *pdata;
> > > > +
> > > > + oh_name = "ocp2scp_usb_phy";
> > > > + name = "omap-ocp2scp";
> > >
> > > how about adding checks here to return early case we're not running on
> > > OMAP4 or OMAP5 ??
> > >
> >
> > I suppose even OMAP4-only, since OMAP5 always has DT enabled.
>
> Hmm yes, currently omap_hwmod_lookup(oh_name) produces
> bogus errors for other omaps as the hwmod data is only
> there for omap4.

shouldn't that be fixed too ? I mean, if data isn't just return -ENODEV
or something similar.

--
balbi
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2012-10-26 23:01    [W:0.085 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site