From owner-freebsd-current@freebsd.org Thu Aug 2 14:33:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FC461069024 for ; Thu, 2 Aug 2018 14:33:24 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE0C38B39F for ; Thu, 2 Aug 2018 14:33:23 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 01033ad4-9661-11e8-93fa-f3ebd9db2b94 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 01033ad4-9661-11e8-93fa-f3ebd9db2b94; Thu, 02 Aug 2018 14:33:21 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w72EXKEv040611; Thu, 2 Aug 2018 08:33:20 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533220400.1369.31.camel@freebsd.org> Subject: Re: acpiconf -s 3 does not call acpi sleep event handlers From: Ian Lepore To: Andriy Gapon , cem@freebsd.org, Johannes Lundberg Cc: freebsd-current Date: Thu, 02 Aug 2018 08:33:20 -0600 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 14:33:24 -0000 On Thu, 2018-08-02 at 08:20 +0300, Andriy Gapon wrote: > On 02/08/2018 01:17, Conrad Meyer wrote: > > > > I don't understand the concern.  There is only one listener to the > > event and it just invokes ReqSleepState, which is responsible for > > performing all suspend behavior.  The behavior is identical between > > lid close and acpiconf. > Unless someone is adding a new listener for that event. > Or if there is some listener in some proprietary or local module that's not part of base freebsd. The ability to support modules that didn't exist at the time the event was added is exactly the main benefit of a loose-runtime-binding scheme such as event notifications. -- Ian