From: Felipe Balbi <felipe.lima@indt.org.br>
To: ext David Brownell <david-b@pacbell.net>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] MUSB HDRC: RMMOD fixing
Date: Wed, 17 Jan 2007 16:28:03 -0400 [thread overview]
Message-ID: <1169065683.14795.12.camel@balbi> (raw)
In-Reply-To: <200701171157.26218.david-b@pacbell.net>
Hi Dave,
Of course I still have a few patches to scrub out from my queue too;
> but this isn't one of them.
>
> - Dave
If you check the source code itself, you'll see musb_writeb
duplicated...
could you clarify why we need that?
Here's the code I'm talking about:
static void musb_free(struct musb *musb)
{
/* this has multiple entry modes. it handles fault cleanup after
* probe(), where things may be partially set up, as well as rmmod
* cleanup after everything's been de-activated.
*/
#ifdef CONFIG_SYSFS
device_remove_file(musb->controller, &dev_attr_mode);
device_remove_file(musb->controller, &dev_attr_cable);
#endif
#ifdef CONFIG_USB_GADGET_MUSB_HDRC
musb_gadget_cleanup(musb);
#endif
if (musb->nIrq >= 0) {
disable_irq_wake(musb->nIrq);
free_irq(musb->nIrq, musb);
}
if (is_dma_capable() && musb->pDmaController) {
struct dma_controller *c = musb->pDmaController;
(void) c->stop(c->pPrivateData);
dma_controller_factory.destroy(c);
}
musb_writeb(musb->pRegs, MGC_O_HDRC_DEVCTL, 0);
musb_platform_exit(musb);
musb_writeb(musb->pRegs, MGC_O_HDRC_DEVCTL, 0);
if (musb->clock) {
clk_disable(musb->clock);
clk_put(musb->clock);
}
#ifdef CONFIG_USB_MUSB_HDRC_HCD
usb_put_hcd(musb_to_hcd(musb));
#else
kfree(musb);
#endif
}
--
Best Regards,
Felipe Balbi
felipe.lima@indt.org.br
Nokia Institute of Technology - INdT
Kernel Developers Team
+55 92 8127 0839
next prev parent reply other threads:[~2007-01-17 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 19:39 [PATCH] MUSB HDRC: RMMOD fixing Felipe Balbi
2007-01-17 19:57 ` David Brownell
2007-01-17 20:28 ` Felipe Balbi [this message]
2007-01-18 19:39 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1169065683.14795.12.camel@balbi \
--to=felipe.lima@indt.org.br \
--cc=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.