Linux USB
 help / color / mirror / Atom feed
From: Sanjay R Mehta <sanmehta@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
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 22:23:29 +0530	[thread overview]
Message-ID: <5d2c8aa2-32d6-28f4-0fa7-1cf2556a71fe@amd.com> (raw)
In-Reply-To: <2023071235-steadier-fling-2446@gregkh>



On 7/12/2023 10:12 PM, Greg KH wrote:
> 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. I'll get this right and send the patch.
> thanks,
> 
> greg k-h

      reply	other threads:[~2023-07-12 16:53 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
2023-07-12 16:53       ` Sanjay R Mehta [this message]

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=5d2c8aa2-32d6-28f4-0fa7-1cf2556a71fe@amd.com \
    --to=sanmehta@amd.com \
    --cc=Sanath.S@amd.com \
    --cc=Sanju.Mehta@amd.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.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