mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Singh, Sandeep" <ssingh1@amd.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>,
	Sandeep Singh <Sandeep.Singh@amd.com>,
	mathias.nyman@intel.com, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	sanket.goswami@amd.com, Nehal-bakulchandra.Shah@amd.com
Cc: Shyam-sundar.S-k@amd.com
Subject: Re: [PATCH v2] usb: xhci: Workaround for S3 issue on AMD SNPS 3.0 xHC
Date: Wed, 28 Oct 2020 12:01:29 +0530	[thread overview]
Message-ID: <8ebe6707-5f83-58d3-b895-e193a191f48a@amd.com> (raw)
In-Reply-To: <ed3847f0-f219-547a-e887-cd0d48f77dda@linux.intel.com>


On 10/26/2020 8:16 PM, Mathias Nyman wrote:
> [CAUTION: External Email]
>
> On 23.10.2020 16.15, Sandeep Singh wrote:
>> From: Sandeep Singh <sandeep.singh@amd.com>
>>
>> On some platform of AMD, S3 fails with HCE and SRE errors. To fix this,
>> need to disable a bit which is enable in sparse controller.
>>
>> Signed-off-by: Sanket Goswami <Sanket.Goswami@amd.com>
>> Signed-off-by: Sandeep Singh <sandeep.singh@amd.com>
>> ---
>> Changes since v1:(https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.org%2Flkml%2F2020%2F10%2F23%2F368&amp;data=04%7C01%7CSandeep.Singh%40amd.com%7Ca8900bc99ca441507cc408d879bdc5e9%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637393203258053573%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=GM7TXOawh6nLZaX1ABZLlptYeyoUSMHnwhCxbY6zFZI%3D&amp;reserved=0)
>>        -> Add xhci.h changes
>>
> Added to queue.
> This looks like it should go to stable as well.

Thanks Mathias , please help to queue this up from 4.19+.

Regards

Sandeep

>
> -Mathias

      reply	other threads:[~2020-10-28 22:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 13:15 Sandeep Singh
2020-10-26 14:46 ` Mathias Nyman
2020-10-28  6:31   ` Singh, Sandeep [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=8ebe6707-5f83-58d3-b895-e193a191f48a@amd.com \
    --to=ssingh1@amd.com \
    --cc=Nehal-bakulchandra.Shah@amd.com \
    --cc=Sandeep.Singh@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=mathias.nyman@linux.intel.com \
    --cc=sanket.goswami@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
all inboxes | Powered by JetHome®