From: Greg KH <gregkh@linuxfoundation.org>
To: Sanjay R Mehta <sanmehta@amd.com>
Cc: Sanjay R Mehta <Sanju.Mehta@amd.com>,
mika.westerberg@linux.intel.com, andreas.noever@gmail.com,
michael.jamet@intel.com, YehezkelShB@gmail.com,
linux-usb@vger.kernel.org, Sanath S <Sanath.S@amd.com>
Subject: Re: [PATCH RESEND] thunderbolt: Fix Thunderbolt 3 display flickering issue on 2nd hot plug onwards
Date: Wed, 12 Jul 2023 18:42:08 +0200 [thread overview]
Message-ID: <2023071235-steadier-fling-2446@gregkh> (raw)
In-Reply-To: <af96080c-5c86-fffb-74ac-3bdcf5d4e5cc@amd.com>
On Wed, Jul 12, 2023 at 11:33:58AM +0530, Sanjay R Mehta wrote:
>
>
> On 7/12/2023 11:23 AM, Greg KH wrote:
> > On Wed, Jul 12, 2023 at 12:32:26AM -0500, Sanjay R Mehta wrote:
> >> From: Sanjay R Mehta <sanju.mehta@amd.com>
> >>
> >> Previously, on unplug events, the TMU mode was disabled first
> >> followed by the Time Synchronization Handshake, irrespective of
> >> whether the tb_switch_tmu_rate_write() API was successful or not.
> >>
> >> However, this caused a problem with Thunderbolt 3 (TBT3)
> >> devices, as the TSPacketInterval bits were always enabled by default,
> >> leading the host router to assume that the device router's TMU was
> >> already enabled and preventing it from initiating the Time
> >> Synchronization Handshake. As a result, TBT3 monitors experienced
> >> display flickering from the second hot plug onwards.
> >>
> >> To address this issue, we have modified the code to only disable the
> >> Time Synchronization Handshake during TMU disable if the
> >> tb_switch_tmu_rate_write() function is successful. This ensures that
> >> the TBT3 devices function correctly and eliminates the display
> >> flickering issue.
> >>
> >> Signed-off-by: Sanjay R Mehta <sanju.mehta@amd.com>
> >> Signed-off-by: Sanath S <Sanath.S@amd.com>
> >> ---
> >> drivers/thunderbolt/tmu.c | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > Why is this a RESEND? What changed?
> >
> > And the ordering of the signed-off-by is incorrect.
> >
> Hi Greg, My Apologies, but am unable to comprehend what I should be
> doing here. Please guide me on this.
Please go and take the AMD kernel developer class/training/something and
work with internal developers to get this right before resending it
again.
thanks,
greg k-h
next prev parent reply other threads:[~2023-07-12 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 5:32 [PATCH RESEND] thunderbolt: Fix Thunderbolt 3 display flickering issue on 2nd hot plug onwards Sanjay R Mehta
2023-07-12 5:53 ` Greg KH
2023-07-12 6:03 ` Sanjay R Mehta
2023-07-12 16:42 ` Greg KH [this message]
2023-07-12 16:53 ` Sanjay R Mehta
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=2023071235-steadier-fling-2446@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Sanath.S@amd.com \
--cc=Sanju.Mehta@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=sanmehta@amd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox