From mboxrd@z Thu Jan  1 00:00:00 1970
From: Greg KH <greg@kroah.com>
Date: Wed, 29 Apr 2009 18:12:50 +0000
Subject: Re: Best practice for loading platform modules
Message-Id: <20090429181250.GA29954@kroah.com>
List-Id: <linux-hotplug.vger.kernel.org>
References: <c4aed99f0904291105u1d4c0081qe91969a3ada64c96@mail.gmail.com>
In-Reply-To: <c4aed99f0904291105u1d4c0081qe91969a3ada64c96@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

On Wed, Apr 29, 2009 at 11:11:35AM -0700, Greg KH wrote:
> On Wed, Apr 29, 2009 at 02:05:37PM -0400, Chris Hallinan wrote:
> > I have an OMAP3 board, and want usb (host mode) configured as a
> > loadable module.  Using a generic rule such as this:
> > RUN+="/sbin/modprobe -b $env{MODALIAS}"
> > 
> > ends up passing "platform:musb_hdrc" to modprobe, which obviously
> > fails.
> 
> Why would that fail?  Do you have the proper modalias in the kernel
> module to handle this?  If not, can you add it?

I see:
	MODULE_ALIAS("platform:" MUSB_DRIVER_NAME);
in the musb code, perhaps MUSB_DRIVER_NAME is not set correctly to be
"musb_hdrc" somehow?

thanks,

greg k-h