linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>
Cc: Matthias Kaehlcke <mka@chromium.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Felipe Balbi <balbi@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: dwc3: qcom: Defer dwc3-qcom probe if dwc3 isn't probed properly
Date: Wed, 27 Jul 2022 11:34:10 +0200	[thread overview]
Message-ID: <YuEGkkWV5s+q4hbf@kroah.com> (raw)
In-Reply-To: <b491bb80-aef5-f90b-4763-68fa5435b6d9@quicinc.com>

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Wed, Jul 27, 2022 at 02:56:06PM +0530, Krishna Kurapati PSSNV wrote:
> Hi Greg,
> 
>   As Mathias pointed out in another thread, no issue was seen so far on
> present QC targets as wakeup-source property was added recently and only for
> SC7180 and SC7280. We ran into some issues like wakeup from system suspend
> in host mode wasn't happening although we enabled wakeup-source in SC7180
> that eventually led us to this bug. But i tried to add debug prints to
> follow the code flow and see that the issue is present on SM8350 as well :
> *"supplier 88e9000.phy-wrapper not ready" *and deferring dwc3 probe.**This
> doesn't seem to be specific to SC7180.

I have no context here at all, sorry.

Remember, some of us get thousands of emails a week to handle and
review.  I don't know what other thread you are talking about, nor what
the issue here is at all, nor even what the patch is.

totally confused,

greg k-h

  parent reply	other threads:[~2022-07-27  9:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 14:55 [PATCH] usb: dwc3: qcom: Defer dwc3-qcom probe if dwc3 isn't probed properly Krishna Kurapati
2022-07-14 15:01 ` Greg Kroah-Hartman
2022-07-14 15:03   ` Krishna Kurapati PSSNV
2022-07-14 15:02 ` Greg Kroah-Hartman
2022-07-14 15:09   ` Krishna Kurapati PSSNV
2022-07-14 15:28     ` Greg Kroah-Hartman
2022-07-14 15:43       ` Krishna Kurapati PSSNV
2022-07-14 15:53   ` Matthias Kaehlcke
     [not found]     ` <b491bb80-aef5-f90b-4763-68fa5435b6d9@quicinc.com>
2022-07-27  9:34       ` Greg Kroah-Hartman [this message]
     [not found]     ` <9f8551be-4848-1f68-fe55-2c6108fa2f67@quicinc.com>
2022-07-27  9:55       ` Greg Kroah-Hartman
2022-07-14 15:56 ` Matthias Kaehlcke
2022-07-15  9:40 ` Pavan Kondeti
  -- strict thread matches above, loose matches on Subject: below --
2022-07-14 14:31 Krishna Kurapati

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=YuEGkkWV5s+q4hbf@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=agross@kernel.org \
    --cc=balbi@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=p.zabel@pengutronix.de \
    --cc=quic_kriskura@quicinc.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;
as well as URLs for NNTP newsgroup(s).