RFC regmap: support firmware-described non-sequential register reads
Get series with b4
b4 am [email protected] change-id 20260722-regmap-single-read-a2e95070cd66Versions newest first
- v1 RFC Latest2 patches 17 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | dt-bindings: regmap: add common schema for no-sequential-readDocumentation/ | +26 | 17 replies | |
| 2/2 | regmap: implement no-sequential-read firmware propertydrivers/ | +13 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 0/2] regmap: support firmware-described non-sequential register reads
Hi all,
this series adds support for firmware/device-tree described constraints on sequential register reads.
The motivating use case are camera modules from Vision Components. These modules may integrate image sensors that normally support incrementing multi-register reads, while the MCU (which sits basically "between" the I2C host and the camera sensors) breaks them. In such cases, single-register reads work, but sequential/bulk register reads do not.
This limitation is therefore not a property of the sensor silicon itself, but of the hardware module/integration in which the device is used. As a result, it cannot be identified from the deivce driver and handling it in each affected device driver does not scale well.
To address this, the series introduces a common firmware property (no-sequential-read) describing hardware integrations where reading multiple consecutive registers in a single operation is not reliable. regmap then consumes that property and maps it to its existing use_single_read configuration. This keeps the hardware constraint described in firmware/device-tree while applying it in the layer that already owns the register read transfer policy.
The initial discussion that motivated this approach can be found here:
https://lore.kernel.org/lkml/[email protected]/
Feedback is especially welcome on the property naming, the placement of the common binding schema, and if regmap is the best place to implment this.
Thanks,
Richard
---
Richard Leitner (2):
dt-bindings: regmap: add common schema for no-sequential-read
regmap: implement no-sequential-read firmware property
.../devicetree/bindings/regmap/common.yaml | 26 ++++++++++++++++++++++ drivers/base/regmap/regmap.c | 14 +++++++++++- 2 files changed, 39 insertions(+), 1 deletion(-)
---
base-commit: 248951ddc14de84de3910f9b13f51491a8cd91df
change-id: 20260722-regmap-single-read-a2e95070cd66
Best regards,
Signature · 1 line
Richard Leitner <[email protected]>