* Felipe Balbi <balbi@xxxxxx> [120611 00:19]: > On Sun, Jun 10, 2012 at 11:34:17PM -0700, Tony Lindgren wrote: > > Hi, > > > > Similar comments to the asess patch on this one below. > > > > * Paul Walmsley <paul@xxxxxxxxx> [120610 17:57]: > > > --- /dev/null > > > +++ b/include/linux/platform_data/fsusb.h > > > > This would be better as include/linux/platform_data/omap-usb.h. > > > > > +#include <plat/omap_hwmod.h> > > > > This include should not be needed here if the hwmod function is > > a static function in the some hwmod*.c file. > > > > > +/* HCCOMMANDSTATUS: the register offset of the HCCOMMANDSTATUS register */ > > > +#define HCCOMMANDSTATUS 0x0008 > > > + > > > +/* HCCOMMANDSTATUS_HCR: the bitmask of the host controller reset flag */ > > > +#define HCCOMMANDSTATUS_HCR_MASK (1 << 0) > > > > I think these already have standard defines in some OHCI header? > > Felipe may be able to comment more on this? > > Well, yeah... but it's defined on drivers/usb/host/ohci.h and it's > actually a structure: OK I guess then the define is OK. > > This should be "static inline int fsusb_reset_host_controller" as it's > > in a header. > > why is it even in a header ? Only hwmod_fsusb_preprogram() will use it > anyway. Well ideally it would be something that any OHCI driver can use for it's reset, and whatever bus code can also call to reset and idle for the unused devices that don't have the driver compiled in. Got any better suggestions where to place it? I could be a generic ohci_reset function in some header? I don't want to have driver specific code under arch/arm/*omap*/* as the bus level code should not need to know anything about the driver specific registers. Regards, Tony -- 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
