public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: jeremy.linton@arm•com (Jeremy Linton)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 0/5] ACPI: parse the SPCR table
Date: Thu, 18 Feb 2016 15:15:44 -0600	[thread overview]
Message-ID: <56C63480.5020605@arm.com> (raw)
In-Reply-To: <1455559532-8305-1-git-send-email-aleksey.makarov@linaro.org>

On 02/15/2016 12:05 PM, Aleksey Makarov wrote:
> This patchset is based on the patchset by Leif Lindholm [1]
>
> 'ARM Server Base Boot Requirements' [2] mentions SPCR (Serial Port
> Console Redirection Table) [3] as a mandatory ACPI table that
> specifies the configuration of serial console.
>
> SPCR support is included in QEMU's ARM mach-virt since 2.4 release.
>
> Introduce a new function acpi_console_check().  At the uart port
> registration, this function checks if the ACPI SPCR table specifies
> its argument of type struct uart_port to be a console
> and if so calls add_preferred_console().
>
> Use SPCR to tell if SBSA serial driver should use 32-bit access to registers.
>
> To be able to access SPCR table each time any console is registered
> change __init to __ref for early_acpi_os_unmap_memory().
>
> The patchset should be applied to tty-next.
(trimming)

This works on the JunoR2 with a new enough firmware to have the SPCR table.

Tested-by: Jeremy Linton <jeremy.linton@arm•com>

      parent reply	other threads:[~2016-02-18 21:15 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 18:05 [PATCH v3 0/5] ACPI: parse the SPCR table Aleksey Makarov
2016-02-15 18:05 ` [PATCH v3 1/5] ACPI: change __init to __ref for early_acpi_os_unmap_memory() Aleksey Makarov
2016-02-17  2:44   ` Zheng, Lv
2016-02-17  2:51     ` Zheng, Lv
2016-02-17 13:08       ` Aleksey Makarov
2016-02-18  3:36         ` Zheng, Lv
2016-02-18 22:03           ` Peter Hurley
2016-02-19  2:58             ` Zheng, Lv
2016-02-19 11:02               ` Aleksey Makarov
2016-02-22  2:24                 ` Zheng, Lv
2016-02-22 14:58                   ` Aleksey Makarov
2016-02-23  0:19                     ` Zheng, Lv
2016-02-26  6:39                     ` Zheng, Lv
2016-02-26 10:33                       ` Aleksey Makarov
2016-02-19 10:42             ` Aleksey Makarov
2016-02-19 15:25               ` Peter Hurley
2016-02-19 17:20                 ` Christopher Covington
2016-02-22  5:37                   ` Peter Hurley
2016-02-22 14:43                   ` Aleksey Makarov
2016-02-22 14:35                 ` Aleksey Makarov
2016-03-01 15:24                   ` Peter Hurley
2016-02-15 18:05 ` [PATCH v3 2/5] ACPI: parse SPCR and enable matching console Aleksey Makarov
2016-02-18 22:19   ` Peter Hurley
2016-02-19 10:47     ` Aleksey Makarov
2016-02-19 16:13       ` Peter Hurley
2016-02-21  9:42   ` Yury Norov
2016-02-22 15:03     ` Aleksey Makarov
2016-02-15 18:05 ` [PATCH v3 3/5] ACPI: enable ACPI_SPCR_TABLE on ARM64 Aleksey Makarov
2016-02-15 18:05 ` [PATCH v3 4/5] ACPI: add definition of DBG2 subtypes Aleksey Makarov
2016-02-15 18:05 ` [PATCH v3 5/5] serial: pl011: use SPCR to setup 32-bit access Aleksey Makarov
2016-02-16 19:11 ` [PATCH v3 0/5] ACPI: parse the SPCR table Mark Salter
2016-02-17  2:36 ` Christopher Covington
2016-02-18 21:15 ` Jeremy Linton [this message]

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=56C63480.5020605@arm.com \
    --to=jeremy.linton@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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