public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Ajay Agarwal <ajayagarwal@google.com>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Jingoo Han" <jingoohan1@gmail.com>,
	"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Bjorn Andersson" <quic_bjorande@quicinc.com>,
	"Sajid Dalvi" <sdalvi@google.com>
Subject: Re: [PATCH] Revert "PCI: dwc: Wait for link up only if link is started"
Date: Fri, 14 Jul 2023 10:55:29 +0200	[thread overview]
Message-ID: <ZLENgbMe4YVOINRQ@hovoldconsulting.com> (raw)
In-Reply-To: <ZK7m0hjQg7H5rANZ@google.com>

On Wed, Jul 12, 2023 at 11:15:54PM +0530, Ajay Agarwal wrote:
> On Tue, Jul 11, 2023 at 08:52:23AM +0200, Johan Hovold wrote:

> > All mainline drivers already start the link before that
> > wait-for-link-up, so the commit in question makes very little sense.
> > That's why I prefer reverting it, so as to not pollute the git logs
> > (e.g. for git blame) with misleading justifications.

> I am developing a PCIe driver which will not have the start_link
> callback defined. Instead, the link will be coming up much later based
> on some other trigger. So my driver will not attempt the LTSSM training
> on probe. So even if the probe is made asynchronous, it will still end
> up wasting 1 second of time.

Yeah, I had the suspicion that this was really motivated by some
out-of-tree driver, which as I'm sure you know, is not a concern for
mainline.

Vendor drivers do all sorts of crazy stuff and we don't carry code in
mainline for the sole benefit of such drivers that have not been
upstreamed (and likely never will be).

So again, I think this patch should just be reverted.

If you want to get something like this in, you can send a follow-on
patch describing your actual motivation and use case. But as it appears
to boil down to "I need this for my out-of-tree driver", I suspect such
a patch would still be rejected.

Johan

  reply	other threads:[~2023-07-14  8:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  8:26 [PATCH] Revert "PCI: dwc: Wait for link up only if link is started" Johan Hovold
2023-07-06 12:58 ` Manivannan Sadhasivam
2023-07-07 12:47   ` Johan Hovold
2023-07-10 16:21     ` Ajay Agarwal
2023-07-10 16:42       ` Ajay Agarwal
2023-07-10 17:06         ` Krzysztof Wilczyński
2023-07-11  6:52           ` Johan Hovold
2023-07-12 17:45             ` Ajay Agarwal
2023-07-14  8:55               ` Johan Hovold [this message]
2024-01-11 15:43                 ` Ajay Agarwal
2023-07-11  7:37       ` Manivannan Sadhasivam
2024-01-12 10:00         ` Ajay Agarwal
2024-01-19  7:40           ` Manivannan Sadhasivam
2023-07-25 20:05 ` Bjorn Helgaas
2023-07-26  8:30   ` Johan Hovold
2023-07-26 15:58     ` Bjorn Helgaas

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=ZLENgbMe4YVOINRQ@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=ajayagarwal@google.com \
    --cc=bhelgaas@google.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=quic_bjorande@quicinc.com \
    --cc=robh@kernel.org \
    --cc=sdalvi@google.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