drm/mxsfb: use bus_format to determine LCD bus width
Subsystems (4)
Stefan Agner
maintainerPATCH v2 1/1 drm/mxsfb: use bus_format to determine LCD bus width
The LCD bus width does not need to align with the pixel format. The LCDIF controller automatically converts between pixel formats and bus width by padding or dropping LSBs.
The DRM subsystem has the notion of bus_format which allows to determine what bus_formats are supported by the display. Choose the first available or fallback to 24 bit if none are available.
---
Changes in v2:
- Use seperate function mxsfb_set_bus_fmt
drivers/gpu/drm/mxsfb/mxsfb_crtc.c | 33 +++++++++++++++++++++++++++++++-- drivers/gpu/drm/mxsfb/mxsfb_regs.h | 1 + 2 files changed, 32 insertions(+), 2 deletions(-)
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +31 -2
@@ -65,13 +65,11 @@ static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb)switch (format) {case DRM_FORMAT_RGB565 :dev_dbg (drm->dev,"Setting up RGB565 mode\n" ); - ctrl |=CTRL_SET_BUS_WIDTH (STMLCDIF_16BIT ); ctrl |=CTRL_SET_WORD_LENGTH (0 ); ctrl1 |=CTRL1_SET_BYTE_PACKAGING (0xf );break ;case DRM_FORMAT_XRGB8888 :dev_dbg (drm->dev,"Setting up XRGB8888 mode\n" ); - ctrl |=CTRL_SET_BUS_WIDTH (STMLCDIF_24BIT ); ctrl |=CTRL_SET_WORD_LENGTH (3 );/* Do not use packed pixels = one pixel per word instead. */ ctrl1 |=CTRL1_SET_BYTE_PACKAGING (0x7 );
@@ -87,6 +85,35 @@ static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb)return 0 ; } +static void mxsfb_set_bus_fmt (struct mxsfb_drm_private *mxsfb) +{ +struct drm_crtc *crtc = &mxsfb->pipe.crtc; +struct drm_device *drm = crtc->dev; +u32 bus_format =MEDIA_BUS_FMT_RGB888_1X24 ; +u32 reg; + +writel (CTRL_BUS_WIDTH_MASK , mxsfb->base +LCDC_CTRL +REG_CLR ); + +if (mxsfb->connector.display_info.num_bus_formats) + bus_format = mxsfb->connector.display_info.bus_formats[0 ]; + +switch (bus_format) { +case MEDIA_BUS_FMT_RGB565_1X16 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_16BIT ); +break ; +case MEDIA_BUS_FMT_RGB666_1X18 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_18BIT ); +break ; +case MEDIA_BUS_FMT_RGB888_1X24 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_24BIT ); +break ; +default : +dev_err (drm->dev,"Unknown media bus format %d\n" , bus_format); +break ; + } +writel (reg, mxsfb->base +LCDC_CTRL +REG_SET ); +} +static void mxsfb_enable_controller (struct mxsfb_drm_private *mxsfb) {u32 reg;
@@ -182,6 +209,8 @@ static void mxsfb_crtc_mode_set_nofb(struct mxsfb_drm_private *mxsfb)writel (vdctrl0, mxsfb->base +LCDC_VDCTRL0 ); +mxsfb_set_bus_fmt (mxsfb); +/* Frame length in lines. */ writel (m->crtc_vtotal, mxsfb->base +LCDC_VDCTRL1 );
drivers/gpu/drm/mxsfb/mxsfb_regs.h +1 -0
@@ -44,6 +44,7 @@#define CTRL_DATA_SELECT (1 << 16)#define CTRL_SET_BUS_WIDTH (x) (((x) & 0x3) << 10)#define CTRL_GET_BUS_WIDTH (x) (((x) >> 10) & 0x3) +#define CTRL_BUS_WIDTH_MASK (0x3 << 10)#define CTRL_SET_WORD_LENGTH (x) (((x) & 0x3) << 8)#define CTRL_GET_WORD_LENGTH (x) (((x) >> 8) & 0x3)#define CTRL_MASTER (1 << 5)
Signature · 6 lines
2.10.2 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Marek Vasut
maintainerQuoted 9 lines · Stefan Agner
The LCD bus width does not need to align with the pixel format. The LCDIF controller automatically converts between pixel formats and bus width by padding or dropping LSBs.
The DRM subsystem has the notion of
bus_formatwhich allows to determine whatbus_formatsare supported by the display. Choose the first available or fallback to 24 bit if none are available.Signed-off-by Stefan Agner <[email protected]>
Minor nits below.
Quoted 27 lines
---
Changes in v2:
- Use seperate functionmxsfb_set_bus_fmtdrivers/gpu/drm/mxsfb/mxsfb_crtc.c | 33 +++++++++++++++++++++++++++++++-- drivers/gpu/drm/mxsfb/mxsfb_regs.h | 1 + 2 files changed, 32 insertions(+), 2 deletions(-)drivers/gpu/drm/mxsfb/mxsfb_crtc.c +0
-2@@ -65,13 +65,11 @@ static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb)switch (format) {case DRM_FORMAT_RGB565 :dev_dbg (drm->dev,"Setting up RGB565 mode\n" ); - ctrl |=CTRL_SET_BUS_WIDTH (STMLCDIF_16BIT ); ctrl |=CTRL_SET_WORD_LENGTH (0 ); ctrl1 |=CTRL1_SET_BYTE_PACKAGING (0xf );break ;case DRM_FORMAT_XRGB8888 :dev_dbg (drm->dev,"Setting up XRGB8888 mode\n" ); - ctrl |=CTRL_SET_BUS_WIDTH (STMLCDIF_24BIT ); ctrl |=CTRL_SET_WORD_LENGTH (3 );/* Do not use packed pixels = one pixel per word instead. */ ctrl1 |=CTRL1_SET_BYTE_PACKAGING (0x7 );
drivers/gpu/drm/mxsfb/mxsfb_crtc.c static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb) · line 93
Quoted 9 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +6
-0@@ -87,6 +85,35 @@ static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb)return 0 ; } +static void mxsfb_set_bus_fmt (struct mxsfb_drm_private *mxsfb) +{ +struct drm_crtc *crtc = &mxsfb->pipe.crtc; +struct drm_device *drm = crtc->dev; +u32 bus_format =MEDIA_BUS_FMT_RGB888_1X24 ; +u32 reg;
^^^ this is uninitialized
drivers/gpu/drm/mxsfb/mxsfb_crtc.c static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb) · line 102
Quoted 8 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +8
-0+writel (CTRL_BUS_WIDTH_MASK , mxsfb->base +LCDC_CTRL +REG_CLR ); + +if (mxsfb->connector.display_info.num_bus_formats) + bus_format = mxsfb->connector.display_info.bus_formats[0 ]; + +switch (bus_format) { +case MEDIA_BUS_FMT_RGB565_1X16 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_16BIT );
^^^
here you're doing operation on uninited value.
drivers/gpu/drm/mxsfb/mxsfb_crtc.c static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb) · line 114
Quoted 12 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +12
-0+break ; +case MEDIA_BUS_FMT_RGB666_1X18 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_18BIT ); +break ; +case MEDIA_BUS_FMT_RGB888_1X24 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_24BIT ); +break ; +default : +dev_err (drm->dev,"Unknown media bus format %d\n" , bus_format); +break ; + } +writel (reg, mxsfb->base +LCDC_CTRL +REG_SET );
What I was thinking might be better is to save the calculated LCD_CRTC value in mxsfb_drm_private , but maybe R-M-W is good enough after all? Two writes are IMO not great because it unnecessarily reconfigures the controller twice.
Quoted 27 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +4
-0+} +static void mxsfb_enable_controller (struct mxsfb_drm_private *mxsfb) {u32 reg;@@ -182,6 +209,8 @@ static void mxsfb_crtc_mode_set_nofb(struct mxsfb_drm_private *mxsfb)writel (vdctrl0, mxsfb->base +LCDC_VDCTRL0 ); +mxsfb_set_bus_fmt (mxsfb); +/* Frame length in lines. */ writel (m->crtc_vtotal, mxsfb->base +LCDC_VDCTRL1 );drivers/gpu/drm/mxsfb/mxsfb_regs.h +1
-0@@ -44,6 +44,7 @@#define CTRL_DATA_SELECT (1 << 16)#define CTRL_SET_BUS_WIDTH (x) (((x) & 0x3) << 10)#define CTRL_GET_BUS_WIDTH (x) (((x) >> 10) & 0x3) +#define CTRL_BUS_WIDTH_MASK (0x3 << 10)#define CTRL_SET_WORD_LENGTH (x) (((x) & 0x3) << 8)#define CTRL_GET_WORD_LENGTH (x) (((x) >> 8) & 0x3)#define CTRL_MASTER (1 << 5)
Signature · 2 lines
Best regards, Marek Vasut
Stefan Agner
maintainerQuoted 62 lines · Marek Vasut
Quoted 9 lines · Stefan Agner
The LCD bus width does not need to align with the pixel format. The LCDIF controller automatically converts between pixel formats and bus width by padding or dropping LSBs.
The DRM subsystem has the notion of
bus_formatwhich allows to determine whatbus_formatsare supported by the display. Choose the first available or fallback to 24 bit if none are available.Signed-off-by Stefan Agner <[email protected]>Minor nits below.
Quoted 27 lines
---
Changes in v2:
- Use seperate functionmxsfb_set_bus_fmtdrivers/gpu/drm/mxsfb/mxsfb_crtc.c | 33 +++++++++++++++++++++++++++++++-- drivers/gpu/drm/mxsfb/mxsfb_regs.h | 1 + 2 files changed, 32 insertions(+), 2 deletions(-)drivers/gpu/drm/mxsfb/mxsfb_crtc.c +0
-2@@ -65,13 +65,11 @@ static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb)switch (format) {case DRM_FORMAT_RGB565 :dev_dbg (drm->dev,"Setting up RGB565 mode\n" ); - ctrl |=CTRL_SET_BUS_WIDTH (STMLCDIF_16BIT ); ctrl |=CTRL_SET_WORD_LENGTH (0 ); ctrl1 |=CTRL1_SET_BYTE_PACKAGING (0xf );break ;case DRM_FORMAT_XRGB8888 :dev_dbg (drm->dev,"Setting up XRGB8888 mode\n" ); - ctrl |=CTRL_SET_BUS_WIDTH (STMLCDIF_24BIT ); ctrl |=CTRL_SET_WORD_LENGTH (3 );/* Do not use packed pixels = one pixel per word instead. */ ctrl1 |=CTRL1_SET_BYTE_PACKAGING (0x7 );drivers/gpu/drm/mxsfb/mxsfb_crtc.c static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb) · line 93
Quoted 9 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +6
-0@@ -87,6 +85,35 @@ static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb)return 0 ; } +static void mxsfb_set_bus_fmt (struct mxsfb_drm_private *mxsfb) +{ +struct drm_crtc *crtc = &mxsfb->pipe.crtc; +struct drm_device *drm = crtc->dev; +u32 bus_format =MEDIA_BUS_FMT_RGB888_1X24 ; +u32 reg;^^^ this is uninitialized
drivers/gpu/drm/mxsfb/mxsfb_crtc.c static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb) · line 102
Quoted 8 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +8
-0+writel (CTRL_BUS_WIDTH_MASK , mxsfb->base +LCDC_CTRL +REG_CLR ); + +if (mxsfb->connector.display_info.num_bus_formats) + bus_format = mxsfb->connector.display_info.bus_formats[0 ]; + +switch (bus_format) { +case MEDIA_BUS_FMT_RGB565_1X16 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_16BIT );^^^
here you're doing operation on uninited value.
Quoted 15 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb) · line 114
Quoted 12 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +12
-0+break ; +case MEDIA_BUS_FMT_RGB666_1X18 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_18BIT ); +break ; +case MEDIA_BUS_FMT_RGB888_1X24 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_24BIT ); +break ; +default : +dev_err (drm->dev,"Unknown media bus format %d\n" , bus_format); +break ; + } +writel (reg, mxsfb->base +LCDC_CTRL +REG_SET );What I was thinking might be better is to save the calculated
LCD_CRTCvalue inmxsfb_drm_private, but maybe R-M-W is good enough after all?
Yeah I see what you are saying, however I would prefer to not cache if there is no real reason to...
It is now a write to the clear and one write to the set variant of the register, not sure if that counts as "two writes".
Quoted 2 lines
Two writes are IMO not great because it unnecessarily reconfigures the controller twice.
Does that matter? At this point, the RUN bit is guaranteed not to be set...
--
Stefan
Quoted 15 lines
Quoted 15 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +4
-0+} +static void mxsfb_enable_controller (struct mxsfb_drm_private *mxsfb) {u32 reg;@@ -182,6 +209,8 @@ static void mxsfb_crtc_mode_set_nofb(struct mxsfb_drm_private *mxsfb)writel (vdctrl0, mxsfb->base +LCDC_VDCTRL0 ); +mxsfb_set_bus_fmt (mxsfb); +/* Frame length in lines. */ writel (m->crtc_vtotal, mxsfb->base +LCDC_VDCTRL1 );
Quoted 13 lines
drivers/gpu/drm/mxsfb/mxsfb_regs.h line 50
Quoted 13 lines
drivers/gpu/drm/mxsfb/mxsfb_regs.h +1
-0@@ -44,6 +44,7 @@#define CTRL_DATA_SELECT (1 << 16)#define CTRL_SET_BUS_WIDTH (x) (((x) & 0x3) << 10)#define CTRL_GET_BUS_WIDTH (x) (((x) >> 10) & 0x3) +#define CTRL_BUS_WIDTH_MASK (0x3 << 10)#define CTRL_SET_WORD_LENGTH (x) (((x) & 0x3) << 8)#define CTRL_GET_WORD_LENGTH (x) (((x) >> 8) & 0x3)#define CTRL_MASTER (1 << 5)
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Marek Vasut
maintainerQuoted 79 lines · Stefan Agner
Quoted 62 lines · Marek Vasut
Quoted 9 lines · Stefan Agner
The LCD bus width does not need to align with the pixel format. The LCDIF controller automatically converts between pixel formats and bus width by padding or dropping LSBs.
The DRM subsystem has the notion of
bus_formatwhich allows to determine whatbus_formatsare supported by the display. Choose the first available or fallback to 24 bit if none are available.Signed-off-by Stefan Agner <[email protected]>Minor nits below.
Quoted 27 lines
---
Changes in v2:
- Use seperate functionmxsfb_set_bus_fmtdrivers/gpu/drm/mxsfb/mxsfb_crtc.c | 33 +++++++++++++++++++++++++++++++-- drivers/gpu/drm/mxsfb/mxsfb_regs.h | 1 + 2 files changed, 32 insertions(+), 2 deletions(-)drivers/gpu/drm/mxsfb/mxsfb_crtc.c +0
-2@@ -65,13 +65,11 @@ static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb)switch (format) {case DRM_FORMAT_RGB565 :dev_dbg (drm->dev,"Setting up RGB565 mode\n" ); - ctrl |=CTRL_SET_BUS_WIDTH (STMLCDIF_16BIT ); ctrl |=CTRL_SET_WORD_LENGTH (0 ); ctrl1 |=CTRL1_SET_BYTE_PACKAGING (0xf );break ;case DRM_FORMAT_XRGB8888 :dev_dbg (drm->dev,"Setting up XRGB8888 mode\n" ); - ctrl |=CTRL_SET_BUS_WIDTH (STMLCDIF_24BIT ); ctrl |=CTRL_SET_WORD_LENGTH (3 );/* Do not use packed pixels = one pixel per word instead. */ ctrl1 |=CTRL1_SET_BYTE_PACKAGING (0x7 );drivers/gpu/drm/mxsfb/mxsfb_crtc.c static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb) · line 93
Quoted 9 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +6
-0@@ -87,6 +85,35 @@ static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb)return 0 ; } +static void mxsfb_set_bus_fmt (struct mxsfb_drm_private *mxsfb) +{ +struct drm_crtc *crtc = &mxsfb->pipe.crtc; +struct drm_device *drm = crtc->dev; +u32 bus_format =MEDIA_BUS_FMT_RGB888_1X24 ; +u32 reg;^^^ this is uninitialized
drivers/gpu/drm/mxsfb/mxsfb_crtc.c static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb) · line 102
Quoted 8 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +8
-0+writel (CTRL_BUS_WIDTH_MASK , mxsfb->base +LCDC_CTRL +REG_CLR ); + +if (mxsfb->connector.display_info.num_bus_formats) + bus_format = mxsfb->connector.display_info.bus_formats[0 ]; + +switch (bus_format) { +case MEDIA_BUS_FMT_RGB565_1X16 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_16BIT );^^^
here you're doing operation on uninited value.Quoted 15 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c static int mxsfb_set_pixel_fmt(struct mxsfb_drm_private *mxsfb) · line 114
Quoted 12 lines
drivers/gpu/drm/mxsfb/mxsfb_crtc.c +12
-0+break ; +case MEDIA_BUS_FMT_RGB666_1X18 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_18BIT ); +break ; +case MEDIA_BUS_FMT_RGB888_1X24 : + reg |=CTRL_SET_BUS_WIDTH (STMLCDIF_24BIT ); +break ; +default : +dev_err (drm->dev,"Unknown media bus format %d\n" , bus_format); +break ; + } +writel (reg, mxsfb->base +LCDC_CTRL +REG_SET );What I was thinking might be better is to save the calculated
LCD_CRTCvalue inmxsfb_drm_private, but maybe R-M-W is good enough after all?
Quoted 2 lines
Yeah I see what you are saying, however I would prefer to not cache if there is no real reason to...
OK
Quoted 2 lines
It is now a write to the clear and one write to the set variant of the register, not sure if that counts as "two writes".
It's two writel() calls, it does.
Quoted 5 lines
Quoted 2 lines
Two writes are IMO not great because it unnecessarily reconfigures the controller twice.
Does that matter? At this point, the RUN bit is guaranteed not to be set...
It's probably a matter of taste, although I'd be more comfortable with RMW here.
Signature · 2 lines
Best regards, Marek Vasut