[sensors] Introduce Generic Sensor API interfaces

device/generic_sensor/sensor_provider_impl.cc

Index: device/generic_sensor/sensor_provider_impl.cc
diff --git a/device/generic_sensor/sensor_provider_impl.cc b/device/generic_sensor/sensor_provider_impl.cc
new file mode 100644
index 0000000000000000000000000000000000000000..1a2f79a82b726a972ff9370bdf7c003aa9a75eb5
--- /dev/null
+++ b/device/generic_sensor/sensor_provider_impl.cc
@@ -0,0 +1,71 @@
+// Copyright 2016 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 "device/generic_sensor/sensor_provider_impl.h"
+
+#include <utility>
+
+#include "device/generic_sensor/platform_sensor_provider.h"
+#include "device/generic_sensor/sensor_impl.h"
+
+namespace device {
+
+namespace {
+
+uint64_t GetBufferOffset(mojom::SensorType type) {
+  return (static_cast<uint64_t>(mojom::SensorType::LAST) -
+          static_cast<uint64_t>(type)) *
+         mojom::SensorReadBuffer::kReadBufferSize;
+}
+
+}  // namespace
+
+// static
+void SensorProviderImpl::Create(
+    mojo::InterfaceRequest<mojom::SensorProvider> request) {
+  PlatformSensorProvider* provider = PlatformSensorProvider::GetInstance();
+  if (provider)

[timvolodine, 2016/08/19 16:02:30]

so what happens if provider is null? maybe better to always return a non-null
provider that would fail to CreateSensor() in this case so that error callback
is invoked?

[Mikhail, 2016/08/19 19:10:02]

blink part will be notified on very early stage via mojo mechanisms
(connection_error_handler)

[timvolodine, 2016/08/22 18:42:46]

wouldn't that result in duplicate code though? empty provider implementation
would simply use the !sensor code path.. also easier to distinguish between
empty platform or something wrong with mojo connection, just saying.

[Mikhail, 2016/08/22 19:07:50]

mm.. why would it cause code duplication?
From API POV we do not need to distinguish, Sensor will switch to 'errored'
state in any of these cases.
My point here is to return/notify error as soon as we know that we cannot
proceed (no service available).

[timvolodine, 2016/08/22 19:42:25]

I guess it's a question of semantics, so up to you to decide.

(having something with potential null value usually results in more 'special'
cases though)

+    new SensorProviderImpl(std::move(request), provider);
+}
+
+SensorProviderImpl::SensorProviderImpl(
+    mojo::InterfaceRequest<mojom::SensorProvider> request,
+    PlatformSensorProvider* provider)
+    : binding_(this, std::move(request)), provider_(provider) {
+  DCHECK(provider_);
+}
+
+SensorProviderImpl::~SensorProviderImpl() {}
+
+void SensorProviderImpl::GetSensor(mojom::SensorType type,
+                                   mojom::SensorRequest sensor_request,
+                                   const GetSensorCallback& callback) {
+  auto cloned_handle = provider_->CloneSharedBufferHandle();
+  if (!cloned_handle.is_valid()) {
+    callback.Run(nullptr, nullptr);
+    return;
+  }
+
+  scoped_refptr<PlatformSensor> sensor = provider_->GetSensor(type);
+  if (!sensor) {
+    sensor = provider_->CreateSensor(
+        type, mojom::SensorReadBuffer::kReadBufferSize, GetBufferOffset(type));
+  }
+
+  if (!sensor) {
+    callback.Run(nullptr, nullptr);
+    return;
+  }
+
+  auto sensor_impl = new SensorImpl(std::move(sensor_request), sensor);
+
+  auto sensor_read_buffer = mojom::SensorReadBuffer::New();
+  sensor_read_buffer->memory = std::move(cloned_handle);
+  sensor_read_buffer->offset = GetBufferOffset(type);
+  sensor_read_buffer->mode = sensor->GetReportingMode();
+
+  callback.Run(std::move(sensor_read_buffer), sensor_impl->GetClient());
+}
+
+}  // namespace device