From: Shanker Donthineni <shankerd@codeaurora.org>
To: Julien Grall <julien.grall@arm.com>,
xen-devel <xen-devel@lists.xensource.com>
Cc: Andre Przywara <andre.przywara@arm.com>,
Philip Elcan <pelcan@codeaurora.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Vikram Sethi <vikrams@codeaurora.org>
Subject: Re: [PATCH] arm/acpi: Add Server Base System Architecture UART support
Date: Fri, 27 May 2016 10:19:00 -0500 [thread overview]
Message-ID: <57486564.9040708@codeaurora.org> (raw)
In-Reply-To: <5748601B.9010902@arm.com>
I'll address your review comments in V2 patch.
On 05/27/2016 09:56 AM, Julien Grall wrote:
> Hello Shanker,
>
> On 27/05/16 15:01, Shanker Donthineni wrote:
>> On 05/27/2016 08:04 AM, Julien Grall wrote:
>>> On 27/05/16 01:28, Shanker Donthineni wrote:
>>>> The ARM Server Base System Architecture describes a generic UART
>>>> interface. It doesn't support clock control registers to set
>>>> baudrate. So, extend the driver probe() to handle SBSA interface
>>>> types and set the baudrate to 115200 for SBSA interfaces.
>>>
>>> I cannot find any mention of the baudrate in the SBSA. Where does it come from?
>>>
>> Yes, no where mentioned about the baudrate in SBSA document. I used 115200 based on the the Linux PL011 driver.
>
> Looking at the Linux code, it is a default when there is no valid configuration (which may not be suitable for any platform?).
>
> Whilst Linux userspace cares about the baudrate, Xen only use it to configure the hardware. Given that the UART should have been configured by the hardware-specific software, the proper value should be BAUD_AUTO.
>
> If you look at the code, pl011_init_preirq will read the baud rate when uart->baud == BAUD_AUTO but will never be used after.
>
>>> Also the driver is using registers which should not be touch for the SBSA UART (see appendix B in the SBSA ARM-DEN-0029 v3.0). So this need to be address to get a proper support.
>>>
>> Yes, I agree with you, Which registers it is touching other than baudrate control registers?
>
> Well, I only gave a quick look and noticed the difference between the SBSA and the pl011 (e.g CR, IFLS,...) . I am sure you can find out the rest of the registers by looking at the code (pl011-uart.h) and the spec.
>
> Regards,
>
--
Shanker Donthineni
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-27 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 0:28 [PATCH] arm/acpi: Add Server Base System Architecture UART support Shanker Donthineni
2016-05-27 13:04 ` Julien Grall
2016-05-27 14:01 ` Shanker Donthineni
2016-05-27 14:56 ` Julien Grall
2016-05-27 15:19 ` Shanker Donthineni [this message]
2016-05-30 6:54 ` Wei Chen
2016-05-30 12:00 ` Stefano Stabellini
2016-05-30 12:08 ` Julien Grall
2016-05-30 12:22 ` Julien Grall
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=57486564.9040708@codeaurora.org \
--to=shankerd@codeaurora.org \
--cc=andre.przywara@arm.com \
--cc=julien.grall@arm.com \
--cc=pelcan@codeaurora.org \
--cc=sstabellini@kernel.org \
--cc=vikrams@codeaurora.org \
--cc=xen-devel@lists.xensource.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).