drm/vc4: crtc: Rework a bit the CRTC state code
Subsystems (3)
PATCH v2 1/2 drm/vc4: crtc: Rework a bit the CRTC state code
The current CRTC state reset hook in vc4 allocates a vc4_crtc_state structure as a drm_crtc_state, and relies on the fact that vc4_crtc_state embeds drm_crtc_state as its first member, and therefore can be safely casted.
However, this is pretty fragile especially since there's no check for this in place, and we're going to need to access vc4_crtc_state member at reset so this looks like a good occasion to make it more robust.
---
Changes from v1:
- new patch
--- drivers/gpu/drm/vc4/vc4_crtc.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
drivers/gpu/drm/vc4/vc4_crtc.c +10 -3
@@ -852,11 +852,18 @@ void vc4_crtc_destroy_state(struct drm_crtc *crtc,void vc4_crtc_reset (struct drm_crtc *crtc) { +struct vc4_crtc_state *vc4_crtc_state; +if (crtc->state)vc4_crtc_destroy_state (crtc, crtc->state); - crtc->state =kzalloc (sizeof (struct vc4_crtc_state ),GFP_KERNEL ); -if (crtc->state) -__drm_atomic_helper_crtc_reset (crtc, crtc->state); + + vc4_crtc_state =kzalloc (sizeof (*vc4_crtc_state),GFP_KERNEL ); +if (!vc4_crtc_state) { + crtc->state =NULL ; +return ; + } + +__drm_atomic_helper_crtc_reset (crtc, &vc4_crtc_state->base); }static const struct drm_crtc_funcs vc4_crtc_funcs = {
Signature · 7 lines
2.26.2 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH v2 2/2 drm/vc4: crtc: Keep the previously assigned HVS FIFO
The HVS FIFOs are currently assigned each time we have an atomic_check for all the enabled CRTCs.
However, if we are running multiple outputs in parallel and we happen to disable the first (by index) CRTC, we end up changing the assigned FIFO of the second CRTC without disabling and reenabling the pixelvalve which ends up in a stall and eventually a VBLANK timeout.
In order to fix this, we can create a special value for our assigned channel to mark it as disabled, and if our CRTC already had an assigned channel in its previous state, we keep on using it.
---
Changes from v1:
- Split away the crtc state reset refactoring
- Fixed the checkpatch warnings
--- drivers/gpu/drm/vc4/vc4_crtc.c | 1 + drivers/gpu/drm/vc4/vc4_drv.h | 2 ++ drivers/gpu/drm/vc4/vc4_kms.c | 22 ++++++++++++++++------ 3 files changed, 19 insertions(+), 6 deletions(-)
drivers/gpu/drm/vc4/vc4_crtc.c +1 -0
@@ -863,6 +863,7 @@ void vc4_crtc_reset(struct drm_crtc *crtc)return ; } + vc4_crtc_state->assigned_channel =VC4_HVS_CHANNEL_DISABLED ;__drm_atomic_helper_crtc_reset (crtc, &vc4_crtc_state->base); }
drivers/gpu/drm/vc4/vc4_drv.h +2 -0
@@ -532,6 +532,8 @@ struct vc4_crtc_state { } margins; }; +#define VC4_HVS_CHANNEL_DISABLED ((unsigned int)-1) +static inline struct vc4_crtc_state *to_vc4_crtc_state (struct drm_crtc_state *crtc_state) {
drivers/gpu/drm/vc4/vc4_kms.c +16 -6
@@ -616,7 +616,7 @@ static int vc4_atomic_check(struct drm_device *dev, struct drm_atomic_state *state) { unsigned long unassigned_channels = GENMASK(NUM_CHANNELS - 1, 0); -struct drm_crtc_state *crtc_state; +struct drm_crtc_state *old_crtc_state, *new_crtc_state;struct drm_crtc *crtc;int i, ret;
@@ -629,6 +629,8 @@ vc4_atomic_check(struct drm_device *dev, struct drm_atomic_state *state)* modified. */ list_for_each_entry (crtc, &dev->mode_config.crtc_list, head) { +struct drm_crtc_state *crtc_state; +if (!crtc->state->enable)continue ;
@@ -637,15 +639,23 @@ vc4_atomic_check(struct drm_device *dev, struct drm_atomic_state *state)return PTR_ERR (crtc_state); } -for_each_new_crtc_in_state (state, crtc, crtc_state, i) { -struct vc4_crtc_state *vc4_crtc_state = -to_vc4_crtc_state (crtc_state); +for_each_oldnew_crtc_in_state (state, crtc, old_crtc_state, new_crtc_state, i) { +struct vc4_crtc_state *new_vc4_crtc_state = +to_vc4_crtc_state (new_crtc_state);struct vc4_crtc *vc4_crtc =to_vc4_crtc (crtc);unsigned int matching_channels; -if (!crtc_state->enable) +if (old_crtc_state->enable && !new_crtc_state->enable) + new_vc4_crtc_state->assigned_channel =VC4_HVS_CHANNEL_DISABLED ; + +if (!new_crtc_state->enable)continue ; +if (new_vc4_crtc_state->assigned_channel !=VC4_HVS_CHANNEL_DISABLED ) { + unassigned_channels &= ~BIT (new_vc4_crtc_state->assigned_channel); +continue ; + } +/* * The problem we have to solve here is that we have * up to 7 encoders, connected to up to 6 CRTCs.
@@ -674,7 +684,7 @@ vc4_atomic_check(struct drm_device *dev, struct drm_atomic_state *state)if (matching_channels) {unsigned int channel =ffs (matching_channels) -1 ; - vc4_crtc_state->assigned_channel = channel; + new_vc4_crtc_state->assigned_channel = channel; unassigned_channels &= ~BIT (channel); }else {return -EINVAL ;
Signature · 7 lines
2.26.2 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v2 2/2] drm/vc4: crtc: Keep the previously assigned HVS FIFO
Hi Maxime
Sorry for the delay.
Quoted 9 lines · Maxime Ripard
The HVS FIFOs are currently assigned each time we have an
atomic_checkfor all the enabled CRTCs.However, if we are running multiple outputs in parallel and we happen to disable the first (by index) CRTC, we end up changing the assigned FIFO of the second CRTC without disabling and reenabling the pixelvalve which ends up in a stall and eventually a VBLANK timeout.
Quoted 7 lines
In order to fix this, we can create a special value for our assigned channel to mark it as disabled, and if our CRTC already had an assigned channel in its previous state, we keep on using it.
Fixes 87ebcd42fb7b ("drm/vc4: crtc: Assign output to channel automatically")Signed-off-by Maxime Ripard <[email protected]>Tested-by Dave Stevenson <[email protected]>
I retested too and had triple output (HDMI-0, HDMI-1, and DPI) working happily! Switching around resolutions on the HDMI outputs was working fine. DPI was an Adafruit Kippah and 800x480 LCD, so no options on resolution.
We may finally have this muxing nailed.
Dave
Quoted 96 lines
---
Changes from v1:
- Split away the crtc state reset refactoring
- Fixed the checkpatch warnings--- drivers/gpu/drm/vc4/vc4_crtc.c | 1 + drivers/gpu/drm/vc4/vc4_drv.h | 2 ++ drivers/gpu/drm/vc4/vc4_kms.c | 22 ++++++++++++++++------ 3 files changed, 19 insertions(+), 6 deletions(-)drivers/gpu/drm/vc4/vc4_crtc.c +1
-0@@ -863,6 +863,7 @@ void vc4_crtc_reset(struct drm_crtc *crtc)return ; } + vc4_crtc_state->assigned_channel =VC4_HVS_CHANNEL_DISABLED ;__drm_atomic_helper_crtc_reset (crtc, &vc4_crtc_state->base); }drivers/gpu/drm/vc4/vc4_drv.h +2
-0@@ -532,6 +532,8 @@ struct vc4_crtc_state { } margins; }; +#define VC4_HVS_CHANNEL_DISABLED ((unsigned int)-1) +static inline struct vc4_crtc_state *to_vc4_crtc_state (struct drm_crtc_state *crtc_state) {drivers/gpu/drm/vc4/vc4_kms.c +16
-7@@ -616,7 +616,7 @@ static int vc4_atomic_check(struct drm_device *dev, struct drm_atomic_state *state) { unsigned long unassigned_channels = GENMASK(NUM_CHANNELS - 1, 0); -struct drm_crtc_state *crtc_state; +struct drm_crtc_state *old_crtc_state, *new_crtc_state;struct drm_crtc *crtc;int i, ret;@@ -629,6 +629,8 @@ vc4_atomic_check(struct drm_device *dev, struct drm_atomic_state *state)* modified. */ list_for_each_entry (crtc, &dev->mode_config.crtc_list, head) { +struct drm_crtc_state *crtc_state; +if (!crtc->state->enable)continue ;@@ -637,15 +639,23 @@ vc4_atomic_check(struct drm_device *dev, struct drm_atomic_state *state)return PTR_ERR (crtc_state); } -for_each_new_crtc_in_state (state, crtc, crtc_state, i) { -struct vc4_crtc_state *vc4_crtc_state = -to_vc4_crtc_state (crtc_state); +for_each_oldnew_crtc_in_state (state, crtc, old_crtc_state, new_crtc_state, i) { +struct vc4_crtc_state *new_vc4_crtc_state = +to_vc4_crtc_state (new_crtc_state);struct vc4_crtc *vc4_crtc =to_vc4_crtc (crtc);unsigned int matching_channels; -if (!crtc_state->enable) +if (old_crtc_state->enable && !new_crtc_state->enable) + new_vc4_crtc_state->assigned_channel =VC4_HVS_CHANNEL_DISABLED ; + +if (!new_crtc_state->enable)continue ; +if (new_vc4_crtc_state->assigned_channel !=VC4_HVS_CHANNEL_DISABLED ) { + unassigned_channels &= ~BIT (new_vc4_crtc_state->assigned_channel); +continue ; + } +/* * The problem we have to solve here is that we have * up to 7 encoders, connected to up to 6 CRTCs. @@ -674,7 +684,7 @@ vc4_atomic_check(struct drm_device *dev, struct drm_atomic_state *state)if (matching_channels) {unsigned int channel =ffs (matching_channels) -1 ; - vc4_crtc_state->assigned_channel = channel; + new_vc4_crtc_state->assigned_channel = channel; unassigned_channels &= ~BIT (channel); }else {return -EINVAL ; --
Quoted 2 lines
2.26.2
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi Maxime
Quoted 5 lines · Maxime Ripard
The current CRTC state reset hook in vc4 allocates a
vc4_crtc_statestructure as adrm_crtc_state, and relies on the fact thatvc4_crtc_stateembedsdrm_crtc_stateas its first member, and therefore can be safely casted.
s/casted/cast
Quoted 6 lines
However, this is pretty fragile especially since there's no check for this in place, and we're going to need to access
vc4_crtc_statemember at reset so this looks like a good occasion to make it more robust.Signed-off-by Maxime Ripard <[email protected]>Tested-by Dave Stevenson <[email protected]>
Based on the issue I perceived with the previous patch, I'm happy. I haven't thought about how the framework handles losing the state, but that's not the driver's problem.
There is still an implicit assumption that drm_crtc_state is the first member from the implementation of to_vc4_crtc_state in vc4_drv.h. To make it even more robust that could be a container_of instead. I haven't checked for any other places that make the assumption though.
Quoted 35 lines
---
Changes from v1:
- new patch--- drivers/gpu/drm/vc4/vc4_crtc.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)drivers/gpu/drm/vc4/vc4_crtc.c +10
-4@@ -852,11 +852,18 @@ void vc4_crtc_destroy_state(struct drm_crtc *crtc,void vc4_crtc_reset (struct drm_crtc *crtc) { +struct vc4_crtc_state *vc4_crtc_state; +if (crtc->state)vc4_crtc_destroy_state (crtc, crtc->state); - crtc->state =kzalloc (sizeof (struct vc4_crtc_state ),GFP_KERNEL ); -if (crtc->state) -__drm_atomic_helper_crtc_reset (crtc, crtc->state); + + vc4_crtc_state =kzalloc (sizeof (*vc4_crtc_state),GFP_KERNEL ); +if (!vc4_crtc_state) { + crtc->state =NULL ; +return ; + } + +__drm_atomic_helper_crtc_reset (crtc, &vc4_crtc_state->base); }static const struct drm_crtc_funcs vc4_crtc_funcs = { --
Quoted 2 lines
2.26.2
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 14 lines · Dave Stevenson
Hi Maxime
Quoted 5 lines · Maxime Ripard
The current CRTC state reset hook in vc4 allocates a
vc4_crtc_statestructure as adrm_crtc_state, and relies on the fact thatvc4_crtc_stateembedsdrm_crtc_stateas its first member, and therefore can be safely casted.s/casted/cast
Quoted 3 lines
However, this is pretty fragile especially since there's no check for this in place, and we're going to need to access
vc4_crtc_statemember at reset so this looks like a good occasion to make it more robust.
Also your next atomic_check will probably look at this, most definitely in the memcpy to take over the old state. So yeah KASAN should complain if you get this wrong :-)
Probably want a Fixes: line for this too.
-Daniel
Quoted 56 lines
Quoted 3 lines
Signed-off-by Maxime Ripard <[email protected]>Tested-by Dave Stevenson <[email protected]>Based on the issue I perceived with the previous patch, I'm happy. I haven't thought about how the framework handles losing the state, but that's not the driver's problem.
There is still an implicit assumption that
drm_crtc_stateis the first member from the implementation ofto_vc4_crtc_stateinvc4_drv.h. To make it even more robust that could be acontainer_ofinstead. I haven't checked for any other places that make the assumption though.Reviewed-by Dave Stevenson <[email protected]>Quoted 35 lines
---
Changes from v1:
- new patch--- drivers/gpu/drm/vc4/vc4_crtc.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)drivers/gpu/drm/vc4/vc4_crtc.c +10
-4@@ -852,11 +852,18 @@ void vc4_crtc_destroy_state(struct drm_crtc *crtc,void vc4_crtc_reset (struct drm_crtc *crtc) { +struct vc4_crtc_state *vc4_crtc_state; +if (crtc->state)vc4_crtc_destroy_state (crtc, crtc->state); - crtc->state =kzalloc (sizeof (struct vc4_crtc_state ),GFP_KERNEL ); -if (crtc->state) -__drm_atomic_helper_crtc_reset (crtc, crtc->state); + + vc4_crtc_state =kzalloc (sizeof (*vc4_crtc_state),GFP_KERNEL ); +if (!vc4_crtc_state) { + crtc->state =NULL ; +return ; + } + +__drm_atomic_helper_crtc_reset (crtc, &vc4_crtc_state->base); }static const struct drm_crtc_funcs vc4_crtc_funcs = { --Quoted 2 lines
2.26.2
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi Dave,
Quoted 18 lines · Dave Stevenson
Hi Maxime
Quoted 5 lines · Maxime Ripard
The current CRTC state reset hook in vc4 allocates a
vc4_crtc_statestructure as adrm_crtc_state, and relies on the fact thatvc4_crtc_stateembedsdrm_crtc_stateas its first member, and therefore can be safely casted.s/casted/cast
Quoted 6 lines
However, this is pretty fragile especially since there's no check for this in place, and we're going to need to access
vc4_crtc_statemember at reset so this looks like a good occasion to make it more robust.Signed-off-by Maxime Ripard <[email protected]>Tested-by Dave Stevenson <[email protected]>
Quoted 8 lines
Based on the issue I perceived with the previous patch, I'm happy. I haven't thought about how the framework handles losing the state, but that's not the driver's problem.
There is still an implicit assumption that
drm_crtc_stateis the first member from the implementation ofto_vc4_crtc_stateinvc4_drv.h. To make it even more robust that could be acontainer_ofinstead. I haven't checked for any other places that make the assumption though.
Good catch, I'll send another patch to fix it
Quoted 1 line
Reviewed-by Dave Stevenson <[email protected]>
Does it apply to the second patch as well?
Thanks!
Maxime
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Dave Stevenson
maintainerQuoted 31 lines · Maxime Ripard
Hi Dave,
Quoted 18 lines · Dave Stevenson
Hi Maxime
Quoted 5 lines · Maxime Ripard
The current CRTC state reset hook in vc4 allocates a
vc4_crtc_statestructure as adrm_crtc_state, and relies on the fact thatvc4_crtc_stateembedsdrm_crtc_stateas its first member, and therefore can be safely casted.s/casted/cast
Quoted 6 lines
However, this is pretty fragile especially since there's no check for this in place, and we're going to need to access
vc4_crtc_statemember at reset so this looks like a good occasion to make it more robust.Signed-off-by Maxime Ripard <[email protected]>Tested-by Dave Stevenson <[email protected]>Quoted 8 lines
Based on the issue I perceived with the previous patch, I'm happy. I haven't thought about how the framework handles losing the state, but that's not the driver's problem.
There is still an implicit assumption that
drm_crtc_stateis the first member from the implementation ofto_vc4_crtc_stateinvc4_drv.h. To make it even more robust that could be acontainer_ofinstead. I haven't checked for any other places that make the assumption though.
Quoted 5 lines
Good catch, I'll send another patch to fix it
Quoted 1 line
Reviewed-by Dave Stevenson <[email protected]>Does it apply to the second patch as well?
No. I got another interrupt before I'd refreshed my memory over what the second patch was doing and responding to it. I'll do that now (I don't think it changed much from v1)
Dave.
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi,
Quoted 22 lines · Dave Stevenson
Hi Maxime
Quoted 5 lines · Maxime Ripard
The current CRTC state reset hook in vc4 allocates a
vc4_crtc_statestructure as adrm_crtc_state, and relies on the fact thatvc4_crtc_stateembedsdrm_crtc_stateas its first member, and therefore can be safely casted.s/casted/cast
Quoted 6 lines
However, this is pretty fragile especially since there's no check for this in place, and we're going to need to access
vc4_crtc_statemember at reset so this looks like a good occasion to make it more robust.Signed-off-by Maxime Ripard <[email protected]>Tested-by Dave Stevenson <[email protected]>Based on the issue I perceived with the previous patch, I'm happy. I haven't thought about how the framework handles losing the state, but that's not the driver's problem.
Quoted 6 lines
There is still an implicit assumption that
drm_crtc_stateis the first member from the implementation ofto_vc4_crtc_stateinvc4_drv.h. To make it even more robust that could be acontainer_ofinstead. I haven't checked for any other places that make the assumption though.Reviewed-by Dave Stevenson <[email protected]>
Applied 1 and 2, with the typo fixed (and the fixes tag suggested by Daniel)
Maxime
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel