From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nate Lawson Subject: bm_rld semantics Date: Mon, 13 Oct 2003 23:00:26 -0700 (PDT) Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20031013225002.U29646@root.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Cc: paul.s.diefenbaugh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org List-Id: linux-acpi@vger.kernel.org I'm a little confused as to what BM_RLD actually does. Section 4.7.3.2.1 says only that setting BM_RLD enables bm activity to exit the C3 state. However, the last paragraph of 8.1.4 says that if BM_RLD is set after exiting C3, then it was exited at the request of a bus master. So in practice, do people implement one or both behaviors? If BM_RLD is set before C3 but zero after exiting it, does this mean it was exited due to an interrupt? It seems the Linux driver only uses BM_RLD as a control register. Thanks, Nate ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php