* Re: [linuxppc-dev] Unbinding device from a driver
[not found] <B2B5EF0D8FDD10429C8DE6C4C2B38282093BABDD@039-SN2MPN1-023.039d.mgd.msft.net>
@ 2013-07-08 23:33 ` Scott Wood
2013-07-09 4:47 ` Gupta Ruchika-R66431
0 siblings, 1 reply; 2+ messages in thread
From: Scott Wood @ 2013-07-08 23:33 UTC (permalink / raw)
To: Gupta Ruchika-R66431; +Cc: linuxppc-dev, linux-kernel
On 07/04/2013 05:35:28 AM, Gupta Ruchika-R66431 wrote:
> Hi,
>
>
>
> I am trying to unbind a platform device from a driver. Even when the
> remove function of the device returns an EBUSY error, the device is
> unbound from the driver. Is this the right behavior ? Why does kernel
> forcefully unbind the device even if device remove function returns
> an error ?
From looking at the code, it seems it's not allowed for a driver to
refuse the unbinding. If you can't unbind yet, you need to block until
you can (and take measures to ensure that it won't take too long).
I don't know the history of why the remove method can return an error
even though nothing seems to check it.
> root@p4080ds: ls
>
> bind ffe301000.jr ffe302000.jr ffe303000.jr ffe304000.jr uevent
> unbind
>
>
>
> root@p4080ds: echo ffe301000.jr > unbind
>
> In caam_jr_remove
>
> caam_jr ffe301000.jr: Device Busy
Is the caam_jr driver printing this, or the device model infrastructure?
-Scott
^ permalink raw reply [flat|nested] 2+ messages in thread* RE: [linuxppc-dev] Unbinding device from a driver
2013-07-08 23:33 ` [linuxppc-dev] Unbinding device from a driver Scott Wood
@ 2013-07-09 4:47 ` Gupta Ruchika-R66431
0 siblings, 0 replies; 2+ messages in thread
From: Gupta Ruchika-R66431 @ 2013-07-09 4:47 UTC (permalink / raw)
To: Wood Scott-B07421; +Cc: linuxppc-dev, linux-kernel
> -----Original Message-----
> From: Wood Scott-B07421
> Sent: Tuesday, July 09, 2013 5:04 AM
> To: Gupta Ruchika-R66431
> Cc: linuxppc-dev@linux.freescale.net; linux-kernel@vger.kernel.org
> Subject: Re: [linuxppc-dev] Unbinding device from a driver
>
> On 07/04/2013 05:35:28 AM, Gupta Ruchika-R66431 wrote:
> > Hi,
> >
> >
> >
> > I am trying to unbind a platform device from a driver. Even when the
> > remove function of the device returns an EBUSY error, the device is
> > unbound from the driver. Is this the right behavior ? Why does kernel
> > forcefully unbind the device even if device remove function returns an
> > error ?
>
> From looking at the code, it seems it's not allowed for a driver to refuse
> the unbinding. If you can't unbind yet, you need to block until you can
> (and take measures to ensure that it won't take too long).
>
> I don't know the history of why the remove method can return an error even
> though nothing seems to check it.
>
> > root@p4080ds: ls
> >
> > bind ffe301000.jr ffe302000.jr ffe303000.jr ffe304000.jr uevent
> > unbind
> >
> >
> >
> > root@p4080ds: echo ffe301000.jr > unbind
> >
> > In caam_jr_remove
> >
> > caam_jr ffe301000.jr: Device Busy
>
> Is the caam_jr driver printing this, or the device model infrastructure?
This is being printed by jr driver.
Ruchika
>
> -Scott
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-07-09 4:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <B2B5EF0D8FDD10429C8DE6C4C2B38282093BABDD@039-SN2MPN1-023.039d.mgd.msft.net>
2013-07-08 23:33 ` [linuxppc-dev] Unbinding device from a driver Scott Wood
2013-07-09 4:47 ` Gupta Ruchika-R66431
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®