From: Greg KH <gregkh@linuxfoundation.org>
To: Rajat Khandelwal <rajat.khandelwal@intel.corp-partner.google.com>
Cc: heikki.krogerus@linux.intel.com, rajat.khandelwal@intel.com,
shawn.c.lee@intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Enter safe mode only when pins need to be reconfigured
Date: Wed, 24 Aug 2022 07:59:45 +0200 [thread overview]
Message-ID: <YwW+UUrn47MCbNIA@kroah.com> (raw)
In-Reply-To: <YwW+LI345ind56ks@kroah.com>
On Wed, Aug 24, 2022 at 07:59:08AM +0200, Greg KH wrote:
> On Tue, Aug 23, 2022 at 10:39:49PM +0530, Rajat Khandelwal wrote:
> > From: Lee Shawn C <shawn.c.lee@intel.com>
> >
> > There is no point to enter safe mode during DP/TBT configuration
> > if the DP/TBT was already configured in mux. This is because safe
> > mode is only applicable when there is a need to reconfigure the
> > pins in order to avoid damage within/to port partner.
> >
> > 1. if HPD interrupt arrives and DP mode was already configured,
> > safe mode is entered again which is not desired.
> > 2. in chrome systems, IOM/mux is already configured before OS
> > comes up. Thus, when driver is probed, it blindly enters safe
> > mode due to PD negotiations but only after gfx driver lowers
> > dp_phy_ownership, will the IOM complete safe mode and send
> > ack to PMC.
> > Since, that never happens, we see IPC timeout.
> >
> > Hence, allow safe mode only when pin reconfiguration is not
> > required, which makes sense.
> >
> > Signed-off-by: Rajat Khandelwal <rajat.khandelwal@intel.com>
> > Signed-off-by: Lee Shawn C <shawn.c.lee@intel.com>
>
> First off, don't use invalid "corp-partner.google.com" email addresses,
> you know that's not going to work and just bounce everywhere and there's
> no proof that this has any relationship to your intel address :(
Also the email verification fails, so it looks like you just spoofed
this message, which also makes it impossible for me to accept.
greg k-h
next prev parent reply other threads:[~2022-08-24 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 17:09 [PATCH] Enter safe mode only when pins need to be reconfigured Rajat Khandelwal
2022-08-24 5:59 ` Greg KH
2022-08-24 5:59 ` Greg KH [this message]
[not found] <20220822054019.GA32363@abhijeet-NUC11PAHi5>
2022-08-23 12:45 ` Khandelwal, Rajat
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=YwW+UUrn47MCbNIA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rajat.khandelwal@intel.com \
--cc=rajat.khandelwal@intel.corp-partner.google.com \
--cc=shawn.c.lee@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