bebob: Add support for M-Audio special Firewire series

This commit allows this driver to support some models which M-Audio produces
with DM1000 but its firmware is special. They are:
 - Firewire 1814
 - ProjectMix I/O

They have heavily customized firmware. The usual operations can't be applied to
them. For this reason, this commit adds some model specific members in 'struct
snd_bebob' and model specific functions. Some parameters are write-only so this
commit also adds control interface for them.

M-Audio special firmware quirks:
 - Just after powering on, they wait to download firmware. This state is
   changed when receiving cue. Then bus reset is generated and the device is
   recognized as a different model with the uploaded firmware.
 - They don't respond against BridgeCo AV/C extension commands. So drivers
   can't get their stream formations and so on.
 - They do not start to transmit packets only by establishing connection but
   also by receiving SIGNAL FORMAT command.
 - They can't handle frequent transactions. In this reason, this driver often
   fail to handle them.

This module don't support to upload firmware.
bebob: Send a cue to load firmware for M-Audio Firewire series

This commit is optional. The purpose of this commit is to help testers.

Just powering on, these devices below wait to download firmware.
 - Firewire Audiophile
 - Firewire 410
 - Firewire 1814
 - ProjectMix I/O

But firmware version 5058 or later, flash memory in the device stores the
firmware. So this driver can enable these devices by sending a certain cue to
load the firmware. To reading these codes, this cue is a kind of Bootloader
Commands. The role of this cue is to initialize configuration to factory
settings.

I think this functionality should be implemented in user-land. FFADO already
have 'ffado-bridgeco-downloader' to take the device to download firmware. To
read these codes, this cue is a kind of Bootloader Commands. The role of this
cue is to initialize configuration to factory settings