From: Johannes Erdfelt <johannes@erdfelt.com>
To: Greg KH <greg@kroah.com>
Cc: Joerg Pommnitz <pommnitz@yahoo.com>,
linux-usb-users@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Software based unplug of USB device?
Date: Mon, 3 May 2004 11:10:33 -0700 [thread overview]
Message-ID: <20040503181033.GS1542@sventech.com> (raw)
In-Reply-To: <20040503145413.GA31691@kroah.com>
On Mon, May 03, 2004, Greg KH <greg@kroah.com> wrote:
> On Mon, May 03, 2004 at 12:21:20PM +0200, Joerg Pommnitz wrote:
> > Hello listees,
> > we are struggling with a 3rd party USB device. It comes with its own
> > firmware and its own Linux USB serial drivers.
>
> Which device and driver is this? Do you have a pointer to the driver?
>
> > Unfortunately the
> > communication between the device and the user application seems to break
> > down from time to time. This situation can easily be resolved by
> > unplugging and then re-plugging the device. Unfortunately this requires
> > manual intervention.
> > While resolving the real issue would be the preferred way to deal with
> > this problem, we would settle for a way to do a software unplug/re-plug.
>
> Do you want to do this from within the kernel, or from userspace? If
> from within the kernel, you should be able to drop the power to a hub
> port and reenable it, but I haven't checked to see if that works in a
> long time.
Wouldn't usb_reset_device() work? That's assuming the device isn't
totally and completely hosed.
It can be done via usbfs as well.
JE
prev parent reply other threads:[~2004-05-03 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 10:21 Software based unplug of USB device? Joerg Pommnitz
2004-05-03 11:07 ` Duncan Sands
2004-05-03 14:54 ` Greg KH
2004-05-03 18:10 ` Johannes Erdfelt [this message]
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=20040503181033.GS1542@sventech.com \
--to=johannes@erdfelt.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=pommnitz@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox