ANDROID: usb: gadget: android_f_accessory: use spinlock instead of

mutex lock

The configfs_composite_disconnect function was holding a spin lock, and
the android_acc_disconnect function was holding a mutex lock. As a
result of this, sleeping function called from invalid context error was
coming.

[  106.229993][  T987] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:289
[  106.231143][  T987] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 987, name: android.hardwar
[  106.232305][  T987] preempt_count: 1, expected: 0   //hold spin_lock_irqsave(&gi->spinlock, flags) and preempt_count will plus one
[  106.232899][  T987] RCU nest depth: 0, expected: 0
[  106.233505][  T987] Preemption disabled at:
[  106.233507][  T987] [<ffffffdaa1a288f0>] configfs_composite_disconnect+0x2c/0x6c
[  106.234055][  T987] CPU: 6 PID: 987 Comm: android.hardwar Tainted: G        W  OE      6.6.17-android15-1-ge8779207b2e9 #1
[  106.236422][  T987] Hardware name: MT6991(ENG) (DT)
[  106.236425][  T987] Call trace:
[  106.236426][  T987]  dump_backtrace+0xec/0x138
[  106.236434][  T987]  show_stack+0x18/0x24
[  106.236437][  T987]  dump_stack_lvl+0x50/0x6c
[  106.236449][  T987]  dump_stack+0x18/0x24
[  106.236452][  T987]  __might_resched+0x150/0x170
[  106.236458][  T987]  __might_sleep+0x48/0x7c
[  106.236460][  T987]  mutex_lock+0x24/0x74
[  106.236465][  T987]  android_acc_disconnect+0x1c/0xe0
[  106.236472][  T987]  __composite_disconnect+0x20/0x12c

Steps to reproduce the issue:
1. Connect the Android device via USB cable to the computer.
2. Open the USB Preference to change the USB function.
3. Select the MTP, PTP, or other USB function and switch it.
4. Kernel log will show this Warning log after switch USB function.

Test: manually tested the above steps, and successfully switch between
USB modes.
Bug: 322732675

Change-Id: I8131595b02ecb2631defcca4cdde456d83f76525
Signed-off-by: Ashish Kumar Gupta <kumarashishg@google.com>