From: Jani Nikula <jani.nikula@linux.intel.com>
To: imre.deak@intel.com
Cc: intel-gfx@lists.freedesktop.org,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
Date: Fri, 16 Dec 2022 18:49:54 +0200 [thread overview]
Message-ID: <87zgbnthsd.fsf@intel.com> (raw)
In-Reply-To: <Y5yd5PvWb2fl66/s@ideak-desk.fi.intel.com>
On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
> On Fri, Dec 16, 2022 at 06:10:39PM +0200, Jani Nikula wrote:
>> On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
>> > On Wed, Dec 14, 2022 at 04:41:42PM -0500, Lyude Paul wrote:
>> >> For the whole series:
>> >>
>> >> Reviewed-by: Lyude Paul <lyude@redhat.com>
>> >
>> > Thanks for the review, pushed it to drm-misc-next.
>>
>> Hmm, with the drm-misc *not* cherry-picking patches from drm-misc-next
>> to drm-misc-fixes, these will only get backported to stable kernels
>> after they hit Linus' tree in the next (as opposed to current) merge
>> window after a full development cycle. Wonder if they should be
>> expedited.
>
> Ok, it should've been pushed to -fixes then, will do that next time.
> Yes, I think sending them already before the next merge window would be
> good.
Cc: drm-misc maintainers, I think this is for you to figure out.
BR,
Jani.
>
>>
>> BR,
>> Jani.
>>
>> >
>> >> Thanks!
>> >>
>> >> On Wed, 2022-12-14 at 20:42 +0200, Imre Deak wrote:
>> >> > If the sink gets disconnected during receiving a multi-packet DP MST AUX
>> >> > down-reply/up-request sideband message, the state keeping track of which
>> >> > packets have been received already is not reset. This results in a failed
>> >> > sanity check for the subsequent message packet received after a sink is
>> >> > reconnected (due to the pending message not yet completed with an
>> >> > end-of-message-transfer packet), indicated by the
>> >> >
>> >> > "sideband msg set header failed"
>> >> >
>> >> > error.
>> >> >
>> >> > Fix the above by resetting the up/down message reception state after a
>> >> > disconnect event.
>> >> >
>> >> > Cc: Lyude Paul <lyude@redhat.com>
>> >> > Cc: <stable@vger.kernel.org> # v3.17+
>> >> > Signed-off-by: Imre Deak <imre.deak@intel.com>
>> >> > ---
>> >> > drivers/gpu/drm/display/drm_dp_mst_topology.c | 3 +++
>> >> > 1 file changed, 3 insertions(+)
>> >> >
>> >> > diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > index 51a46689cda70..90819fff2c9ba 100644
>> >> > --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > @@ -3641,6 +3641,9 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
>> >> > drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
>> >> > ret = 0;
>> >> > mgr->payload_id_table_cleared = false;
>> >> > +
>> >> > + memset(&mgr->down_rep_recv, 0, sizeof(mgr->down_rep_recv));
>> >> > + memset(&mgr->up_req_recv, 0, sizeof(mgr->up_req_recv));
>> >> > }
>> >> >
>> >> > out_unlock:
>> >>
>> >> --
>> >> Cheers,
>> >> Lyude Paul (she/her)
>> >> Software Engineer at Red Hat
>> >>
>>
>> --
>> Jani Nikula, Intel Open Source Graphics Center
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: imre.deak@intel.com
Cc: Lyude Paul <lyude@redhat.com>,
intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
Date: Fri, 16 Dec 2022 18:49:54 +0200 [thread overview]
Message-ID: <87zgbnthsd.fsf@intel.com> (raw)
In-Reply-To: <Y5yd5PvWb2fl66/s@ideak-desk.fi.intel.com>
On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
> On Fri, Dec 16, 2022 at 06:10:39PM +0200, Jani Nikula wrote:
>> On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
>> > On Wed, Dec 14, 2022 at 04:41:42PM -0500, Lyude Paul wrote:
>> >> For the whole series:
>> >>
>> >> Reviewed-by: Lyude Paul <lyude@redhat.com>
>> >
>> > Thanks for the review, pushed it to drm-misc-next.
>>
>> Hmm, with the drm-misc *not* cherry-picking patches from drm-misc-next
>> to drm-misc-fixes, these will only get backported to stable kernels
>> after they hit Linus' tree in the next (as opposed to current) merge
>> window after a full development cycle. Wonder if they should be
>> expedited.
>
> Ok, it should've been pushed to -fixes then, will do that next time.
> Yes, I think sending them already before the next merge window would be
> good.
Cc: drm-misc maintainers, I think this is for you to figure out.
BR,
Jani.
>
>>
>> BR,
>> Jani.
>>
>> >
>> >> Thanks!
>> >>
>> >> On Wed, 2022-12-14 at 20:42 +0200, Imre Deak wrote:
>> >> > If the sink gets disconnected during receiving a multi-packet DP MST AUX
>> >> > down-reply/up-request sideband message, the state keeping track of which
>> >> > packets have been received already is not reset. This results in a failed
>> >> > sanity check for the subsequent message packet received after a sink is
>> >> > reconnected (due to the pending message not yet completed with an
>> >> > end-of-message-transfer packet), indicated by the
>> >> >
>> >> > "sideband msg set header failed"
>> >> >
>> >> > error.
>> >> >
>> >> > Fix the above by resetting the up/down message reception state after a
>> >> > disconnect event.
>> >> >
>> >> > Cc: Lyude Paul <lyude@redhat.com>
>> >> > Cc: <stable@vger.kernel.org> # v3.17+
>> >> > Signed-off-by: Imre Deak <imre.deak@intel.com>
>> >> > ---
>> >> > drivers/gpu/drm/display/drm_dp_mst_topology.c | 3 +++
>> >> > 1 file changed, 3 insertions(+)
>> >> >
>> >> > diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > index 51a46689cda70..90819fff2c9ba 100644
>> >> > --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > @@ -3641,6 +3641,9 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
>> >> > drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
>> >> > ret = 0;
>> >> > mgr->payload_id_table_cleared = false;
>> >> > +
>> >> > + memset(&mgr->down_rep_recv, 0, sizeof(mgr->down_rep_recv));
>> >> > + memset(&mgr->up_req_recv, 0, sizeof(mgr->up_req_recv));
>> >> > }
>> >> >
>> >> > out_unlock:
>> >>
>> >> --
>> >> Cheers,
>> >> Lyude Paul (she/her)
>> >> Software Engineer at Red Hat
>> >>
>>
>> --
>> Jani Nikula, Intel Open Source Graphics Center
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: imre.deak@intel.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
Date: Fri, 16 Dec 2022 18:49:54 +0200 [thread overview]
Message-ID: <87zgbnthsd.fsf@intel.com> (raw)
In-Reply-To: <Y5yd5PvWb2fl66/s@ideak-desk.fi.intel.com>
On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
> On Fri, Dec 16, 2022 at 06:10:39PM +0200, Jani Nikula wrote:
>> On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
>> > On Wed, Dec 14, 2022 at 04:41:42PM -0500, Lyude Paul wrote:
>> >> For the whole series:
>> >>
>> >> Reviewed-by: Lyude Paul <lyude@redhat.com>
>> >
>> > Thanks for the review, pushed it to drm-misc-next.
>>
>> Hmm, with the drm-misc *not* cherry-picking patches from drm-misc-next
>> to drm-misc-fixes, these will only get backported to stable kernels
>> after they hit Linus' tree in the next (as opposed to current) merge
>> window after a full development cycle. Wonder if they should be
>> expedited.
>
> Ok, it should've been pushed to -fixes then, will do that next time.
> Yes, I think sending them already before the next merge window would be
> good.
Cc: drm-misc maintainers, I think this is for you to figure out.
BR,
Jani.
>
>>
>> BR,
>> Jani.
>>
>> >
>> >> Thanks!
>> >>
>> >> On Wed, 2022-12-14 at 20:42 +0200, Imre Deak wrote:
>> >> > If the sink gets disconnected during receiving a multi-packet DP MST AUX
>> >> > down-reply/up-request sideband message, the state keeping track of which
>> >> > packets have been received already is not reset. This results in a failed
>> >> > sanity check for the subsequent message packet received after a sink is
>> >> > reconnected (due to the pending message not yet completed with an
>> >> > end-of-message-transfer packet), indicated by the
>> >> >
>> >> > "sideband msg set header failed"
>> >> >
>> >> > error.
>> >> >
>> >> > Fix the above by resetting the up/down message reception state after a
>> >> > disconnect event.
>> >> >
>> >> > Cc: Lyude Paul <lyude@redhat.com>
>> >> > Cc: <stable@vger.kernel.org> # v3.17+
>> >> > Signed-off-by: Imre Deak <imre.deak@intel.com>
>> >> > ---
>> >> > drivers/gpu/drm/display/drm_dp_mst_topology.c | 3 +++
>> >> > 1 file changed, 3 insertions(+)
>> >> >
>> >> > diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > index 51a46689cda70..90819fff2c9ba 100644
>> >> > --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > @@ -3641,6 +3641,9 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
>> >> > drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
>> >> > ret = 0;
>> >> > mgr->payload_id_table_cleared = false;
>> >> > +
>> >> > + memset(&mgr->down_rep_recv, 0, sizeof(mgr->down_rep_recv));
>> >> > + memset(&mgr->up_req_recv, 0, sizeof(mgr->up_req_recv));
>> >> > }
>> >> >
>> >> > out_unlock:
>> >>
>> >> --
>> >> Cheers,
>> >> Lyude Paul (she/her)
>> >> Software Engineer at Red Hat
>> >>
>>
>> --
>> Jani Nikula, Intel Open Source Graphics Center
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-12-16 16:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 18:42 [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Imre Deak
2022-12-14 18:42 ` Imre Deak
2022-12-14 18:42 ` Imre Deak
2022-12-14 18:42 ` [Intel-gfx] [PATCH 2/3] drm/display/dp_mst: Fix down message handling after a packet reception error Imre Deak
2022-12-14 18:42 ` Imre Deak
2022-12-14 18:42 ` Imre Deak
2022-12-14 18:42 ` [Intel-gfx] [PATCH 3/3] drm/display/dp_mst: Fix payload addition on a disconnected sink Imre Deak
2022-12-14 18:42 ` Imre Deak
2022-12-14 18:42 ` Imre Deak
2022-12-14 20:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Patchwork
2022-12-14 21:41 ` [Intel-gfx] [PATCH 1/3] " Lyude Paul
2022-12-14 21:41 ` Lyude Paul
2022-12-14 21:41 ` Lyude Paul
2022-12-16 15:10 ` [Intel-gfx] " Imre Deak
2022-12-16 15:10 ` Imre Deak
2022-12-16 15:10 ` Imre Deak
2022-12-16 16:10 ` [Intel-gfx] " Jani Nikula
2022-12-16 16:10 ` Jani Nikula
2022-12-16 16:33 ` Imre Deak
2022-12-16 16:33 ` Imre Deak
2022-12-16 16:49 ` Jani Nikula [this message]
2022-12-16 16:49 ` Jani Nikula
2022-12-16 16:49 ` Jani Nikula
2022-12-16 8:06 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgbnthsd.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mripard@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.