Use mtp-responder-dummy.socket when there is no mtp-responser.socket 82/225182/3 accepted/tizen/unified/20200220.122433 submit/tizen/20200218.230813
authorINSUN PYO <insun.pyo@samsung.com>
Tue, 18 Feb 2020 04:41:52 +0000 (13:41 +0900)
committerINSUN PYO <insun.pyo@samsung.com>
Tue, 18 Feb 2020 06:15:10 +0000 (15:15 +0900)
commit0202291b7c1b3be3db32bba3001d51d7efe6a362
tree2f9976cf3edcc50fe3444dace7a52ae18e2a6f86
parent0c129c2561c2e62f2176e4435412a969b4617fb2
Use mtp-responder-dummy.socket when there is no mtp-responser.socket

The mtp-responder.socket is special in the configfs environment.
If mtp-responder.socket is missing, gadget configuration will fail.
As a result, all usb operations do not work properly.
So in environments that mtp doesn't support, use dummy mtp.

Applied target : XU3, Artik headless, RPI4

Change-Id: I34bee7c1837ada478959407cd7c6500e219f28bc
CMakeLists.txt
hw/usb_gadget_common.c
mtp-responder-dummy/descs [new file with mode: 0644]
mtp-responder-dummy/mtp-responder-dummy.service [new file with mode: 0644]
mtp-responder-dummy/mtp-responder-dummy.socket [new file with mode: 0644]
mtp-responder-dummy/strs [new file with mode: 0644]
packaging/libdevice-node.spec