Add |notify_client_on_reading_change| flag to sensor configuration

device/generic_sensor/sensor_impl.h

Index: device/generic_sensor/sensor_impl.h
diff --git a/device/generic_sensor/sensor_impl.h b/device/generic_sensor/sensor_impl.h
index 4a6ecc95e0faaff7590e15aba65c74ad9b26a0ea..9b16a4eebced634f0c69408ba6df4fcf6a543949 100644
--- a/device/generic_sensor/sensor_impl.h
+++ b/device/generic_sensor/sensor_impl.h
@@ -40,6 +40,10 @@ class SensorImpl final : public mojom::Sensor, public PlatformSensor::Client {
   scoped_refptr<PlatformSensor> sensor_;
   mojom::SensorClientPtr client_;
   bool suspended_;
+  // The number of configurations that have |suppress_on_change_events_|
+  // flag set to false. If there is at least one configuration that sets this
+  // flag to false, SensorClient::SensorReadingChanged() is called.
+  int not_suppress_on_change_events_count_;

[Reilly Grant (use Gerrit), 2017/06/09 22:10:02]

This is getting really weird. Since we only ever set one configuration on a
sensor (and should enforce that in a future patch) can we invert this so that if
any configuration suppresses notifications then we don't send them?

[juncai, 2017/06/09 22:52:32]

Done.

 
   DISALLOW_COPY_AND_ASSIGN(SensorImpl);
 };