On Fri, 8 Feb 2008, David Brownell wrote:
> > Yes, that's what I'm saying. I had a GPIO in use and rmmod-ed pca953x. It
> > did produce an error message
> >
> > pca953x 0-0041: gpiochip_remove() failed, -16
> >
> > , but rmmod completed.
>
> Doesn't that seem buglike to you?
>
> Oh, right --
On Fri, 8 Feb 2008, David Brownell wrote:
Yes, that's what I'm saying. I had a GPIO in use and rmmod-ed pca953x. It
did produce an error message
pca953x 0-0041: gpiochip_remove() failed, -16
, but rmmod completed.
Doesn't that seem buglike to you?
Oh, right -- the module exit
> > > As long as one or more GPIOs on a gpio chip are used its driver should
> > > not
> > > be unloaded.
> >
> > The mechanism currently in place is to have gpiochip_remove() fail
> > if the platform's teardown() logic doesn't reject it. (It may be
> > practical to have the teardown code get
On Fri, 8 Feb 2008, David Brownell wrote:
> On Friday 08 February 2008, Guennadi Liakhovetski wrote:
> > As long as one or more GPIOs on a gpio chip are used its driver should not
> > be unloaded.
>
> The mechanism currently in place is to have gpiochip_remove() fail
> if the platform's
On Friday 08 February 2008, Guennadi Liakhovetski wrote:
> As long as one or more GPIOs on a gpio chip are used its driver should not
> be unloaded.
The mechanism currently in place is to have gpiochip_remove() fail
if the platform's teardown() logic doesn't reject it. (It may be
practical to
As long as one or more GPIOs on a gpio chip are used its driver should not
be unloaded.
Signed-off-by: Guennadi Liakhovetski <[EMAIL PROTECTED]>
---
Note, that existing drivers do not have to be modified, for example those,
that are always statically linked in the kernel, as long as the
On Friday 08 February 2008, Guennadi Liakhovetski wrote:
As long as one or more GPIOs on a gpio chip are used its driver should not
be unloaded.
The mechanism currently in place is to have gpiochip_remove() fail
if the platform's teardown() logic doesn't reject it. (It may be
practical to
On Fri, 8 Feb 2008, David Brownell wrote:
On Friday 08 February 2008, Guennadi Liakhovetski wrote:
As long as one or more GPIOs on a gpio chip are used its driver should not
be unloaded.
The mechanism currently in place is to have gpiochip_remove() fail
if the platform's teardown()
As long as one or more GPIOs on a gpio chip are used its driver should not
be unloaded.
Signed-off-by: Guennadi Liakhovetski [EMAIL PROTECTED]
---
Note, that existing drivers do not have to be modified, for example those,
that are always statically linked in the kernel, as long as the
9 matches
Mail list logo
