Add enterprise policy to turn off Bluetooth.

chrome/browser/permissions/permission_manager.cc

Index: chrome/browser/permissions/permission_manager.cc
diff --git a/chrome/browser/permissions/permission_manager.cc b/chrome/browser/permissions/permission_manager.cc
index da0aba43ebb2ef681aa6a2e3a6e998d8a4849419..b3e6d99d3a4ed2d595552b116533e3c753d7ff3e 100644
--- a/chrome/browser/permissions/permission_manager.cc
+++ b/chrome/browser/permissions/permission_manager.cc
@@ -84,6 +84,8 @@ ContentSettingsType PermissionTypeToContentSetting(PermissionType permission) {
       return CONTENT_SETTINGS_TYPE_MEDIASTREAM_MIC;
     case PermissionType::VIDEO_CAPTURE:
       return CONTENT_SETTINGS_TYPE_MEDIASTREAM_CAMERA;
+    case PermissionType::BLUETOOTH_GUARD:

[raymes, 2016/02/22 22:34:34]

I wonder if we should just call this BLUETOOTH? 

[Jeffrey Yasskin, 2016/02/22 22:52:17]

I picked BLUETOOTH_GUARD because it's not where the main BLUETOOTH data gets
stored; it just guards use of the overall API. That said, I'm fine using just
"BLUETOOTH" like
https://codereview.chromium.org/1427433017/diff/1/components/content_settings...
did. Let me know which you prefer.

And maybe in the long run we can have a single PermissionType that covers both
the guard and the main data storage, and then we won't have that ambiguity at
all until we call down to the ContentSettings layer.

+      return CONTENT_SETTINGS_TYPE_BLUETOOTH_GUARD;
     case PermissionType::NUM:
       // This will hit the NOTREACHED below.
       break;