[PATCH RFC 1/2] dt-bindings: regmap: add common schema for no-sequential-read

[Richard Leitner <richard.leitner@linux.dev>]

Introduce a common regmap dt-binding schema with an optional boolean
property no-sequential-read to describe hardware integrations where
reading multiple consecutive registers in a single operation is not
reliable and registers must be read individually.

A typical case are imaging sensors used on vendor-provided camera
modules whose bus integration does not support reads that advance across
consecutive register addresses. In such cases, single-register reads
work, but bulk reads do not. This restriction is a property of the
concrete hardware integration, not of the chip itself. It therefore
cannot be identified from the device driver and duplicating firmware
parsing in each affected driver does not scale.

Signed-off-by: Richard Leitner <richard.leitner@linux.dev>
---
 .../devicetree/bindings/regmap/common.yaml         | 26 ++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/Documentation/devicetree/bindings/regmap/common.yaml b/Documentation/devicetree/bindings/regmap/common.yaml
new file mode 100644
index 0000000000000..1d713bc3217da
--- /dev/null
+++ b/Documentation/devicetree/bindings/regmap/common.yaml
@@ -0,0 +1,26 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/regmap/common.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Common register access constraints
+
+maintainers:
+  - TBD
+
+description:
+  Common properties describing register access constraints.
+
+properties:
+  no-sequential-read:
+    type: boolean
+    description:
+      Indicates that this device instance does not support sequential
+      register reads.
+
+      Reads may start at a given register address, but reading multiple
+      consecutive registers in a single operation is not reliable.
+      Software must instead read registers individually.
+
+additionalProperties: true

-- 
2.53.0