linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 218198] Suspend/Resume Regression with attached ATA devices
Date: Sun, 03 Dec 2023 19:50:46 +0000	[thread overview]
Message-ID: <bug-218198-11613-4m8lH62VXx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218198-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218198

--- Comment #12 from Phillip Susi (phill@thesusis.net) ---
bugzilla-daemon@kernel.org writes:

> I guess you need to ask Intel.
>
> I assume that their firmware simply requires the DEVSLP signal to be
> asserted in order to enter lower CPU power states.

I would say it's the hardware that requires the ata link to be powered
down, not the firmware.  They seem to have decided that the way to get
the hardware to power down was to add a new state to ALPM instead of
using runtime pm to actually disable the port.  I would love to hear
from Intel why they went this route.

> If you just send a command to the device, if it not easy for HW logic
> to determine which state is in. It would need to read some registers
> or similar. Sounds way more complex than just having a logic gate.

I'm not quite sure what you are getting at here.  The point of the ATA
SLEEP command is to inform the device that it should power down
everything, including the SATA PHY, and only keep a simple logic gate
active that can detect the big and obvious RESET signal from the host.
It seems to accomplish the same goal as DEVSLP without requiring hacking
in another logic line somewhere that wasn't meant for that purpose.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-12-03 19:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  7:06 [Bug 218198] New: Suspend/Resume Regression with attached ATA devices bugzilla-daemon
2023-11-28  7:08 ` [Bug 218198] " bugzilla-daemon
2023-11-28  7:47 ` [Bug 218198] New: " Damien Le Moal
2023-11-28  7:47 ` [Bug 218198] " bugzilla-daemon
2023-11-28  8:24 ` bugzilla-daemon
2023-11-29 10:42   ` Niklas Cassel
2023-11-29 18:47     ` Phillip Susi
2023-11-30  8:48       ` Niklas Cassel
2023-11-28  8:24 ` bugzilla-daemon
2023-11-28  9:54 ` bugzilla-daemon
2023-11-28  9:55 ` bugzilla-daemon
2023-11-29 10:42 ` bugzilla-daemon
2023-11-29 18:10 ` bugzilla-daemon
2023-12-15 15:28   ` Niklas Cassel
2023-11-29 18:10 ` bugzilla-daemon
2023-11-29 18:11 ` bugzilla-daemon
2023-11-29 18:47 ` bugzilla-daemon
2023-11-30  8:49 ` bugzilla-daemon
2023-12-03 19:50   ` Phillip Susi
2023-12-03 19:50 ` bugzilla-daemon [this message]
2023-12-04  9:31 ` bugzilla-daemon
2023-12-05 21:37   ` Phillip Susi
2023-12-05 21:37 ` bugzilla-daemon
2023-12-06  6:51 ` bugzilla-daemon
2023-12-07 13:55   ` Phillip Susi
2023-12-07 13:55 ` bugzilla-daemon
2023-12-15 10:51 ` bugzilla-daemon
2023-12-15 15:28 ` bugzilla-daemon
2023-12-18 10:18 ` bugzilla-daemon
2023-12-18 10:29   ` Damien Le Moal
2023-12-18 10:20 ` bugzilla-daemon
2023-12-18 10:21 ` bugzilla-daemon
2023-12-18 10:21 ` bugzilla-daemon
2023-12-18 10:22 ` bugzilla-daemon
2023-12-18 10:22 ` bugzilla-daemon
2023-12-18 10:29 ` bugzilla-daemon
2023-12-18 10:36 ` bugzilla-daemon
2024-03-05 13:32 ` bugzilla-daemon

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=bug-218198-11613-4m8lH62VXx@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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).