Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1619759yba; Thu, 25 Apr 2019 02:57:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqz3JHkzbq/qWBD83QN++uTHyVd3zta9Y/FuhhcloSoa/XvnpFyM4aYU6k4K/9dxHb0fgj15 X-Received: by 2002:a17:902:61:: with SMTP id 88mr37709379pla.166.1556186244168; Thu, 25 Apr 2019 02:57:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556186244; cv=none; d=google.com; s=arc-20160816; b=MJkwj7abcsvlM5p8QVOdOkQqBS0xI7IvIZCoD3ytNpDqC3pxdJFK4TBjHLlN1tiD3y 1q4jLWn9tQWEKHWMgRO8WLRFiMPaIUyseDYPGdpc/DIra8cyoNbRBXaRZGQllI8xzor0 QpCYLcV5D6vrgkJHkOArEWloBLcT2L6lD4kuN7DLFx/nEezjotQ1bvtARHWoox5Ou5d2 FRsOTtI+8P0tIoLqVh7+/BEkvzTTJUxZYkB4WnSrt4+plhHNK+9z3Dh1+zt4c4BnAWEU UJyla1pZRUPRf888nQPu0KV5Zq7r9HbMzar9CuuPMU3wFI4q7UFcHGIKbt9q14ikqDLp poyA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=HhQ7jYzghgIqKgaAgfN76700l4OvgCKkOAd2ol9E0lU=; b=DKtCTAGX39iO0+lptSKhsp4MPHNtcS1CkbKuBbr9lpeNS1c++coXdJNPs7pms+BlKP CY+x5mPV84J2p7k6wDMFeuwtA4UuHAw6kaheyyzt/ixWDM6XYQvAiFWTJy13MTbpPyES pcqItxREQ4M+nWFAgKkLhxJmWPK/Hf49k12rowLtlF5n6O2yF8WADjFMCMvhHUohSnMD pjQRGTkD/8jnaImnlf8G4C4yOGrguA56zkUAqoFyHIzNtx2aQX4bNkk/luCE4LYEA7DF 7cQQ8UvQ1OE3hd3DoPwD/dl63pdiBBxayAYLDSpVJ95BScKzn/yxbWOt9NlPb+940yfm jv6w== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=casper.20170209 header.b=HxlYlSpm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r63si2150914plb.157.2019.04.25.02.57.08; Thu, 25 Apr 2019 02:57:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=casper.20170209 header.b=HxlYlSpm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388662AbfDXSJC (ORCPT + 99 others); Wed, 24 Apr 2019 14:09:02 -0400 Received: from casper.infradead.org ([85.118.1.10]:48580 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725978AbfDXSJB (ORCPT ); Wed, 24 Apr 2019 14:09:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=HhQ7jYzghgIqKgaAgfN76700l4OvgCKkOAd2ol9E0lU=; b=HxlYlSpmH7r5MFlhylXWNgWOFx pTx99hWG4+DIyjCa/WBRRbokCmSxtYMlWfXUuPkuUJ9gwnUINs5JGuwXSvw5I44vVxOhC3iRHXp7u Z1iCmkBWtIT2gKRLi5h4nEle7u3PTMjbfGyLvqJN5qbXyxfVWEytpkuIFJTA4gifT2If8ap94O+jL 79F5TWQ5txbqkjlLKe2K9XoUn65IiQM/5h3WQEwNzFR4hmDj6K8oir9+tGEJgA3gSAqzncFpvuDi4 vNiU5/QL+zLJCyFogbpW8Qrn+N9Y0NNTz2nVw86kV0KgVe7VdAcLqmYW3u9Hsf1lU4MsZs8zz3+r6 BUPvEmxQ==; Received: from 177.17.136.231.dynamic.adsl.gvt.net.br ([177.17.136.231] helo=coco.lan) by casper.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1hJMKH-0001uS-M8; Wed, 24 Apr 2019 18:08:58 +0000 Date: Wed, 24 Apr 2019 15:08:52 -0300 From: Mauro Carvalho Chehab To: Changbin Du Cc: rjw@rjwysocki.net, Jonathan Corbet , Bjorn Helgaas , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, fenghua.yu@intel.com, linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org, linux-gpio@vger.kernel.org Subject: Re: [PATCH v5 08/23] Documentation: ACPI: move method-customizing.txt to firmware-guide/acpi and convert to reST Message-ID: <20190424150852.0e415da1@coco.lan> In-Reply-To: <20190424175306.25880-9-changbin.du@gmail.com> References: <20190424175306.25880-1-changbin.du@gmail.com> <20190424175306.25880-9-changbin.du@gmail.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Thu, 25 Apr 2019 01:52:51 +0800 Changbin Du escreveu: > This converts the plain text documentation to reStructuredText format and > add it to Sphinx TOC tree. No essential content change. > > Signed-off-by: Changbin Du Reviewed-by: Mauro Carvalho Chehab > --- > Documentation/acpi/method-customizing.txt | 73 --------------- > Documentation/firmware-guide/acpi/index.rst | 3 +- > .../acpi/method-customizing.rst | 89 +++++++++++++++++++ > 3 files changed, 91 insertions(+), 74 deletions(-) > delete mode 100644 Documentation/acpi/method-customizing.txt > create mode 100644 Documentation/firmware-guide/acpi/method-customizing.rst > > diff --git a/Documentation/acpi/method-customizing.txt b/Documentation/acpi/method-customizing.txt > deleted file mode 100644 > index 7235da975f23..000000000000 > --- a/Documentation/acpi/method-customizing.txt > +++ /dev/null > @@ -1,73 +0,0 @@ > -Linux ACPI Custom Control Method How To > -======================================= > - > -Written by Zhang Rui > - > - > -Linux supports customizing ACPI control methods at runtime. > - > -Users can use this to > -1. override an existing method which may not work correctly, > - or just for debugging purposes. > -2. insert a completely new method in order to create a missing > - method such as _OFF, _ON, _STA, _INI, etc. > -For these cases, it is far simpler to dynamically install a single > -control method rather than override the entire DSDT, because kernel > -rebuild/reboot is not needed and test result can be got in minutes. > - > -Note: Only ACPI METHOD can be overridden, any other object types like > - "Device", "OperationRegion", are not recognized. Methods > - declared inside scope operators are also not supported. > -Note: The same ACPI control method can be overridden for many times, > - and it's always the latest one that used by Linux/kernel. > -Note: To get the ACPI debug object output (Store (AAAA, Debug)), > - please run "echo 1 > /sys/module/acpi/parameters/aml_debug_output". > - > -1. override an existing method > - a) get the ACPI table via ACPI sysfs I/F. e.g. to get the DSDT, > - just run "cat /sys/firmware/acpi/tables/DSDT > /tmp/dsdt.dat" > - b) disassemble the table by running "iasl -d dsdt.dat". > - c) rewrite the ASL code of the method and save it in a new file, > - d) package the new file (psr.asl) to an ACPI table format. > - Here is an example of a customized \_SB._AC._PSR method, > - > - DefinitionBlock ("", "SSDT", 1, "", "", 0x20080715) > - { > - Method (\_SB_.AC._PSR, 0, NotSerialized) > - { > - Store ("In AC _PSR", Debug) > - Return (ACON) > - } > - } > - Note that the full pathname of the method in ACPI namespace > - should be used. > - e) assemble the file to generate the AML code of the method. > - e.g. "iasl -vw 6084 psr.asl" (psr.aml is generated as a result) > - If parameter "-vw 6084" is not supported by your iASL compiler, > - please try a newer version. > - f) mount debugfs by "mount -t debugfs none /sys/kernel/debug" > - g) override the old method via the debugfs by running > - "cat /tmp/psr.aml > /sys/kernel/debug/acpi/custom_method" > - > -2. insert a new method > - This is easier than overriding an existing method. > - We just need to create the ASL code of the method we want to > - insert and then follow the step c) ~ g) in section 1. > - > -3. undo your changes > - The "undo" operation is not supported for a new inserted method > - right now, i.e. we can not remove a method currently. > - For an overridden method, in order to undo your changes, please > - save a copy of the method original ASL code in step c) section 1, > - and redo step c) ~ g) to override the method with the original one. > - > - > -Note: We can use a kernel with multiple custom ACPI method running, > - But each individual write to debugfs can implement a SINGLE > - method override. i.e. if we want to insert/override multiple > - ACPI methods, we need to redo step c) ~ g) for multiple times. > - > -Note: Be aware that root can mis-use this driver to modify arbitrary > - memory and gain additional rights, if root's privileges got > - restricted (for example if root is not allowed to load additional > - modules after boot). > diff --git a/Documentation/firmware-guide/acpi/index.rst b/Documentation/firmware-guide/acpi/index.rst > index 61d67763851b..d1d069b26bbc 100644 > --- a/Documentation/firmware-guide/acpi/index.rst > +++ b/Documentation/firmware-guide/acpi/index.rst > @@ -10,5 +10,6 @@ ACPI Support > namespace > enumeration > osi > + method-customizing > DSD-properties-rules > - gpio-properties > + gpio-properties > \ No newline at end of file > diff --git a/Documentation/firmware-guide/acpi/method-customizing.rst b/Documentation/firmware-guide/acpi/method-customizing.rst > new file mode 100644 > index 000000000000..de3ebcaed4cf > --- /dev/null > +++ b/Documentation/firmware-guide/acpi/method-customizing.rst > @@ -0,0 +1,89 @@ > +.. SPDX-License-Identifier: GPL-2.0 > + > +======================================= > +Linux ACPI Custom Control Method How To > +======================================= > + > +:Author: Zhang Rui > + > + > +Linux supports customizing ACPI control methods at runtime. > + > +Users can use this to: > + > +1. override an existing method which may not work correctly, > + or just for debugging purposes. > +2. insert a completely new method in order to create a missing > + method such as _OFF, _ON, _STA, _INI, etc. > + > +For these cases, it is far simpler to dynamically install a single > +control method rather than override the entire DSDT, because kernel > +rebuild/reboot is not needed and test result can be got in minutes. > + > +.. note:: > + > + - Only ACPI METHOD can be overridden, any other object types like > + "Device", "OperationRegion", are not recognized. Methods > + declared inside scope operators are also not supported. > + > + - The same ACPI control method can be overridden for many times, > + and it's always the latest one that used by Linux/kernel. > + > + - To get the ACPI debug object output (Store (AAAA, Debug)), > + please run:: > + > + echo 1 > /sys/module/acpi/parameters/aml_debug_output > + > + > +1. override an existing method > +============================== > +a) get the ACPI table via ACPI sysfs I/F. e.g. to get the DSDT, > + just run "cat /sys/firmware/acpi/tables/DSDT > /tmp/dsdt.dat" > +b) disassemble the table by running "iasl -d dsdt.dat". > +c) rewrite the ASL code of the method and save it in a new file, > +d) package the new file (psr.asl) to an ACPI table format. > + Here is an example of a customized \_SB._AC._PSR method:: > + > + DefinitionBlock ("", "SSDT", 1, "", "", 0x20080715) > + { > + Method (\_SB_.AC._PSR, 0, NotSerialized) > + { > + Store ("In AC _PSR", Debug) > + Return (ACON) > + } > + } > + > + Note that the full pathname of the method in ACPI namespace > + should be used. > +e) assemble the file to generate the AML code of the method. > + e.g. "iasl -vw 6084 psr.asl" (psr.aml is generated as a result) > + If parameter "-vw 6084" is not supported by your iASL compiler, > + please try a newer version. > +f) mount debugfs by "mount -t debugfs none /sys/kernel/debug" > +g) override the old method via the debugfs by running > + "cat /tmp/psr.aml > /sys/kernel/debug/acpi/custom_method" > + > +2. insert a new method > +====================== > +This is easier than overriding an existing method. > +We just need to create the ASL code of the method we want to > +insert and then follow the step c) ~ g) in section 1. > + > +3. undo your changes > +==================== > +The "undo" operation is not supported for a new inserted method > +right now, i.e. we can not remove a method currently. > +For an overridden method, in order to undo your changes, please > +save a copy of the method original ASL code in step c) section 1, > +and redo step c) ~ g) to override the method with the original one. > + > + > +.. note:: We can use a kernel with multiple custom ACPI method running, > + But each individual write to debugfs can implement a SINGLE > + method override. i.e. if we want to insert/override multiple > + ACPI methods, we need to redo step c) ~ g) for multiple times. > + > +.. note:: Be aware that root can mis-use this driver to modify arbitrary > + memory and gain additional rights, if root's privileges got > + restricted (for example if root is not allowed to load additional > + modules after boot). Thanks, Mauro