drm/solomon: Add support for the SSD133x controller family
Subsystems (4)
Javier Martinez Canillas
maintainerv3 cover drm/solomon: Add support for the SSD133x controller family
Hello,
This patch-set adds support for the family of SSD133x Solomon controllers, such as the SSD1331. These are used for RGB Dot Matrix OLED/PLED panels.
This is a v3 that addresses issues pointed out in v2:
https://lore.kernel.org/dri-devel/[email protected]/
The patches were tested on a Waveshare SSD1331 display using glmark2-drm, fbcon, fbtests and the retroarch emulator. The binding schema were tested using the make W=1 dt_binding_check target.
Patch #1 and #2 are fixes for the DT binding schema of the existing SSD130x and SSD132x families.
Patch #3 adds a DT binding schema for the SSD133x controllers and patch #4 extends the ssd130x DRM driver to support the SSD133x controller family.
Best regards,
Javier
Changes in v3:
- Move solomon,ssd-common.yaml ref before the properties section and width/height constraints after the other properties (Conor Dooley).
Changes in v2:
- Unconditionally set the width and height constraints (Conor Dooley).
- Fix indentation in the DTS examples (Krzysztof Kozlowski).
Javier Martinez Canillas (4):
dt-bindings: display: ssd1307fb: Add vendor prefix to width and height
dt-bindings: display: ssd132x: Add vendor prefix to width and height
dt-bindings: display: Add SSD133x OLED controllers drm/ssd130x: Add support for the SSD133x OLED controller family
.../bindings/display/solomon,ssd1307fb.yaml | 20 +- .../bindings/display/solomon,ssd132x.yaml | 12 +- .../bindings/display/solomon,ssd133x.yaml | 57 +++ drivers/gpu/drm/solomon/ssd130x-i2c.c | 5 + drivers/gpu/drm/solomon/ssd130x-spi.c | 7 + drivers/gpu/drm/solomon/ssd130x.c | 370 ++++++++++++++++++ drivers/gpu/drm/solomon/ssd130x.h | 5 +- 7 files changed, 459 insertions(+), 17 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/solomon,ssd133x.yaml
Signature · 1 line
2.43.0
Javier Martinez Canillas
maintainerPATCH v3 1/4 dt-bindings: display: ssd1307fb: Add vendor prefix to width and height
The commit 591825fba8a2 ("dt-bindings: display: ssd1307fb: Remove default width and height values") used the wrong properties for width and height, instead of the correct "solomon,width" and "solomon,height" properties.
Fix this by adding the vendor prefix to the width and height properties.
---
(no changes since v1)
.../bindings/display/solomon,ssd1307fb.yaml | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-)
Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml +10 -10
@@ -131,9 +131,9 @@ allOf: const: sinowealth,sh1106 then: properties: - width: + solomon,width: default: 132 - height: + solomon,height: default: 64 solomon,dclk-div: default: 1
@@ -149,9 +149,9 @@ allOf: - solomon,ssd1305 then: properties: - width: + solomon,width: default: 132 - height: + solomon,height: default: 64 solomon,dclk-div: default: 1
@@ -167,9 +167,9 @@ allOf: - solomon,ssd1306 then: properties: - width: + solomon,width: default: 128 - height: + solomon,height: default: 64 solomon,dclk-div: default: 1
@@ -185,9 +185,9 @@ allOf: - solomon,ssd1307 then: properties: - width: + solomon,width: default: 128 - height: + solomon,height: default: 39 solomon,dclk-div: default: 2
@@ -205,9 +205,9 @@ allOf: - solomon,ssd1309 then: properties: - width: + solomon,width: default: 128 - height: + solomon,height: default: 64 solomon,dclk-div: default: 1
Signature · 1 line
2.43.0
Re: [PATCH v3 1/4] dt-bindings: display: ssd1307fb: Add vendor prefix to width and height
Quoted 10 lines · Javier Martinez Canillas
The commit
591825fba8a2("dt-bindings: display: ssd1307fb: Remove default width and height values") used the wrong properties for width and height, instead of the correct "solomon,width" and "solomon,height" properties.Fix this by adding the vendor prefix to the width and height properties.
Fixes 591825fba8a2 ("dt-bindings: display: ssd1307fb: Remove default width and height values")Reported-by Conor Dooley <[email protected]>Signed-off-by Javier Martinez Canillas <[email protected]>
Quoted 7 lines
---
(no changes since v1)
.../bindings/display/solomon,ssd1307fb.yaml | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-)
Javier Martinez Canillas
maintainerPATCH v3 2/4 dt-bindings: display: ssd132x: Add vendor prefix to width and height
In reply to Javier Martinez CanillasCommit 2d23e7d6bacb ("dt-bindings: display: Add SSD132x OLED controllers") used the wrong properties for width and height, instead of the correct "solomon,width" and "solomon,height" properties.
Fix this by adding the vendor prefix to the width and height properties.
---
(no changes since v1)
.../devicetree/bindings/display/solomon,ssd132x.yaml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
Documentation/devicetree/bindings/display/solomon,ssd132x.yaml +6 -6
@@ -30,9 +30,9 @@ allOf: const: solomon,ssd1322 then: properties: - width: + solomon,width: default: 480 - height: + solomon,height: default: 128 - if:
@@ -42,9 +42,9 @@ allOf: const: solomon,ssd1325 then: properties: - width: + solomon,width: default: 128 - height: + solomon,height: default: 80 - if:
@@ -54,9 +54,9 @@ allOf: const: solomon,ssd1327 then: properties: - width: + solomon,width: default: 128 - height: + solomon,height: default: 128 unevaluatedProperties: false
Signature · 1 line
2.43.0
Re: [PATCH v3 2/4] dt-bindings: display: ssd132x: Add vendor prefix to width and height
Quoted 10 lines · Javier Martinez Canillas
Commit
2d23e7d6bacb("dt-bindings: display: Add SSD132x OLED controllers") used the wrong properties for width and height, instead of the correct "solomon,width" and "solomon,height" properties.Fix this by adding the vendor prefix to the width and height properties.
Fixes 2d23e7d6bacb ("dt-bindings: display: Add SSD132x OLED controllers")Reported-by Conor Dooley <[email protected]>Signed-off-by Javier Martinez Canillas <[email protected]>
Quoted 7 lines
---
(no changes since v1)
.../devicetree/bindings/display/solomon,ssd132x.yaml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
Javier Martinez Canillas
maintainerPATCH v3 3/4 dt-bindings: display: Add SSD133x OLED controllers
In reply to Javier Martinez CanillasAdd a Device Tree binding schema for the OLED panels based on the Solomon SSD133x family of controllers.
---
Changes in v3:
- Move solomon,ssd-common.yaml ref before the properties section and width/height constraints after the other properties (Conor Dooley).
Changes in v2:
- Unconditionally set the width and height constraints (Conor Dooley).
- Fix indentation in the DTS examples (Krzysztof Kozlowski).
.../bindings/display/solomon,ssd133x.yaml | 57 +++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/solomon,ssd133x.yaml
Documentation/devicetree/bindings/display/solomon,ssd133x.yaml new file +57 -0
@@ -0,0 +1,57 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/solomon,ssd133x.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Solomon SSD133x OLED Display Controllers + +maintainers: + - Javier Martinez Canillas <[email protected]> + +allOf: + - $ref: solomon,ssd-common.yaml# + +properties: + compatible: + enum: + - solomon,ssd1331 + + solomon,width: + default: 96 + + solomon,height: + default: 64 + +required: + - compatible + - reg + +unevaluatedProperties: false + +examples: + - | + i2c { + #address-cells = <1>; + #size-cells = <0>; + + oled@3c { + compatible = "solomon,ssd1331"; + reg = <0x3c>; + reset-gpios = <&gpio2 7>; + }; + + }; + - | + spi { + #address-cells = <1>; + #size-cells = <0>; + + oled@0 { + compatible = "solomon,ssd1331"; + reg = <0x0>; + reset-gpios = <&gpio2 7>; + dc-gpios = <&gpio2 8>; + spi-max-frequency = <10000000>; + }; + };
Signature · 1 line
2.43.0
Re: [PATCH v3 3/4] dt-bindings: display: Add SSD133x OLED controllers
Quoted 10 lines · Javier Martinez Canillas
Add a Device Tree binding schema for the OLED panels based on the Solomon SSD133x family of controllers.
Signed-off-by Javier Martinez Canillas <[email protected]>---
Changes in v3:
- Move solomon,ssd-common.yaml ref before the properties section and width/height constraints after the other properties (Conor Dooley).
Quoted 8 lines
Changes in v2:
- Unconditionally set the width and height constraints (Conor Dooley).
- Fix indentation in the DTS examples (Krzysztof Kozlowski)..../bindings/display/solomon,ssd133x.yaml | 57 +++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/solomon,ssd133x.yaml
Javier Martinez Canillas
maintainerPATCH v3 4/4 drm/ssd130x: Add support for the SSD133x OLED controller family
In reply to Javier Martinez CanillasThe Solomon SSD133x controllers (such as the SSD1331) are used by RGB dot matrix OLED panels, add a modesetting pipeline to support the chip family.
The SSD133x controllers support 256 (8-bit) and 65k (16-bit) color depths but only the former is implemented for now. This is because the 256 color depth format matches a fourcc code already present in DRM (RGB8), but the 65k pixel format does not match the existing RG16 fourcc code format.
Instead of a R:G:B 5:6:5, the controller expects the 16-bit pixels to be R:G:B 6:5:6, and so a new fourcc needs to be added to support this format.
---
(no changes since v1)
drivers/gpu/drm/solomon/ssd130x-i2c.c | 5 + drivers/gpu/drm/solomon/ssd130x-spi.c | 7 + drivers/gpu/drm/solomon/ssd130x.c | 370 ++++++++++++++++++++++++++ drivers/gpu/drm/solomon/ssd130x.h | 5 +- 4 files changed, 386 insertions(+), 1 deletion(-)
drivers/gpu/drm/solomon/ssd130x-i2c.c +5 -0
@@ -105,6 +105,11 @@ static const struct of_device_id ssd130x_of_match[] = { .compatible = "solomon,ssd1327", .data = &ssd130x_variants[SSD1327_ID], }, +/* ssd133x family */ + { + .compatible = "solomon,ssd1331", + .data = &ssd130x_variants[SSD1331_ID], + }, {/* sentinel */ } };MODULE_DEVICE_TABLE (of, ssd130x_of_match);
drivers/gpu/drm/solomon/ssd130x-spi.c +7 -0
@@ -142,6 +142,11 @@ static const struct of_device_id ssd130x_of_match[] = { .compatible = "solomon,ssd1327", .data = &ssd130x_variants[SSD1327_ID], }, +/* ssd133x family */ + { + .compatible = "solomon,ssd1331", + .data = &ssd130x_variants[SSD1331_ID], + }, {/* sentinel */ } };MODULE_DEVICE_TABLE (of, ssd130x_of_match);
@@ -166,6 +171,8 @@ static const struct spi_device_id ssd130x_spi_table[] = { { "ssd1322", SSD1322_ID }, { "ssd1325", SSD1325_ID }, { "ssd1327", SSD1327_ID }, +/* ssd133x family */ + { "ssd1331", SSD1331_ID }, { /* sentinel */ } };MODULE_DEVICE_TABLE (spi, ssd130x_spi_table);
drivers/gpu/drm/solomon/ssd130x.c +370 -0
454 lines not on this page · raw message
drivers/gpu/drm/solomon/ssd130x.h +4 -1
@@ -25,7 +25,8 @@enum ssd130x_family_ids {SSD130X_FAMILY , -SSD132X_FAMILY +SSD132X_FAMILY , +SSD133X_FAMILY };enum ssd130x_variants {
@@ -39,6 +40,8 @@ enum ssd130x_variants {SSD1322_ID ,SSD1325_ID ,SSD1327_ID , +/* ssd133x family */ +SSD1331_ID , NR_SSD130X_VARIANTS };
Signature · 1 line
2.43.0
Re: [PATCH v3 4/4] drm/ssd130x: Add support for the SSD133x OLED controller family
Quoted 10 lines · Javier Martinez Canillas
The Solomon SSD133x controllers (such as the SSD1331) are used by RGB dot matrix OLED panels, add a modesetting pipeline to support the chip family.
The SSD133x controllers support 256 (8-bit) and 65k (16-bit) color depths but only the former is implemented for now. This is because the 256 color depth format matches a fourcc code already present in DRM (RGB8), but the 65k pixel format does not match the existing RG16 fourcc code format.
Instead of a R:G:B 5:6:5, the controller expects the 16-bit pixels to be R:G:B 6:5:6, and so a new fourcc needs to be added to support this format.
small typo here, R:G:B 6:5:6 => that's 17 bits
other than that, it looks good to me, feel free to add:
Quoted 548 lines
Signed-off-by Javier Martinez Canillas <[email protected]>---
(no changes since v1)
drivers/gpu/drm/solomon/ssd130x-i2c.c | 5 + drivers/gpu/drm/solomon/ssd130x-spi.c | 7 + drivers/gpu/drm/solomon/ssd130x.c | 370 ++++++++++++++++++++++++++ drivers/gpu/drm/solomon/ssd130x.h | 5 +- 4 files changed, 386 insertions(+), 1 deletion(-)drivers/gpu/drm/solomon/ssd130x-i2c.c +5
-0@@ -105,6 +105,11 @@ static const struct of_device_id ssd130x_of_match[] = { .compatible = "solomon,ssd1327", .data = &ssd130x_variants[SSD1327_ID], }, +/* ssd133x family */ + { + .compatible = "solomon,ssd1331", + .data = &ssd130x_variants[SSD1331_ID], + }, {/* sentinel */ } };MODULE_DEVICE_TABLE (of, ssd130x_of_match);drivers/gpu/drm/solomon/ssd130x-spi.c +7
-0@@ -142,6 +142,11 @@ static const struct of_device_id ssd130x_of_match[] = { .compatible = "solomon,ssd1327", .data = &ssd130x_variants[SSD1327_ID], }, +/* ssd133x family */ + { + .compatible = "solomon,ssd1331", + .data = &ssd130x_variants[SSD1331_ID], + }, {/* sentinel */ } };MODULE_DEVICE_TABLE (of, ssd130x_of_match);@@ -166,6 +171,8 @@ static const struct spi_device_id ssd130x_spi_table[] = { { "ssd1322", SSD1322_ID }, { "ssd1325", SSD1325_ID }, { "ssd1327", SSD1327_ID }, +/* ssd133x family */ + { "ssd1331", SSD1331_ID }, { /* sentinel */ } };MODULE_DEVICE_TABLE (spi, ssd130x_spi_table);drivers/gpu/drm/solomon/ssd130x.c +370
-0@@ -119,6 +119,26 @@#define SSD130X_SET_VCOMH_VOLTAGE 0xbe#define SSD132X_SET_FUNCTION_SELECT_B 0xd5 +/* ssd133x commands */ +#define SSD133X_SET_COL_RANGE 0x15 +#define SSD133X_SET_ROW_RANGE 0x75 +#define SSD133X_CONTRAST_A 0x81 +#define SSD133X_CONTRAST_B 0x82 +#define SSD133X_CONTRAST_C 0x83 +#define SSD133X_SET_MASTER_CURRENT 0x87 +#define SSD132X_SET_PRECHARGE_A 0x8a +#define SSD132X_SET_PRECHARGE_B 0x8b +#define SSD132X_SET_PRECHARGE_C 0x8c +#define SSD133X_SET_DISPLAY_START 0xa1 +#define SSD133X_SET_DISPLAY_OFFSET 0xa2 +#define SSD133X_SET_DISPLAY_NORMAL 0xa4 +#define SSD133X_SET_MASTER_CONFIG 0xad +#define SSD133X_POWER_SAVE_MODE 0xb0 +#define SSD133X_PHASES_PERIOD 0xb1 +#define SSD133X_SET_CLOCK_FREQ 0xb3 +#define SSD133X_SET_PRECHARGE_VOLTAGE 0xbb +#define SSD133X_SET_VCOMH_VOLTAGE 0xbe +#define MAX_CONTRAST 255const struct ssd130x_deviceinfo ssd130x_variants[] = {@@ -180,6 +200,12 @@ const struct ssd130x_deviceinfo ssd130x_variants[] = { .default_width = 128, .default_height = 128, .family_id = SSD132X_FAMILY, + }, + /* ssd133x family */ + [SSD1331_ID] = { + .default_width = 96, + .default_height = 64, + .family_id = SSD133X_FAMILY, } };EXPORT_SYMBOL_NS_GPL (ssd130x_variants,DRM_SSD130X );@@ -589,6 +615,117 @@ static int ssd132x_init(struct ssd130x_device *ssd130x)return 0 ; } +static int ssd133x_init (struct ssd130x_device *ssd130x) +{ +int ret; + +/* Set color A contrast */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_CONTRAST_A ,0x91 ); +if (ret <0 ) +return ret; + +/* Set color B contrast */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_CONTRAST_B ,0x50 ); +if (ret <0 ) +return ret; + +/* Set color C contrast */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_CONTRAST_C ,0x7d ); +if (ret <0 ) +return ret; + +/* Set master current */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_SET_MASTER_CURRENT ,0x06 ); +if (ret <0 ) +return ret; + +/* Set column start and end */ + ret =ssd130x_write_cmd (ssd130x,3 ,SSD133X_SET_COL_RANGE ,0x00 , ssd130x->width -1 ); +if (ret <0 ) +return ret; + +/* Set row start and end */ + ret =ssd130x_write_cmd (ssd130x,3 ,SSD133X_SET_ROW_RANGE ,0x00 , ssd130x->height -1 ); +if (ret <0 ) +return ret; + +/* +* Horizontal Address Increment +* Normal order SA,SB,SC (e.g. RGB) +* COM Split Odd Even +* 256 color format +*/ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD13XX_SET_SEG_REMAP ,0x20 ); +if (ret <0 ) +return ret; + +/* Set display start and offset */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_SET_DISPLAY_START ,0x00 ); +if (ret <0 ) +return ret; + + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_SET_DISPLAY_OFFSET ,0x00 ); +if (ret <0 ) +return ret; + +/* Set display mode normal */ + ret =ssd130x_write_cmd (ssd130x,1 ,SSD133X_SET_DISPLAY_NORMAL ); +if (ret <0 ) +return ret; + +/* Set multiplex ratio value */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD13XX_SET_MULTIPLEX_RATIO , ssd130x->height -1 ); +if (ret <0 ) +return ret; + +/* Set master configuration */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_SET_MASTER_CONFIG ,0x8e ); +if (ret <0 ) +return ret; + +/* Set power mode */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_POWER_SAVE_MODE ,0x0b ); +if (ret <0 ) +return ret; + +/* Set Phase 1 and 2 period */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_PHASES_PERIOD ,0x31 ); +if (ret <0 ) +return ret; + +/* Set clock divider */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_SET_CLOCK_FREQ ,0xf0 ); +if (ret <0 ) +return ret; + +/* Set pre-charge A */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD132X_SET_PRECHARGE_A ,0x64 ); +if (ret <0 ) +return ret; + +/* Set pre-charge B */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD132X_SET_PRECHARGE_B ,0x78 ); +if (ret <0 ) +return ret; + +/* Set pre-charge C */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD132X_SET_PRECHARGE_C ,0x64 ); +if (ret <0 ) +return ret; + +/* Set pre-charge level */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_SET_PRECHARGE_VOLTAGE ,0x3a ); +if (ret <0 ) +return ret; + +/* Set VCOMH voltage */ + ret =ssd130x_write_cmd (ssd130x,2 ,SSD133X_SET_VCOMH_VOLTAGE ,0x3e ); +if (ret <0 ) +return ret; + +return 0 ; +} +static int ssd130x_update_rect (struct ssd130x_device *ssd130x,struct drm_rect *rect,u8 *buf,u8 *data_array)@@ -753,6 +890,47 @@ static int ssd132x_update_rect(struct ssd130x_device *ssd130x,return ret; } +static int ssd133x_update_rect (struct ssd130x_device *ssd130x, +struct drm_rect *rect,u8 *data_array, +unsigned int pitch) +{ +unsigned int x = rect->x1; +unsigned int y = rect->y1; +unsigned int columns =drm_rect_width (rect); +unsigned int rows =drm_rect_height (rect); +int ret; + +/* +* The screen is divided in Segment and Common outputs, where +* COM0 to COM[N - 1] are the rows and SEG0 to SEG[M - 1] are +* the columns. +* +* Each Segment has a 8-bit pixel and each Common output has a +* row of pixels. When using the (default) horizontal address +* increment mode, each byte of data sent to the controller has +* a Segment (e.g: SEG0). +* +* When using the 256 color depth format, each pixel contains 3 +* sub-pixels for color A, B and C. These have 3 bit, 3 bit and +* 2 bits respectively. +*/ + +/* Set column start and end */ + ret =ssd130x_write_cmd (ssd130x,3 ,SSD133X_SET_COL_RANGE , x, columns -1 ); +if (ret <0 ) +return ret; + +/* Set row start and end */ + ret =ssd130x_write_cmd (ssd130x,3 ,SSD133X_SET_ROW_RANGE , y, rows -1 ); +if (ret <0 ) +return ret; + +/* Write out update in one go since horizontal addressing mode is used */ + ret =ssd130x_write_data (ssd130x, data_array, pitch * rows); + +return ret; +} +static void ssd130x_clear_screen (struct ssd130x_device *ssd130x,u8 *data_array) {unsigned int pages =DIV_ROUND_UP (ssd130x->height,SSD130X_PAGE_HEIGHT );@@ -805,6 +983,22 @@ static void ssd132x_clear_screen(struct ssd130x_device *ssd130x, u8 *data_array)ssd130x_write_data (ssd130x, data_array, columns * height); } +static void ssd133x_clear_screen (struct ssd130x_device *ssd130x,u8 *data_array) +{ +const struct drm_format_info *fi =drm_format_info (DRM_FORMAT_RGB332 ); +unsigned int pitch; + +if (!fi) +return ; + + pitch =drm_format_info_min_pitch (fi,0 , ssd130x->width); + +memset (data_array,0 , pitch * ssd130x->height); + +/* Write out update in one go since horizontal addressing mode is used */ +ssd130x_write_data (ssd130x, data_array, pitch * ssd130x->height); +} + static int ssd130x_fb_blit_rect(struct drm_framebuffer *fb, const struct iosys_map *vmap, struct drm_rect *rect,@@ -866,6 +1060,36 @@ static int ssd132x_fb_blit_rect(struct drm_framebuffer *fb,return ret; } +static int ssd133x_fb_blit_rect (struct drm_framebuffer *fb, +const struct iosys_map *vmap, +struct drm_rect *rect,u8 *data_array, +struct drm_format_conv_state *fmtcnv_state) +{ +struct ssd130x_device *ssd130x =drm_to_ssd130x (fb->dev); +const struct drm_format_info *fi =drm_format_info (DRM_FORMAT_RGB332 ); +unsigned int dst_pitch; +struct iosys_map dst; +int ret =0 ; + +if (!fi) +return -EINVAL ; + + dst_pitch =drm_format_info_min_pitch (fi,0 ,drm_rect_width (rect)); + + ret =drm_gem_fb_begin_cpu_access (fb,DMA_FROM_DEVICE ); +if (ret) +return ret; + +iosys_map_set_vaddr (&dst, data_array); +drm_fb_xrgb8888_to_rgb332 (&dst, &dst_pitch, vmap, fb, rect, fmtcnv_state); + +drm_gem_fb_end_cpu_access (fb,DMA_FROM_DEVICE ); + +ssd133x_update_rect (ssd130x, rect, data_array, dst_pitch); + +return ret; +} +static int ssd130x_primary_plane_atomic_check (struct drm_plane *plane,struct drm_atomic_state *state) {@@ -964,6 +1188,29 @@ static int ssd132x_primary_plane_atomic_check(struct drm_plane *plane,return 0 ; } +static int ssd133x_primary_plane_atomic_check (struct drm_plane *plane, +struct drm_atomic_state *state) +{ +struct drm_plane_state *plane_state =drm_atomic_get_new_plane_state (state, plane); +struct drm_crtc *crtc = plane_state->crtc; +struct drm_crtc_state *crtc_state =NULL ; +int ret; + +if (crtc) + crtc_state =drm_atomic_get_new_crtc_state (state, crtc); + + ret =drm_atomic_helper_check_plane_state (plane_state, crtc_state, +DRM_PLANE_NO_SCALING , +DRM_PLANE_NO_SCALING , + false, false); +if (ret) +return ret; +else if (!plane_state->visible) +return 0 ; + +return 0 ; +} +static void ssd130x_primary_plane_atomic_update (struct drm_plane *plane,struct drm_atomic_state *state) {@@ -1034,6 +1281,39 @@ static void ssd132x_primary_plane_atomic_update(struct drm_plane *plane,drm_dev_exit (idx); } +static void ssd133x_primary_plane_atomic_update (struct drm_plane *plane, +struct drm_atomic_state *state) +{ +struct drm_plane_state *plane_state =drm_atomic_get_new_plane_state (state, plane); +struct drm_plane_state *old_plane_state =drm_atomic_get_old_plane_state (state, plane); +struct drm_shadow_plane_state *shadow_plane_state =to_drm_shadow_plane_state (plane_state); +struct drm_crtc_state *crtc_state =drm_atomic_get_new_crtc_state (state, plane_state->crtc); +struct ssd130x_crtc_state *ssd130x_crtc_state =to_ssd130x_crtc_state (crtc_state); +struct drm_framebuffer *fb = plane_state->fb; +struct drm_atomic_helper_damage_iter iter; +struct drm_device *drm = plane->dev; +struct drm_rect dst_clip; +struct drm_rect damage; +int idx; + +if (!drm_dev_enter (drm, &idx)) +return ; + +drm_atomic_helper_damage_iter_init (&iter, old_plane_state, plane_state); +drm_atomic_for_each_plane_damage (&iter, &damage) { + dst_clip = plane_state->dst; + +if (!drm_rect_intersect (&dst_clip, &damage)) +continue ; + +ssd133x_fb_blit_rect (fb, &shadow_plane_state->data[0 ], &dst_clip, + ssd130x_crtc_state->data_array, + &shadow_plane_state->fmtcnv_state); + } + +drm_dev_exit (idx); +} +static void ssd130x_primary_plane_atomic_disable (struct drm_plane *plane,struct drm_atomic_state *state) {@@ -1082,6 +1362,30 @@ static void ssd132x_primary_plane_atomic_disable(struct drm_plane *plane,drm_dev_exit (idx); } +static void ssd133x_primary_plane_atomic_disable (struct drm_plane *plane, +struct drm_atomic_state *state) +{ +struct drm_device *drm = plane->dev; +struct ssd130x_device *ssd130x =drm_to_ssd130x (drm); +struct drm_plane_state *plane_state =drm_atomic_get_new_plane_state (state, plane); +struct drm_crtc_state *crtc_state; +struct ssd130x_crtc_state *ssd130x_crtc_state; +int idx; + +if (!plane_state->crtc) +return ; + + crtc_state =drm_atomic_get_new_crtc_state (state, plane_state->crtc); + ssd130x_crtc_state =to_ssd130x_crtc_state (crtc_state); + +if (!drm_dev_enter (drm, &idx)) +return ; + +ssd133x_clear_screen (ssd130x, ssd130x_crtc_state->data_array); + +drm_dev_exit (idx); +} +/* Called during init to allocate the plane's atomic state. */ static void ssd130x_primary_plane_reset (struct drm_plane *plane) {@@ -1144,6 +1448,12 @@ static const struct drm_plane_helper_funcs ssd130x_primary_plane_helper_funcs[] .atomic_check = ssd132x_primary_plane_atomic_check, .atomic_update = ssd132x_primary_plane_atomic_update, .atomic_disable = ssd132x_primary_plane_atomic_disable, + }, + [SSD133X_FAMILY] = { + DRM_GEM_SHADOW_PLANE_HELPER_FUNCS, + .atomic_check = ssd133x_primary_plane_atomic_check, + .atomic_update = ssd133x_primary_plane_atomic_update, + .atomic_disable = ssd133x_primary_plane_atomic_disable, } };@@ -1214,6 +1524,33 @@ static int ssd132x_crtc_atomic_check(struct drm_crtc *crtc,return 0 ; } +static int ssd133x_crtc_atomic_check (struct drm_crtc *crtc, +struct drm_atomic_state *state) +{ +struct drm_device *drm = crtc->dev; +struct ssd130x_device *ssd130x =drm_to_ssd130x (drm); +struct drm_crtc_state *crtc_state =drm_atomic_get_new_crtc_state (state, crtc); +struct ssd130x_crtc_state *ssd130x_state =to_ssd130x_crtc_state (crtc_state); +const struct drm_format_info *fi =drm_format_info (DRM_FORMAT_RGB332 ); +unsigned int pitch; +int ret; + +if (!fi) +return -EINVAL ; + + ret =drm_crtc_helper_atomic_check (crtc, state); +if (ret) +return ret; + + pitch =drm_format_info_min_pitch (fi,0 , ssd130x->width); + + ssd130x_state->data_array =kmalloc (pitch * ssd130x->height,GFP_KERNEL ); +if (!ssd130x_state->data_array) +return -ENOMEM ; + +return 0 ; +} +/* Called during init to allocate the CRTC's atomic state. */ static void ssd130x_crtc_reset (struct drm_crtc *crtc) {@@ -1275,6 +1612,10 @@ static const struct drm_crtc_helper_funcs ssd130x_crtc_helper_funcs[] = { .mode_valid = ssd130x_crtc_mode_valid, .atomic_check = ssd132x_crtc_atomic_check, }, + [SSD133X_FAMILY] = { + .mode_valid = ssd130x_crtc_mode_valid, + .atomic_check = ssd133x_crtc_atomic_check, + }, }; static const struct drm_crtc_funcs ssd130x_crtc_funcs = {@@ -1337,6 +1678,31 @@ static void ssd132x_encoder_atomic_enable(struct drm_encoder *encoder,ssd130x_power_off (ssd130x); } +static void ssd133x_encoder_atomic_enable (struct drm_encoder *encoder, +struct drm_atomic_state *state) +{ +struct drm_device *drm = encoder->dev; +struct ssd130x_device *ssd130x =drm_to_ssd130x (drm); +int ret; + + ret =ssd130x_power_on (ssd130x); +if (ret) +return ; + + ret =ssd133x_init (ssd130x); +if (ret) + goto power_off; + +ssd130x_write_cmd (ssd130x,1 ,SSD13XX_DISPLAY_ON ); + +backlight_enable (ssd130x->bl_dev); + +return ; + +power_off: +ssd130x_power_off (ssd130x); +} +static void ssd130x_encoder_atomic_disable (struct drm_encoder *encoder,struct drm_atomic_state *state) {@@ -1358,6 +1724,10 @@ static const struct drm_encoder_helper_funcs ssd130x_encoder_helper_funcs[] = { [SSD132X_FAMILY ] = { .atomic_enable = ssd132x_encoder_atomic_enable, .atomic_disable = ssd130x_encoder_atomic_disable, + }, + [SSD133X_FAMILY ] = { + .atomic_enable = ssd133x_encoder_atomic_enable, + .atomic_disable = ssd130x_encoder_atomic_disable, } };drivers/gpu/drm/solomon/ssd130x.h +4
-1@@ -25,7 +25,8 @@enum ssd130x_family_ids {SSD130X_FAMILY , -SSD132X_FAMILY +SSD132X_FAMILY , +SSD133X_FAMILY };enum ssd130x_variants {@@ -39,6 +40,8 @@ enum ssd130x_variants {SSD1322_ID ,SSD1325_ID ,SSD1327_ID , +/* ssd133x family */ +SSD1331_ID , NR_SSD130X_VARIANTS };
Javier Martinez Canillas
maintainerRe: [PATCH v3 4/4] drm/ssd130x: Add support for the SSD133x OLED controller family
Jocelyn Falempe <[email protected]> writes:
Hello Jocelyn,
Thanks a lot for your review!
Quoted 9 lines · Javier Martinez Canillas
Quoted 8 lines
The Solomon SSD133x controllers (such as the SSD1331) are used by RGB dot matrix OLED panels, add a modesetting pipeline to support the chip family.
The SSD133x controllers support 256 (8-bit) and 65k (16-bit) color depths but only the former is implemented for now. This is because the 256 color depth format matches a fourcc code already present in DRM (RGB8), but the 65k pixel format does not match the existing RG16 fourcc code format.
Quoted 5 lines
Quoted 2 lines
Instead of a R:G:B 5:6:5, the controller expects the 16-bit pixels to be R:G:B 6:5:6, and so a new fourcc needs to be added to support this format.
small typo here, R:G:B 6:5:6 => that's 17 bits
Oh, tanks for pointing that out.
It seems to be a typo in the SSD1331 controller datasheet itself:
https://cdn-shop.adafruit.com/datasheets/SSD1331_1.2.pdf
"Each pixel has 16-bit data. Three sub-pixels for color A, B and C have 6 bits, 5 bits and 6 bits respectively."
I blindly copied what the datasheet said without relizing that it was 17 bits indeed!
So looking again at "Table 9 - Data bus usage under different bus width and color depth mode" in the datasheet shared above, it seems the format has the same sub-pixel layout than DRM_FORMAT_RGB565. But I tested with that format and the colors were off, and the same for DRM_FORMAT_BGR565.
Now, even when only using 256 colors the images are pretty decent as you can see in https://fosstodon.org/@javierm/111591985174504541
I'll reword the commit message and drop the comment about that RGB format and explain that only DRM_FORMAT_RGB332 is supported for now.
Quoted 3 lines
other than that, it looks good to me, feel free to add:
Reviewed-by Jocelyn Falempe <[email protected]>
Signature · 5 lines
Best regards, Javier Martinez Canillas Core Platforms Red Hat