| Message ID | 20231116180743.2763021-1-javierm@redhat.com |
|---|---|
| State | Changes Requested |
| Headers | show |
| Series | [1/3] dt-bindings: display: ssd1307fb: Change "solomon,page-offset" default value | expand |
| Context | Check | Description |
|---|---|---|
| robh/checkpatch | warning | total: 0 errors, 1 warnings, 8 lines checked |
| robh/patch-applied | success | |
| robh/dtbs-check | warning | build log |
| robh/dt-meta-schema | success |
On Thu, Nov 16, 2023 at 07:07:37PM +0100, Javier Martinez Canillas wrote: > This is used to specify the page start address offset of the display RAM. > > The value is used as offset when setting the page start address with the > SSD130X_SET_PAGE_RANGE command, and the driver currently sets its value to > 1 if the property is not present in the Device Tree. > > But the datasheet mentions that the value on reset for the page start is a > 0, so it makes more sense to also have 0 as the default value for the page > offset if the property is not present. > > In fact, using a default value of 1 leads to the display not working when > the fbdev is attached to the framebuffer console. > > Reported-by: Sahaj Sarup <sahaj.sarup@linaro.org> > Signed-off-by: Javier Martinez Canillas <javierm@redhat.com> > --- > > .../devicetree/bindings/display/solomon,ssd1307fb.yaml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml b/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml > index 3afbb52d1b7f..badd81459aaa 100644 > --- a/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml > +++ b/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml > @@ -35,7 +35,7 @@ properties: > > solomon,page-offset: > $ref: /schemas/types.yaml#/definitions/uint32 > - default: 1 > + default: 0 I think I saw it pointed out by Maxime elsewhere that this breaks the ABI. It would be nice if DT defaults matched the hardware's, but I don't really think it is worth breaking the ABI here. Expanding the property description to explain the impact of the particular values might help with incorrect usage. Thanks, Conor. > description: > Offset of pages (band of 8 pixels) that the screen is mapped to > > -- > 2.41.0 >
Conor Dooley <conor@kernel.org> writes: Hello Connor, > On Thu, Nov 16, 2023 at 07:07:37PM +0100, Javier Martinez Canillas wrote: >> This is used to specify the page start address offset of the display RAM. >> >> The value is used as offset when setting the page start address with the >> SSD130X_SET_PAGE_RANGE command, and the driver currently sets its value to >> 1 if the property is not present in the Device Tree. >> >> But the datasheet mentions that the value on reset for the page start is a >> 0, so it makes more sense to also have 0 as the default value for the page >> offset if the property is not present. >> >> In fact, using a default value of 1 leads to the display not working when >> the fbdev is attached to the framebuffer console. >> >> Reported-by: Sahaj Sarup <sahaj.sarup@linaro.org> >> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com> >> --- >> >> .../devicetree/bindings/display/solomon,ssd1307fb.yaml | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml b/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml >> index 3afbb52d1b7f..badd81459aaa 100644 >> --- a/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml >> +++ b/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml >> @@ -35,7 +35,7 @@ properties: >> >> solomon,page-offset: >> $ref: /schemas/types.yaml#/definitions/uint32 >> - default: 1 >> + default: 0 > > I think I saw it pointed out by Maxime elsewhere that this breaks the > ABI. It would be nice if DT defaults matched the hardware's, but I don't > really think it is worth breaking the ABI here. Expanding the property Yes, Maxime also agrees with you as you mentioned. It's fair to say that this may affect potential users even when I honestly think that's unlikely. I'll just discard these patches and point out to people reporting the same problem than Sahaj, that they need to add a "solomon,page-offset" property. > description to explain the impact of the particular values might help > with incorrect usage. > I'm unsure how much that would help to be honest but I might post a patch. > Thanks, > Conor. >
diff --git a/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml b/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml index 3afbb52d1b7f..badd81459aaa 100644 --- a/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml +++ b/Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml @@ -35,7 +35,7 @@ properties: solomon,page-offset: $ref: /schemas/types.yaml#/definitions/uint32 - default: 1 + default: 0 description: Offset of pages (band of 8 pixels) that the screen is mapped to
This is used to specify the page start address offset of the display RAM. The value is used as offset when setting the page start address with the SSD130X_SET_PAGE_RANGE command, and the driver currently sets its value to 1 if the property is not present in the Device Tree. But the datasheet mentions that the value on reset for the page start is a 0, so it makes more sense to also have 0 as the default value for the page offset if the property is not present. In fact, using a default value of 1 leads to the display not working when the fbdev is attached to the framebuffer console. Reported-by: Sahaj Sarup <sahaj.sarup@linaro.org> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com> --- .../devicetree/bindings/display/solomon,ssd1307fb.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)