diff options
author | Marcel Holtmann <marcel@holtmann.org> | 2013-04-10 08:11:35 -0700 |
---|---|---|
committer | Gustavo Padovan <gustavo.padovan@collabora.co.uk> | 2013-04-11 16:34:10 -0300 |
commit | 9f8f962c85461324d18dcb2b1b94a932494d2cc5 (patch) | |
tree | b22a3535959205a4a0ecaa36173f6a8d0da2f4e0 /drivers/mmc/Kconfig | |
parent | b3916db32c4a3124eee9f3742a2f4723731d7602 (diff) |
Bluetooth: Use separate function for BCM92035 vendor setup
Trying to squeeze every single vendor setup routine into the same function
and have it assigned all the time is actually a bad idea. Especially since
the core can handle the absence of a setup routine perfectly fine.
To make this a lot simpler for future additions of vendor setup code,
split the BCM92035 setup into its own function and only assign it when
this specific device has been detected.
Doing it like this has the nice side benefit that we do not have to keep
a copy of the driver_info around.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Diffstat (limited to 'drivers/mmc/Kconfig')
0 files changed, 0 insertions, 0 deletions