The CCS embedded data format has multiple aspects (packing, encoding and the rest, including register addresses and semantics). Explicitly allow non-compliant embedded data to use the two former to reduce redundant documentation. Signed-off-by: Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx> --- .../userspace-api/media/drivers/camera-sensor.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Documentation/userspace-api/media/drivers/camera-sensor.rst b/Documentation/userspace-api/media/drivers/camera-sensor.rst index 9f3b0da3ad0d..dc415b8f6c8e 100644 --- a/Documentation/userspace-api/media/drivers/camera-sensor.rst +++ b/Documentation/userspace-api/media/drivers/camera-sensor.rst @@ -123,3 +123,14 @@ In general, changing the embedded data format from the driver-configured values is not supported. The height of the metadata is device-specific and the width is that (or less of that) of the image width, as configured on the pixel data stream. + +CCS and non-CCS embedded data +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Embedded data which is fully compliant with CCS definitions uses ``CCS embedded +data format <MEDIA-BUS-FMT-CCS-EMBEDDED>`` media bus code (level +3). Device-specific embedded data compliant with either MIPI CCS embedded data +levels 1 or 2 only shall not use CCS embedded data mbus code, but may refer to +CCS embedded data documentation with the level of conformance specified and omit +documenting these aspects of the format. The rest of the device-specific +embedded data format is documented in the context of the data format itself. -- 2.39.2
