public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 4/4] x86: tangier: Use spaces over TABs in ASL code
Date: Thu, 29 Aug 2019 17:04:21 +0300	[thread overview]
Message-ID: <20190829140421.2830-4-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20190829140421.2830-1-andriy.shevchenko@linux.intel.com>

For sake of consistency use spaces over TABs in ASL code.

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
 .../asm/arch-tangier/acpi/southcluster.asl    | 26 +++++++++----------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/arch/x86/include/asm/arch-tangier/acpi/southcluster.asl b/arch/x86/include/asm/arch-tangier/acpi/southcluster.asl
index f73a6b351c..c622783f44 100644
--- a/arch/x86/include/asm/arch-tangier/acpi/southcluster.asl
+++ b/arch/x86/include/asm/arch-tangier/acpi/southcluster.asl
@@ -382,19 +382,19 @@ Device (PCI0)
                 Name (RBUF, ResourceTemplate()
                 {
                     /*
-		     * Shadow registers in SRAM for PMIC:
-		     *   SRAM	PMIC register
-		     *   --------------------
-		     *   0x00-	Unknown
-		     *   0x03	THRMIRQ (0x04)
-		     *   0x04	BCUIRQ (0x05)
-		     *   0x05	ADCIRQ (0x06)
-		     *   0x06	CHGRIRQ0 (0x07)
-		     *   0x07	CHGRIRQ1 (0x08)
-		     *   0x08-	Unknown
-		     *   0x0a	PBSTATUS (0x27)
-		     *   0x0b-	Unknown
-		     */
+                     * Shadow registers in SRAM for PMIC:
+                     *   SRAM    PMIC register
+                     *   --------------------
+                     *   0x00-    Unknown
+                     *   0x03    THRMIRQ (0x04)
+                     *   0x04    BCUIRQ (0x05)
+                     *   0x05    ADCIRQ (0x06)
+                     *   0x06    CHGRIRQ0 (0x07)
+                     *   0x07    CHGRIRQ1 (0x08)
+                     *   0x08-    Unknown
+                     *   0x0a    PBSTATUS (0x27)
+                     *   0x0b-    Unknown
+                     */
                     Memory32Fixed(ReadWrite, 0xFFFFF610, 0x00000010)
                     Interrupt(ResourceConsumer, Level, ActiveHigh, Shared, ,, ) { 30 }
                     Interrupt(ResourceConsumer, Level, ActiveHigh, Shared, ,, ) { 23 }
-- 
2.23.0.rc1

  parent reply	other threads:[~2019-08-29 14:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 14:04 [U-Boot] [PATCH v1 1/4] x86: acpi: Annotate struct acpi_table_header with __packed Andy Shevchenko
2019-08-29 14:04 ` [U-Boot] [PATCH v1 2/4] x86: tangier: Reserve PCI ECAM in motherboard resources Andy Shevchenko
2019-09-10  8:14   ` Bin Meng
2019-09-10  8:21     ` Bin Meng
2019-08-29 14:04 ` [U-Boot] [PATCH v1 3/4] x86: tangier: Fix off-by-one error when preparing CSRT Andy Shevchenko
2019-09-10  8:14   ` Bin Meng
2019-09-10  8:21     ` Bin Meng
2019-08-29 14:04 ` Andy Shevchenko [this message]
2019-09-10  8:14   ` [U-Boot] [PATCH v1 4/4] x86: tangier: Use spaces over TABs in ASL code Bin Meng
2019-09-10  8:21     ` Bin Meng
2019-08-29 14:13 ` [U-Boot] [PATCH v1 1/4] x86: acpi: Annotate struct acpi_table_header with __packed Bin Meng
2019-08-29 14:28   ` Andy Shevchenko
2019-09-10  8:14     ` Bin Meng
2019-09-10  8:20       ` Bin Meng

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=20190829140421.2830-4-andriy.shevchenko@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=u-boot@lists.denx.de \
    /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