drm/vc4: hvs: Various improvements
Subsystems (3)
v2 cover drm/vc4: hvs: Various improvements
Hi,
These patches used to be part of the series:
https://lore.kernel.org/all/[email protected]/
but since the main patch got superseded by another core patch, I've split the cleanup patches out into their own series.
Let me know what you think,
Maxime
Changes from v1:
- Used DRM_PLANE_COMMIT_ACTIVE_ONLY to skip atomic_flush
Maxime Ripard (7):
drm/vc4: kms: Take old state core clock rate into account drm/vc4: hvs: Fix frame count register readout drm/vc4: hvs: Store channel in variable
drm/vc4: hvs: Remove dlist setup duplication
drm/vc4: hvs: Move the dlist setup to its own function drm/vc4: kms: Ignore atomic_flush if we're disabled drm/vc4: hvs: Use pointer to HVS in HVS_READ and HVS_WRITE macros
drivers/gpu/drm/vc4/vc4_crtc.c | 14 ++-- drivers/gpu/drm/vc4/vc4_drv.h | 15 ++-- drivers/gpu/drm/vc4/vc4_hvs.c | 127 ++++++++++++++++++++------------- drivers/gpu/drm/vc4/vc4_kms.c | 13 ++-- drivers/gpu/drm/vc4/vc4_regs.h | 12 +++- 5 files changed, 115 insertions(+), 66 deletions(-)
Signature · 1 line
2.35.1
PATCH v2 1/7 drm/vc4: kms: Take old state core clock rate into account
During a commit, the core clock, which feeds the HVS, needs to run at a minimum of 500MHz.
While doing that commit, we can also change the mode to one that requires a higher core clock, so we take the core clock rate associated to that new state into account for that boost.
However, the old state also needs to be taken into account if it requires a core clock higher that the new one and our 500MHz limit, since it's still live in hardware at the beginning of our commit.
--- drivers/gpu/drm/vc4/vc4_kms.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/gpu/drm/vc4/vc4_kms.c +3 -2
@@ -385,9 +385,10 @@ static void vc4_atomic_commit_tail(struct drm_atomic_state *state) }if (vc4->hvs->hvs5) { +unsigned long state_rate =max (old_hvs_state->core_clock_rate, + new_hvs_state->core_clock_rate); unsigned long core_rate = max_t(unsigned long, -500000000 , - new_hvs_state->core_clock_rate); +500000000 , state_rate);clk_set_min_rate (hvs->core_clk, core_rate); }
Signature · 1 line
2.35.1
PATCH v2 2/7 drm/vc4: hvs: Fix frame count register readout
In reply to Maxime RipardIn order to get the field currently being output, the driver has been using the display FIFO frame count in the HVS, reading a 6-bit field at the offset 12 in the DISPSTATx register.
While that field is indeed at that location for the FIFO 1 and 2, the one for the FIFO0 is actually in the DISPSTAT1 register, at the offset 18.
--- drivers/gpu/drm/vc4/vc4_crtc.c | 2 +- drivers/gpu/drm/vc4/vc4_drv.h | 1 + drivers/gpu/drm/vc4/vc4_hvs.c | 23 +++++++++++++++++++++++ drivers/gpu/drm/vc4/vc4_regs.h | 12 ++++++++++-- 4 files changed, 35 insertions(+), 3 deletions(-)
drivers/gpu/drm/vc4/vc4_crtc.c +1 -1
@@ -123,7 +123,7 @@ static bool vc4_crtc_get_scanout_position(struct drm_crtc *crtc, *vpos /=2 ;/* Use hpos to correct for field offset in interlaced mode. */ -if (VC4_GET_FIELD (val,SCALER_DISPSTATX_FRAME_COUNT ) %2 ) +if (vc4_hvs_get_fifo_frame_count (dev, vc4_crtc_state->assigned_channel) %2 ) *hpos += mode->crtc_htotal /2 ; }
drivers/gpu/drm/vc4/vc4_drv.h +1 -0
@@ -935,6 +935,7 @@ void vc4_irq_reset(struct drm_device *dev);extern struct platform_driver vc4_hvs_driver;void vc4_hvs_stop_channel (struct drm_device *dev,unsigned int output);int vc4_hvs_get_fifo_from_output (struct drm_device *dev,unsigned int output); +u8 vc4_hvs_get_fifo_frame_count (struct drm_device *dev,unsigned int fifo);int vc4_hvs_atomic_check (struct drm_crtc *crtc,struct drm_atomic_state *state);void vc4_hvs_atomic_begin (struct drm_crtc *crtc,struct drm_atomic_state *state);void vc4_hvs_atomic_enable (struct drm_crtc *crtc,struct drm_atomic_state *state);
drivers/gpu/drm/vc4/vc4_hvs.c +23 -0
@@ -197,6 +197,29 @@ static void vc4_hvs_update_gamma_lut(struct drm_crtc *crtc)vc4_hvs_lut_load (crtc); } +u8 vc4_hvs_get_fifo_frame_count (struct drm_device *dev,unsigned int fifo) +{ +struct vc4_dev *vc4 =to_vc4_dev (dev); +u8 field =0 ; + +switch (fifo) { +case 0 : + field =VC4_GET_FIELD (HVS_READ (SCALER_DISPSTAT1 ), +SCALER_DISPSTAT1_FRCNT0 ); +break ; +case 1 : + field =VC4_GET_FIELD (HVS_READ (SCALER_DISPSTAT1 ), +SCALER_DISPSTAT1_FRCNT1 ); +break ; +case 2 : + field =VC4_GET_FIELD (HVS_READ (SCALER_DISPSTAT2 ), +SCALER_DISPSTAT2_FRCNT2 ); +break ; + } + +return field; +} +int vc4_hvs_get_fifo_from_output (struct drm_device *dev,unsigned int output) {struct vc4_dev *vc4 =to_vc4_dev (dev);
drivers/gpu/drm/vc4/vc4_regs.h +10 -2
@@ -379,8 +379,6 @@# define SCALER_DISPSTATX_MODE_EOF 3# define SCALER_DISPSTATX_FULL BIT(29)# define SCALER_DISPSTATX_EMPTY BIT(28) -# define SCALER_DISPSTATX_FRAME_COUNT_MASK VC4_MASK(17, 12) -# define SCALER_DISPSTATX_FRAME_COUNT_SHIFT 12# define SCALER_DISPSTATX_LINE_MASK VC4_MASK(11, 0)# define SCALER_DISPSTATX_LINE_SHIFT 0
@@ -403,9 +401,15 @@ (x) * (SCALER_DISPBKGND1 - \ SCALER_DISPBKGND0))#define SCALER_DISPSTAT1 0x00000058 +# define SCALER_DISPSTAT1_FRCNT0_MASK VC4_MASK(23, 18) +# define SCALER_DISPSTAT1_FRCNT0_SHIFT 18 +# define SCALER_DISPSTAT1_FRCNT1_MASK VC4_MASK(17, 12) +# define SCALER_DISPSTAT1_FRCNT1_SHIFT 12 +#define SCALER_DISPSTATX (x) (SCALER_DISPSTAT0 + \ (x) * (SCALER_DISPSTAT1 - \ SCALER_DISPSTAT0)) +#define SCALER_DISPBASE1 0x0000005c#define SCALER_DISPBASEX (x) (SCALER_DISPBASE0 + \ (x) * (SCALER_DISPBASE1 - \
@@ -415,7 +419,11 @@ (x) * (SCALER_DISPCTRL1 - \ SCALER_DISPCTRL0))#define SCALER_DISPBKGND2 0x00000064 +#define SCALER_DISPSTAT2 0x00000068 +# define SCALER_DISPSTAT2_FRCNT2_MASK VC4_MASK(17, 12) +# define SCALER_DISPSTAT2_FRCNT2_SHIFT 12 +#define SCALER_DISPBASE2 0x0000006c#define SCALER_DISPALPHA2 0x00000070#define SCALER_GAMADDR 0x00000078
Signature · 1 line
2.35.1
PATCH v2 3/7 drm/vc4: hvs: Store channel in variable
In reply to Maxime RipardThe assigned_channel field of our vc4_crtc_state structure is accessed multiple times in vc4_hvs_atomic_flush, so let's move it to a variable that can be used in all those places.
--- drivers/gpu/drm/vc4/vc4_hvs.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
drivers/gpu/drm/vc4/vc4_hvs.c +5 -4
@@ -460,6 +460,7 @@ void vc4_hvs_atomic_flush(struct drm_crtc *crtc,struct drm_device *dev = crtc->dev;struct vc4_dev *vc4 =to_vc4_dev (dev);struct vc4_crtc_state *vc4_state =to_vc4_crtc_state (crtc->state); +unsigned int channel = vc4_state->assigned_channel;struct drm_plane *plane;struct vc4_plane_state *vc4_plane_state;bool debug_dump_regs = false;
@@ -500,8 +501,8 @@ void vc4_hvs_atomic_flush(struct drm_crtc *crtc,/* This sets a black background color fill, as is the case * with other DRM drivers. */ -HVS_WRITE (SCALER_DISPBKGNDX (vc4_state->assigned_channel), -HVS_READ (SCALER_DISPBKGNDX (vc4_state->assigned_channel)) | +HVS_WRITE (SCALER_DISPBKGNDX (channel), +HVS_READ (SCALER_DISPBKGNDX (channel)) |SCALER_DISPBKGND_FILL );/* Only update DISPLIST if the CRTC was already running and is not
@@ -515,7 +516,7 @@ void vc4_hvs_atomic_flush(struct drm_crtc *crtc,vc4_hvs_update_dlist (crtc);if (crtc->state->color_mgmt_changed) { -u32 dispbkgndx =HVS_READ (SCALER_DISPBKGNDX (vc4_state->assigned_channel)); +u32 dispbkgndx =HVS_READ (SCALER_DISPBKGNDX (channel));if (crtc->state->gamma_lut) {vc4_hvs_update_gamma_lut (crtc);
@@ -527,7 +528,7 @@ void vc4_hvs_atomic_flush(struct drm_crtc *crtc,*/ dispbkgndx &= ~SCALER_DISPBKGND_GAMMA ; } -HVS_WRITE (SCALER_DISPBKGNDX (vc4_state->assigned_channel), dispbkgndx); +HVS_WRITE (SCALER_DISPBKGNDX (channel), dispbkgndx); }if (debug_dump_regs) {
Signature · 1 line
2.35.1
PATCH v2 4/7 drm/vc4: hvs: Remove dlist setup duplication
In reply to Maxime RipardSetting the DISPLISTx register needs to occur in every case, and we don't need to protect the register using the event_lock, so we can just move it after the if branches and simplify a bit the function.
--- drivers/gpu/drm/vc4/vc4_hvs.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-)
drivers/gpu/drm/vc4/vc4_hvs.c +3 -6
@@ -402,15 +402,12 @@ static void vc4_hvs_update_dlist(struct drm_crtc *crtc) crtc->state->event =NULL ; } -HVS_WRITE (SCALER_DISPLISTX (vc4_state->assigned_channel), - vc4_state->mm.start); -spin_unlock_irqrestore (&dev->event_lock, flags); - }else { -HVS_WRITE (SCALER_DISPLISTX (vc4_state->assigned_channel), - vc4_state->mm.start); } +HVS_WRITE (SCALER_DISPLISTX (vc4_state->assigned_channel), + vc4_state->mm.start); +spin_lock_irqsave (&vc4_crtc->irq_lock, flags); vc4_crtc->current_dlist = vc4_state->mm.start;spin_unlock_irqrestore (&vc4_crtc->irq_lock, flags);
Signature · 1 line
2.35.1
PATCH v2 5/7 drm/vc4: hvs: Move the dlist setup to its own function
In reply to Maxime RipardThe vc4_hvs_update_dlist function mostly deals with setting up the vblank events and setting up the dlist entry pointer to our current active one.
We'll want to do the former separately from the vblank handling in later patches, so let's move it to a function of its own.
--- drivers/gpu/drm/vc4/vc4_hvs.c | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-)
drivers/gpu/drm/vc4/vc4_hvs.c +14 -5
@@ -382,10 +382,19 @@ int vc4_hvs_atomic_check(struct drm_crtc *crtc, struct drm_atomic_state *state)return 0 ; } +static void vc4_hvs_install_dlist (struct drm_crtc *crtc) +{ +struct drm_device *dev = crtc->dev; +struct vc4_dev *vc4 =to_vc4_dev (dev); +struct vc4_crtc_state *vc4_state =to_vc4_crtc_state (crtc->state); + +HVS_WRITE (SCALER_DISPLISTX (vc4_state->assigned_channel), + vc4_state->mm.start); +} +static void vc4_hvs_update_dlist (struct drm_crtc *crtc) {struct drm_device *dev = crtc->dev; -struct vc4_dev *vc4 =to_vc4_dev (dev);struct vc4_crtc *vc4_crtc =to_vc4_crtc (crtc);struct vc4_crtc_state *vc4_state =to_vc4_crtc_state (crtc->state);unsigned long flags;
@@ -405,9 +414,6 @@ static void vc4_hvs_update_dlist(struct drm_crtc *crtc)spin_unlock_irqrestore (&dev->event_lock, flags); } -HVS_WRITE (SCALER_DISPLISTX (vc4_state->assigned_channel), - vc4_state->mm.start); -spin_lock_irqsave (&vc4_crtc->irq_lock, flags); vc4_crtc->current_dlist = vc4_state->mm.start;spin_unlock_irqrestore (&vc4_crtc->irq_lock, flags);
@@ -434,6 +440,7 @@ void vc4_hvs_atomic_enable(struct drm_crtc *crtc,struct vc4_crtc *vc4_crtc =to_vc4_crtc (crtc);bool oneshot = vc4_crtc->feeds_txp; +vc4_hvs_install_dlist (crtc);vc4_hvs_update_dlist (crtc);vc4_hvs_init_channel (vc4, crtc, mode, oneshot); }
@@ -509,8 +516,10 @@ void vc4_hvs_atomic_flush(struct drm_crtc *crtc,* If the CRTC is being disabled, there's no point in updating this * information. */ -if (crtc->state->active && old_state->active) +if (crtc->state->active && old_state->active) { +vc4_hvs_install_dlist (crtc);vc4_hvs_update_dlist (crtc); + }if (crtc->state->color_mgmt_changed) {u32 dispbkgndx =HVS_READ (SCALER_DISPBKGNDX (channel));
Signature · 1 line
2.35.1
Thomas Zimmermann
maintainerRe: [PATCH v2 5/7] drm/vc4: hvs: Move the dlist setup to its own function
Hi
Am 31.03.22 um 16:37 schrieb Maxime Ripard:
Quoted 56 lines
The
vc4_hvs_update_dlistfunction mostly deals with setting up the vblank events and setting up the dlist entry pointer to our current active one.We'll want to do the former separately from the vblank handling in later patches, so let's move it to a function of its own.
Signed-off-by Maxime Ripard <[email protected]>--- drivers/gpu/drm/vc4/vc4_hvs.c | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-)drivers/gpu/drm/vc4/vc4_hvs.c +11
-4@@ -382,10 +382,19 @@ int vc4_hvs_atomic_check(struct drm_crtc *crtc, struct drm_atomic_state *state)return 0 ; } +static void vc4_hvs_install_dlist (struct drm_crtc *crtc) +{ +struct drm_device *dev = crtc->dev; +struct vc4_dev *vc4 =to_vc4_dev (dev); +struct vc4_crtc_state *vc4_state =to_vc4_crtc_state (crtc->state); + +HVS_WRITE (SCALER_DISPLISTX (vc4_state->assigned_channel), + vc4_state->mm.start); +} +static void vc4_hvs_update_dlist (struct drm_crtc *crtc) {struct drm_device *dev = crtc->dev; -struct vc4_dev *vc4 =to_vc4_dev (dev);struct vc4_crtc *vc4_crtc =to_vc4_crtc (crtc);struct vc4_crtc_state *vc4_state =to_vc4_crtc_state (crtc->state);unsigned long flags;@@ -405,9 +414,6 @@ static void vc4_hvs_update_dlist(struct drm_crtc *crtc)spin_unlock_irqrestore (&dev->event_lock, flags); } -HVS_WRITE (SCALER_DISPLISTX (vc4_state->assigned_channel), - vc4_state->mm.start); -spin_lock_irqsave (&vc4_crtc->irq_lock, flags); vc4_crtc->current_dlist = vc4_state->mm.start;spin_unlock_irqrestore (&vc4_crtc->irq_lock, flags);@@ -434,6 +440,7 @@ void vc4_hvs_atomic_enable(struct drm_crtc *crtc,struct vc4_crtc *vc4_crtc =to_vc4_crtc (crtc);bool oneshot = vc4_crtc->feeds_txp; +vc4_hvs_install_dlist (crtc);vc4_hvs_update_dlist (crtc);vc4_hvs_init_channel (vc4, crtc, mode, oneshot); }
drivers/gpu/drm/vc4/vc4_hvs.c void vc4_hvs_atomic_flush(struct drm_crtc *crtc, · line 522
Quoted 8 lines
drivers/gpu/drm/vc4/vc4_hvs.c +3
-1@@ -509,8 +516,10 @@ void vc4_hvs_atomic_flush(struct drm_crtc *crtc,* If the CRTC is being disabled, there's no point in updating this * information. */ -if (crtc->state->active && old_state->active) +if (crtc->state->active && old_state->active) { +vc4_hvs_install_dlist (crtc);vc4_hvs_update_dlist (crtc); + }
No need for braces here.
Best regards
Thomas
Quoted 3 lines
drivers/gpu/drm/vc4/vc4_hvs.c +0
-0if (crtc->state->color_mgmt_changed) {u32 dispbkgndx =HVS_READ (SCALER_DISPBKGNDX (channel));
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
PATCH v2 6/7 drm/vc4: kms: Ignore atomic_flush if we're disabled
In reply to Maxime Ripardatomic_flush will be called for each CRTC even if they aren't enabled.
The whole code we have there will thus run without a properly affected channel, which can then result in all sorts of weird behaviour.
Fortunately, the DRM_PLANE_COMMIT_ACTIVE_ONLY flag will skip the CRTC atomic_begin and atomic_flush, and the planes atomic_update, if they aren't enabled.
Our plane atomic_update is a nop, and atomic_begin will copy the current HVS channel to the vc4_crtc structure for the interrupt handler to consume, but the handler won't run if the CRTC is disabled. So in the end, it will only skip our CRTC atomic_flush, which is what we want.
--- drivers/gpu/drm/vc4/vc4_kms.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/vc4/vc4_kms.c +2 -1
@@ -401,7 +401,8 @@ static void vc4_atomic_commit_tail(struct drm_atomic_state *state)else vc4_hvs_pv_muxing_commit (vc4, state); -drm_atomic_helper_commit_planes (dev, state,0 ); +drm_atomic_helper_commit_planes (dev, state, +DRM_PLANE_COMMIT_ACTIVE_ONLY );drm_atomic_helper_commit_modeset_enables (dev, state);
Signature · 1 line
2.35.1
PATCH v2 7/7 drm/vc4: hvs: Use pointer to HVS in HVS_READ and HVS_WRITE macros
In reply to Maxime RipardThose macros are really about the HVS itself, and thus its associated structure vc4_hvs, rather than the entire (virtual) vc4 device.
Let's change those macros to use the hvs pointer directly, and change the calling sites accordingly.
--- drivers/gpu/drm/vc4/vc4_crtc.c | 14 +++++-- drivers/gpu/drm/vc4/vc4_drv.h | 16 +++---- drivers/gpu/drm/vc4/vc4_hvs.c | 77 +++++++++++++++++----------------- drivers/gpu/drm/vc4/vc4_kms.c | 5 ++- 4 files changed, 60 insertions(+), 52 deletions(-)
drivers/gpu/drm/vc4/vc4_crtc.c +10 -4
@@ -70,6 +70,7 @@ static const struct debugfs_reg32 crtc_regs[] = {static unsigned int vc4_crtc_get_cob_allocation (struct vc4_dev *vc4,unsigned int channel) { +struct vc4_hvs *hvs = vc4->hvs;u32 dispbase =HVS_READ (SCALER_DISPBASEX (channel));/* Top/base are supposed to be 4-pixel aligned, but the * Raspberry Pi firmware fills the low bits (which are
@@ -89,6 +90,7 @@ static bool vc4_crtc_get_scanout_position(struct drm_crtc *crtc, {struct drm_device *dev = crtc->dev;struct vc4_dev *vc4 =to_vc4_dev (dev); +struct vc4_hvs *hvs = vc4->hvs;struct vc4_crtc *vc4_crtc =to_vc4_crtc (crtc);struct vc4_crtc_state *vc4_crtc_state =to_vc4_crtc_state (crtc->state);unsigned int cob_size;
@@ -123,7 +125,7 @@ static bool vc4_crtc_get_scanout_position(struct drm_crtc *crtc, *vpos /=2 ;/* Use hpos to correct for field offset in interlaced mode. */ -if (vc4_hvs_get_fifo_frame_count (dev, vc4_crtc_state->assigned_channel) %2 ) +if (vc4_hvs_get_fifo_frame_count (hvs, vc4_crtc_state->assigned_channel) %2 ) *hpos += mode->crtc_htotal /2 ; }
@@ -413,6 +415,7 @@ static void vc4_crtc_config_pv(struct drm_crtc *crtc, struct drm_encoder *encodestatic void require_hvs_enabled (struct drm_device *dev) {struct vc4_dev *vc4 =to_vc4_dev (dev); +struct vc4_hvs *hvs = vc4->hvs;WARN_ON_ONCE ((HVS_READ (SCALER_DISPCTRL ) &SCALER_DISPCTRL_ENABLE ) !=SCALER_DISPCTRL_ENABLE );
@@ -426,6 +429,7 @@ static int vc4_crtc_disable(struct drm_crtc *crtc,struct vc4_encoder *vc4_encoder =to_vc4_encoder (encoder);struct vc4_crtc *vc4_crtc =to_vc4_crtc (crtc);struct drm_device *dev = crtc->dev; +struct vc4_dev *vc4 =to_vc4_dev (dev);int ret; CRTC_WRITE(PV_V_CONTROL,
@@ -455,7 +459,7 @@ static int vc4_crtc_disable(struct drm_crtc *crtc, vc4_encoder->post_crtc_disable (encoder, state);vc4_crtc_pixelvalve_reset (crtc); -vc4_hvs_stop_channel (dev, channel); +vc4_hvs_stop_channel (vc4->hvs, channel);if (vc4_encoder && vc4_encoder->post_crtc_powerdown) vc4_encoder->post_crtc_powerdown (encoder, state);
@@ -481,6 +485,7 @@ static struct drm_encoder *vc4_crtc_get_encoder_by_type(struct drm_crtc *crtc,int vc4_crtc_disable_at_boot (struct drm_crtc *crtc) {struct drm_device *drm = crtc->dev; +struct vc4_dev *vc4 =to_vc4_dev (drm);struct vc4_crtc *vc4_crtc =to_vc4_crtc (crtc);enum vc4_encoder_type encoder_type;const struct vc4_pv_data *pv_data;
@@ -502,7 +507,7 @@ int vc4_crtc_disable_at_boot(struct drm_crtc *crtc)if (!(CRTC_READ (PV_V_CONTROL ) &PV_VCONTROL_VIDEN ))return 0 ; - channel =vc4_hvs_get_fifo_from_output (drm, vc4_crtc->data->hvs_output); + channel =vc4_hvs_get_fifo_from_output (vc4->hvs, vc4_crtc->data->hvs_output);if (channel <0 )return 0 ;
@@ -715,6 +720,7 @@ static void vc4_crtc_handle_page_flip(struct vc4_crtc *vc4_crtc)struct drm_crtc *crtc = &vc4_crtc->base;struct drm_device *dev = crtc->dev;struct vc4_dev *vc4 =to_vc4_dev (dev); +struct vc4_hvs *hvs = vc4->hvs;u32 chan = vc4_crtc->current_hvs_channel;unsigned long flags;
@@ -733,7 +739,7 @@ static void vc4_crtc_handle_page_flip(struct vc4_crtc *vc4_crtc)* the CRTC and encoder already reconfigured, leading to * underruns. This can be seen when reconfiguring the CRTC. */ -vc4_hvs_unmask_underrun (dev, chan); +vc4_hvs_unmask_underrun (hvs, chan); }spin_unlock (&vc4_crtc->irq_lock);spin_unlock_irqrestore (&dev->event_lock, flags);
drivers/gpu/drm/vc4/vc4_drv.h +8 -8
@@ -574,8 +574,8 @@ to_vc4_crtc_state(struct drm_crtc_state *crtc_state)#define V3D_READ (offset) readl(vc4->v3d->regs + offset)#define V3D_WRITE (offset, val) writel(val, vc4->v3d->regs + offset) -#define HVS_READ (offset) readl(vc4->hvs->regs + offset) -#define HVS_WRITE (offset, val) writel(val, vc4->hvs->regs + offset) +#define HVS_READ (offset) readl(hvs->regs + offset) +#define HVS_WRITE (offset, val) writel(val, hvs->regs + offset)#define VC4_REG32 (reg) { .name = #reg, .offset = reg }
@@ -933,17 +933,17 @@ void vc4_irq_reset(struct drm_device *dev);/* vc4_hvs.c */ extern struct platform_driver vc4_hvs_driver; -void vc4_hvs_stop_channel (struct drm_device *dev,unsigned int output); -int vc4_hvs_get_fifo_from_output (struct drm_device *dev,unsigned int output); -u8 vc4_hvs_get_fifo_frame_count (struct drm_device *dev,unsigned int fifo); +void vc4_hvs_stop_channel (struct vc4_hvs *hvs,unsigned int output); +int vc4_hvs_get_fifo_from_output (struct vc4_hvs *hvs,unsigned int output); +u8 vc4_hvs_get_fifo_frame_count (struct vc4_hvs *hvs,unsigned int fifo);int vc4_hvs_atomic_check (struct drm_crtc *crtc,struct drm_atomic_state *state);void vc4_hvs_atomic_begin (struct drm_crtc *crtc,struct drm_atomic_state *state);void vc4_hvs_atomic_enable (struct drm_crtc *crtc,struct drm_atomic_state *state);void vc4_hvs_atomic_disable (struct drm_crtc *crtc,struct drm_atomic_state *state);void vc4_hvs_atomic_flush (struct drm_crtc *crtc,struct drm_atomic_state *state); -void vc4_hvs_dump_state (struct drm_device *dev); -void vc4_hvs_unmask_underrun (struct drm_device *dev,int channel); -void vc4_hvs_mask_underrun (struct drm_device *dev,int channel); +void vc4_hvs_dump_state (struct vc4_hvs *hvs); +void vc4_hvs_unmask_underrun (struct vc4_hvs *hvs,int channel); +void vc4_hvs_mask_underrun (struct vc4_hvs *hvs,int channel);/* vc4_kms.c */ int vc4_kms_load (struct drm_device *dev);
drivers/gpu/drm/vc4/vc4_hvs.c +38 -39
223 lines not on this page · raw message
drivers/gpu/drm/vc4/vc4_kms.c +4 -1
@@ -157,6 +157,7 @@ static u16 vc4_ctm_s31_32_to_s0_9(u64 in)static void vc4_ctm_commit (struct vc4_dev *vc4,struct drm_atomic_state *state) { +struct vc4_hvs *hvs = vc4->hvs;struct vc4_ctm_state *ctm_state =to_vc4_ctm_state (vc4->ctm_manager.state);struct drm_color_ctm *ctm = ctm_state->ctm;
@@ -230,6 +231,7 @@ vc4_hvs_get_global_state(struct drm_atomic_state *state)static void vc4_hvs_pv_muxing_commit (struct vc4_dev *vc4,struct drm_atomic_state *state) { +struct vc4_hvs *hvs = vc4->hvs;struct drm_crtc_state *crtc_state;struct drm_crtc *crtc;unsigned int i;
@@ -270,6 +272,7 @@ static void vc4_hvs_pv_muxing_commit(struct vc4_dev *vc4,static void vc5_hvs_pv_muxing_commit (struct vc4_dev *vc4,struct drm_atomic_state *state) { +struct vc4_hvs *hvs = vc4->hvs;struct drm_crtc_state *crtc_state;struct drm_crtc *crtc;unsigned char mux;
@@ -362,7 +365,7 @@ static void vc4_atomic_commit_tail(struct drm_atomic_state *state)continue ; vc4_crtc_state =to_vc4_crtc_state (new_crtc_state); -vc4_hvs_mask_underrun (dev, vc4_crtc_state->assigned_channel); +vc4_hvs_mask_underrun (hvs, vc4_crtc_state->assigned_channel); }for (channel =0 ; channel <HVS_NUM_CHANNELS ; channel++) {
Signature · 1 line
2.35.1
Hi Maxime,
for the whole patchset
Best regards
Thomas
Am 31.03.22 um 16:37 schrieb Maxime Ripard:
Quoted 30 lines
Hi,
These patches used to be part of the series:
https://lore.kernel.org/all/[email protected]/but since the main patch got superseded by another core patch, I've split the cleanup patches out into their own series.
Let me know what you think,
MaximeChanges from v1:
- UsedDRM_PLANE_COMMIT_ACTIVE_ONLYto skipatomic_flushMaxime Ripard (7):
drm/vc4: kms: Take old state core clock rate into account drm/vc4: hvs: Fix frame count register readout drm/vc4: hvs: Store channel in variable
drm/vc4: hvs: Remove dlist setup duplication
drm/vc4: hvs: Move the dlist setup to its own function drm/vc4: kms: Ignoreatomic_flushif we're disabled drm/vc4: hvs: Use pointer to HVS inHVS_READandHVS_WRITEmacrosdrivers/gpu/drm/vc4/vc4_crtc.c | 14 ++-- drivers/gpu/drm/vc4/vc4_drv.h | 15 ++-- drivers/gpu/drm/vc4/vc4_hvs.c | 127 ++++++++++++++++++++------------- drivers/gpu/drm/vc4/vc4_kms.c | 13 ++-- drivers/gpu/drm/vc4/vc4_regs.h | 12 +++- 5 files changed, 115 insertions(+), 66 deletions(-)
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Maxime Ripard
AppliedQuoted 10 lines · Maxime Ripard
These patches used to be part of the series:
https://lore.kernel.org/all/[email protected]/but since the main patch got superseded by another core patch, I've split the cleanup patches out into their own series.
Let me know what you think,
Maxime[...]
Applied to drm/drm-misc (drm-misc-next).
Thanks!
Maxime