Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: lukas@wunner.de
Cc: alex@shazbot.org, bhelgaas@google.com, jtornosm@redhat.com,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 1/2] PCI: Add D3cold as general reset method
Date: Thu, 14 May 2026 14:30:58 +0200	[thread overview]
Message-ID: <20260514123059.23829-1-jtornosm@redhat.com> (raw)
In-Reply-To: <agSNHLc_Sc_G-7vz@wunner.de>

Hello Lukas,

> Why fall back to D3hot, even though the name of the reset method
> suggests it uses D3cold?  If D3cold isn't supported, I'd just not
> expose the new reset method.
Ok, the next version will include D3cold only if supported.

> I'd call it "powercycle" for clarity but that's just my preferred
> bikeshed color.
I don't have any preference, although we can understand clearer what
it is. If there are consensus, I am ok with powercycle.

> So I'd just return -ENOTTY here in the !pci_pr3_present() case
> and I'd do that for probe == 0 as well.
Ok, I am going to wait for Alex Williamson opinion for the other cases
but I will do this as you say in the next version.

Thanks

Best regards
José Ignacio


  reply	other threads:[~2026-05-14 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 12:23 [PATCH v3 1/2] PCI: Add D3cold as general reset method Jose Ignacio Tornos Martinez
2026-05-13 12:23 ` [PATCH v3 2/2] PCI: Disable broken bus reset on Qualcomm devices Jose Ignacio Tornos Martinez
2026-05-13 13:31 ` [PATCH v3 1/2] PCI: Add D3cold as general reset method Alex Williamson
2026-05-14 12:23   ` Jose Ignacio Tornos Martinez
2026-05-13 14:39 ` Lukas Wunner
2026-05-14 12:30   ` Jose Ignacio Tornos Martinez [this message]
2026-05-14  5:07 ` sashiko-bot

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=20260514123059.23829-1-jtornosm@redhat.com \
    --to=jtornosm@redhat.com \
    --cc=alex@shazbot.org \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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