Remove unnecessary dpm policy check logic

dpm policy was already done during rfcomm connection.
no need to check dpm policy in socket writing

Change-Id: I5412d2b4c273a0627911cf52beeb0ded44587a87

diff --git a/bt-api/bt-rfcomm-client.c b/bt-api/bt-rfcomm-client.c
index cd72071..6df76c7 100644 (file)
--- a/bt-api/bt-rfcomm-client.c
+++ b/bt-api/bt-rfcomm-client.c
@@ -1334,14 +1334,6 @@ BT_EXPORT_API int bluetooth_rfcomm_write(int fd, const char *buf, int length)
 
        retv_if(length <= 0, BLUETOOTH_ERROR_INVALID_PARAM);
 
-#ifdef TIZEN_FEATURE_BT_DPM
-       if (_bt_check_dpm(BT_DPM_SPP, NULL) == BT_DPM_RESTRICTED ||
-               _bt_check_dpm(BT_DPM_HF_ONLY, NULL) == BT_DPM_RESTRICTED) {
-               BT_ERR("Not allow to write RFCOMM data");
-               return BLUETOOTH_ERROR_DEVICE_POLICY_RESTRICTION;
-       }
-#endif
-
        switch (privilege_token) {
        case 0:
                result = _bt_check_privilege(BT_BLUEZ_SERVICE, BT_RFCOMM_SOCKET_WRITE);