From: Greg KH <greg@kroah.com>
To: Tony Olech <tony.olech@elandigitalsystems.com>
Cc: Andrew Morton <akpm@osdl.org>,
Kernel Development List <linux-kernel@vger.kernel.org>,
USB Development List <linux-usb-devel@lists.sourceforge.net>,
Bart Prescott <bart.prescott@elandigitalsystems.com>
Subject: Re: USB: ftdi-elan: client driver for ELAN Uxxx adapters - 3rd attempt
Date: Wed, 20 Sep 2006 15:00:40 -0700 [thread overview]
Message-ID: <20060920220040.GB15138@kroah.com> (raw)
In-Reply-To: <1158143165.4328.11.camel@n04-207.elan.private>
On Wed, Sep 13, 2006 at 11:26:04AM +0100, Tony Olech wrote:
> This "ftdi-elan" module is one half of the "driver" for
> ELAN's Uxxx series adapters which are USB to PCMCIA CardBus
> adapters. Currently only the U132 adapter is available and
> it's module is called "u132-hcd".
>
> When the USB hot plug subsystem detects a Uxxx series adapter
> it should load this module.
>
> Upon a successful device probe() the jtag device file interface
> is created and the status workqueue started up.
>
> The jtag device file interface exists for the purpose of
> updating the firmware in the Uxxx series adapter, but as
> yet it had never been used.
>
> The status workqueue initializes the Uxxx and then sits there
> polling the Uxxx until a supported PCMCIA CardBus device is
> detected it will start the command and respond workqueues
> and then load the module that handles the device. This will
> initially be only the u132-hcd module. The status workqueue
> then just polls the Uxxx looking for card ejects.
>
> The command and respond workqueues implement a command
> sequencer for communicating with the firmware on the other
> side of the FTDI chip in the Uxxx. This "ftdi-elan" module
> exports some functions to interface with the sequencer.
>
> Note that this module is a USB client driver.
>
> Note that the "u132-hcd" module is a (cut-down OHCI)
> host controller.
>
> Thus we have a topology with the parent of a host controller
> being a USB client! This really stresses the USB subsystem
> semaphore/mutex handling in the module removal.
>
> Signed-off-by: Tony Olech <tony.olech@elandigitalsystems.com>
I've applied this and fixed the build issue (again with the
drivers/usb/Makefile file) and the Kconfig entries don't need to be
duplicated so many times :)
Also, I've fixed up the sparse warnings, but you are doing something
very wierd with the user buffer still, and I get these warnings:
drivers/usb/misc/ftdi-elan.c:1231:65: warning: dereference of noderef expression
drivers/usb/misc/ftdi-elan.c:1237:65: warning: dereference of noderef expression
with sparse still. I think it's a bunch of debug code that is remaining
in that function, care to send me a follow-on patch that removes it?
thanks,
greg k-h
parent reply other threads:[~2006-09-20 22:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1158143165.4328.11.camel@n04-207.elan.private>]
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=20060920220040.GB15138@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=bart.prescott@elandigitalsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=tony.olech@elandigitalsystems.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
all inboxes | Powered by JetHome®