summaryrefslogtreecommitdiff
path: root/Documentation/driver-api/media/camera-sensor.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/driver-api/media/camera-sensor.rst')
-rw-r--r--Documentation/driver-api/media/camera-sensor.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/driver-api/media/camera-sensor.rst b/Documentation/driver-api/media/camera-sensor.rst
index 93f4f2536c25..96cfbc261b6e 100644
--- a/Documentation/driver-api/media/camera-sensor.rst
+++ b/Documentation/driver-api/media/camera-sensor.rst
@@ -13,7 +13,7 @@ Handling clocks
Camera sensors have an internal clock tree including a PLL and a number of
divisors. The clock tree is generally configured by the driver based on a few
-input parameters that are specific to the hardware:: the external clock frequency
+input parameters that are specific to the hardware: the external clock frequency
and the link frequency. The two parameters generally are obtained from system
firmware. **No other frequencies should be used in any circumstances.**
@@ -123,7 +123,7 @@ Power management
Always use runtime PM to manage the power states of your device. Camera sensor
drivers are in no way special in this respect: they are responsible for
controlling the power state of the device they otherwise control as well. In
-general, the device must be powered on at least when its registers are being
+general, the device shall be powered on at least when its registers are being
accessed and when it is streaming.
Existing camera sensor drivers may rely on the old