On Sunday 22 June 2014 19:37:56 Noralf Trønnes wrote:
>
> I see two possibilities:
> * add a special marker value to separate the registers, as I do now
> * add a flag to indicate a register number. So far I've only seen 8 and
> 16-bit register number widths: register 20h could thus be written as
> 10000020, 1000020, 100020 or 10020
>
> Example (skipped state changes from previous example):
> <100B1 01 2C 2D
> 100B2 01 2C 2D
> 100B3 01 2C 2D 01 2C 2D
> 100B4 07 C0 A2 02 84
> 100C1 C5 C2 0A 00
> 100C3 8A 2A
> 100C4 8A EE
> 100C5 0E
> 10020
> 10036 C0
> 1003A 05
> 100E0 0f 1a 0f 18 2f 28 20 22 1f 1b 23 37 00 07 02 10
> 100E1 0f 1b 0f 17 33 2c 29 2e 30 30 39 3f 00 07 03 10>
>
> Is this a viable solution?
We normally use high-level descriptions of the timings that the driver
then converts into register-level settings. See
Documentation/devicetree/bindings/video/display-timing.txt and
other files in that directory for how existing drivers handle this.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
