Re: Clockgen Unable To Init Driver
Nettie Rosier
For devices on custom boards, as typical of embedded and SoC-(system-on-chip) based hardware, Linux uses platform_data to point to board-specific structures describing devices and how they are connected to the SoC. This can include available ports, chip variants, preferred modes, default initialization, additional pin roles, and so on. This shrinks the board-support packages (BSPs) and minimizes board and application specific #ifdefs in drivers.
I tried to look up the SPI documentation on FTDI website, but I could only find the D2xx driver programmer's manual, which does not have the API calls you mentioned. Also, the only SPI examples they have are in Delphi or VB6, which I can't look at. I did not find the predefined VIs you mentionned, only those for RS232. So, my best guess is that you need to call an SPI start, or that you need to set the clock after the SPI init. You should probably contact their technical support if this does not solve the issue.
A data handling function of this type must be specified during the initialization of the driver. The driver will call this function when it finishes using buffers passed to it by the application, and when it needs to be provided with buffers for the next part of the transfer.
The kernel must discover which I/O device corresponds to the IRQ number before enabling interrupts. Otherwise, for example, how could the kernel handle a signal from a SCSI disk without knowing which vector corresponds to the device? The correspondence is established while initializing each device driver (see Chapter 13).
Before activating a device that is going to use an IRQ line, the corresponding driver invokes request_irq( ). This function creates a new irqaction descriptor and initializes it with the parameter values; it then invokes the setup_irq( ) function to insert the descriptor in the proper IRQ list. The device driver aborts the operation if setup_irq( ) returns an error code, which usually means that the IRQ line is already in use by another device that does not allow interrupt sharing. When the device operation is concluded, the driver invokes the free_irq( ) function to remove the descriptor from the IRQ list and release the memory area.
I have been using the Musiland Mac driver for a couple of months and after the initial problems with firmware issues with my 01USD, 01USD 2012 and 02Dragon I finally got the Dragon to work perfectly except that the mulink. Option is very noisy.The front end used is a MacBook 4gb of ram with western digital external drive ,FireWire connected and Audirvana .Both of the 01USD I have never managed to get working.
aa06259810