Date: Sat, 06 Jul 2019 20:23:14 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 238037] [PATCH] Implement ig4 suspend/resume Message-ID: <bug-238037-227-aUHrU6ttaB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238037-227@https.bugs.freebsd.org/bugzilla/> References: <bug-238037-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238037 marc.priggemeyer@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marc.priggemeyer@gmail.com --- Comment #11 from marc.priggemeyer@gmail.com --- Since I did not yet have any success with suspend/resume on my laptop (I ha= ve to hard reset it because my display fails), I would like to point out this comment: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221777#c7 It's something I proposed in #221777 to correctly initialize the chipset (i= g4 to be exact). The Intel PCH datasheet is very specific on how to handle initialization sequences. I can imagine that you will need to check the IG4_REG_DEVIDLE_CTRL register for the idle state and clear the reset flag. It should basically be the same code snippet as in the referenced comment. Going one step further, it might even be useful to actively put the control= ler into idle state by setting the DEVICE_IDLE bit in the IG4_REG_DEVIDLE_CTRL register during suspend. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238037-227-aUHrU6ttaB>