linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peter@hurleysoftware.com (Peter Hurley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v13 2/5] uart: pl011: Introduce register accessor
Date: Wed, 28 Oct 2015 11:08:49 -0400	[thread overview]
Message-ID: <5630E501.7070506@hurleysoftware.com> (raw)
In-Reply-To: <5630E0F7.9080705@codeaurora.org>

On 10/28/2015 10:51 AM, Timur Tabi wrote:
> On 10/28/2015 09:22 AM, Peter Hurley wrote:
>> EARLYCON_DECLARE(zte, zte_early_console_setup);
>> OF_EARLYCON_DECLARE(zte, ".......", zte_early_console_setup);
>> EARLYCON_DECLARE(sbsa32, sbsa32_early_console_setup);
>> OF_EARLYCON_DECLARE(sbsa32, "arm,sbsa-uart", sbsa32_early_console_setup);
>>
>> The above assumes that the sbsa32 maintains the equivalence of
>> earlycon and console; ie., that
>>
>> / {
>>     chosen {
>>         stdout-path = &uart0;
>>     };
>>
>>     soc {
>>         uart0: serial at xxxxxx {
>>             compatible = "arm,sbsa-uart";
>>         };
>>     };
>> };
>>
>>
>> will start a sbsa32 earlycon and later replace that with
>> sbsa console.
> 
> I never really understood the device tree support for SBSA. The "S" stands for Server, and ARM Server systems are supposed to use ACPI. It's easy to add special cases via device tree, because of its flexibility.

Agreed.

> ACPI is much more difficult, and that's why I used the command-line approach.

Understood.

> Anyway, I found this alternate patch from Lief Lindholm that implements this idea better, although it needs work:
> 
> https://patches.linaro.org/53265/

Yeah, I saw those, but I'm waiting for v2 to review.

Regards,
Peter Hurley

  reply	other threads:[~2015-10-28 15:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1438328959-16177-1-git-send-email-jun.nie@linaro.org>
     [not found] ` <1438328959-16177-3-git-send-email-jun.nie@linaro.org>
2015-09-18 10:51   ` [PATCH v13 2/5] uart: pl011: Introduce register accessor Andre Przywara
2015-09-19  6:46     ` Jun Nie
2015-09-19 21:45       ` Andre Przywara
2015-10-22 23:36     ` Timur Tabi
2015-10-28 14:22       ` Peter Hurley
2015-10-28 14:51         ` Timur Tabi
2015-10-28 15:08           ` Peter Hurley [this message]
     [not found] ` <1438328959-16177-5-git-send-email-jun.nie@linaro.org>
2015-09-18 10:58   ` [PATCH v13 4/5] uart: pl011: Improve LCRH register access decision Andre Przywara
     [not found] ` <1438328959-16177-6-git-send-email-jun.nie@linaro.org>
2015-09-18 13:50   ` [PATCH v13 5/5] uart: pl011: Add support to ZTE ZX296702 uart Andre Przywara
2015-09-18 13:59     ` Russell King - ARM Linux
2015-09-19  6:47       ` Jun Nie
2015-09-19  6:54     ` Jun Nie
2015-10-23 21:54       ` Timur Tabi
2015-10-24  3:23         ` Jun Nie
2015-10-24  3:32           ` Timur Tabi
2015-10-26  1:27             ` Jun Nie
2015-10-27 13:31               ` Peter Hurley
2015-10-26  9:59             ` Andre Przywara
2015-10-26 12:46               ` Timur Tabi
2015-10-26 14:00                 ` Andre Przywara
2015-10-26 14:07                   ` Timur Tabi
2015-10-26 14:42                     ` Andre Przywara
2015-10-26 14:47                       ` Timur Tabi
2015-10-26 15:19                         ` Andre Przywara
2015-10-26 15:31                           ` Timur Tabi
2015-10-27 22:54                           ` Timur Tabi

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=5630E501.7070506@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).