Add enterprise policy to turn off Bluetooth.

chrome/browser/permissions/permission_manager.cc

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/permissions/permission_manager.h"
 
 #include <stddef.h>
 
 #include "base/callback.h"
 #include "build/build_config.h"
@@ skipping 66 matching lines @@
 #endif
     case PermissionType::DURABLE_STORAGE:
       return CONTENT_SETTINGS_TYPE_DURABLE_STORAGE;
     case PermissionType::MIDI:
       // This will hit the NOTREACHED below.
       break;
     case PermissionType::AUDIO_CAPTURE:
       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;
   }
 
   NOTREACHED() << "Unknown content setting for permission "
                << static_cast<int>(permission);
   return CONTENT_SETTINGS_TYPE_DEFAULT;
 }
 
@@ skipping 326 matching lines @@
     // Add the callback to |callbacks| which will be run after the loop to
     // prevent re-entrance issues.
     callbacks.push_back(
         base::Bind(subscription->callback,
                    ContentSettingToPermissionStatus(new_value)));
   }
 
   for (const auto& callback : callbacks)
     callback.Run();
 }