From: Robin Murphy <robin.murphy@arm.com>
To: Qian Cai <quic_qiancai@quicinc.com>, Bing Fan <hptsfb@gmail.com>,
gregkh@linuxfoundation.org, Bing Fan <tombinfan@tencent.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5] arm pl011 serial: support multi-irq request
Date: Mon, 26 Jul 2021 22:14:04 +0100 [thread overview]
Message-ID: <e98962f3-9232-4abf-ec27-a7524a9e786d@arm.com> (raw)
In-Reply-To: <290c01ec-173f-755f-788e-2a33a69586e8@quicinc.com>
On 2021-07-26 21:56, Qian Cai wrote:
>
>
> On 7/26/2021 4:36 PM, Robin Murphy wrote:
>> The important point you're missing, but which the KASAN dump does hint at, is
>> that that is a machine with SBSA generic UARTs booting via ACPI - I know it
>> doesn't do DT at all because I have one too. What matters there is that pl011
>> binds as a platform driver, *not* an amba driver.
>
> Thanks for pointing out, Robin. I just yet to see an ARM server booting from DT
> those days.
Unlikely in production datacentre/cloud environments, indeed, although
some of the mid-range kit like LX2160 does start to blur the line of
what might be considered "server", and that's one example which *does*
have full-featured DT support (even if it also aspires to ACPI...)
What I thought was worth clarifying for the general audience is that the
relevant aspects of "server" here should in fact still be possible to
reproduce on something like a Raspberry Pi or a tiny QEMU VM, if one can
figure out the ACPI runes :)
Thanks,
Robin.
next prev parent reply other threads:[~2021-07-26 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 1:38 [PATCH v5] arm pl011 serial: support multi-irq request Bing Fan
2021-07-23 16:47 ` Qian Cai
2021-07-26 7:17 ` Bing Fan
2021-07-26 16:39 ` Qian Cai
2021-07-26 20:36 ` Robin Murphy
2021-07-26 20:56 ` Qian Cai
2021-07-26 21:14 ` Robin Murphy [this message]
2021-07-27 2:57 ` Bing Fan
2021-08-12 14:31 ` Qian Cai
[not found] ` <67cd6c830e33491e99ea4d2480f4a89d@tencent.com>
[not found] ` <09918b566884413898f63b92ddd037a0@tencent.com>
2021-08-13 13:42 ` [Internet]Re: " Qian Cai
2021-08-13 15:01 ` gregkh
2021-08-13 15:09 ` Robin Murphy
2021-08-13 15:14 ` gregkh
2021-08-13 15:28 ` Qian Cai
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=e98962f3-9232-4abf-ec27-a7524a9e786d@arm.com \
--to=robin.murphy@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hptsfb@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=quic_qiancai@quicinc.com \
--cc=tombinfan@tencent.com \
/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).