xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: shankerd@codeaurora.org,
	xen-devel <xen-devel@lists.xensource.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
	Philip Elcan <pelcan@codeaurora.org>,
	Vikram Sethi <vikrams@codeaurora.org>,
	Wei Chen <wei.chen@linaro.org>
Subject: Re: [PATCH V8 3/3] arm/acpi: Add Server Base System Architecture UART support
Date: Thu, 9 Jun 2016 16:35:18 +0100	[thread overview]
Message-ID: <57598CB6.9050706@arm.com> (raw)
In-Reply-To: <57598A8F.4090901@codeaurora.org>



On 09/06/16 16:26, Shanker Donthineni wrote:
>>> diff --git a/xen/drivers/char/pl011.c b/xen/drivers/char/pl011.c
>>> index a2f929b..d70ec99 100644
>>> --- a/xen/drivers/char/pl011.c
>>> +++ b/xen/drivers/char/pl011.c
>>> @@ -41,6 +41,7 @@ static struct pl011 {
>>>       /* struct timer timer; */
>>>       /* unsigned int timeout_ms; */
>>>       /* bool_t probing, intr_works; */
>>> +    bool sbsa;  /* ARM SBSA generic interface */
>>>   } pl011_com = {0};
>>>
>>>   /* These parity settings can be ORed directly into the LCR. */
>>> @@ -50,6 +51,7 @@ static struct pl011 {
>>>   #define PARITY_MARK  (PEN|SPS)
>>>   #define PARITY_SPACE (PEN|EPS|SPS)
>>>
>>> +/* To compatible with SBSA v2.x document, all accesses should be
>>> 32-bit */
>>
>> The verb is missing. Also please add a full stop at the end of the
>> comment.
>>
>>>   #define pl011_read(uart, off) readl((uart)->regs + (off))
>>>   #define pl011_write(uart, off,val)      writel((val), (uart)->regs
>>> + (off))
>>>
>>
>> [...]
>>
> Sorry, I didn't understand what is [...]?

It used to show that I dropped some part of your mail in my reply.

>>> @@ -313,11 +323,15 @@ static int __init pl011_acpi_uart_init(const
>>> void *data)
>>>           return -EINVAL;
>>>       }
>>>
>>> +    if ( (spcr->interface_type == ACPI_DBG2_SBSA) ||
>>> +         (spcr->interface_type == ACPI_DBG2_SBSA_32) )
>>> +        sbsa = true;
>>
>> I thought I already mentioned this on a previous version:
>>
>> sbsa = (spcr->interface_type == ACPI_DBG2_SBSA || ...);
>>
> You want me change to
>
> sbsa = (spcr->interface_type == ACPI_DBG2_SBSA || spcr->interface_type
> == ACPI_DBG2_SBSA_32)
>
> right?

Yes please.

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-06-09 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 13:28 [PATCH V8 1/3] drivers/pl011: Don't configure baudrate Shanker Donthineni
2016-06-08 13:28 ` [PATCH V8 2/3] drivers/pl011: Use combination of UARTRIS and UARTMSC instead of UARTMIS Shanker Donthineni
2016-06-09 10:15   ` Julien Grall
2016-06-09 15:27     ` Shanker Donthineni
2016-06-08 13:28 ` [PATCH V8 3/3] arm/acpi: Add Server Base System Architecture UART support Shanker Donthineni
2016-06-09 10:19   ` Julien Grall
2016-06-09 15:26     ` Shanker Donthineni
2016-06-09 15:35       ` Julien Grall [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=57598CB6.9050706@arm.com \
    --to=julien.grall@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=pelcan@codeaurora.org \
    --cc=shankerd@codeaurora.org \
    --cc=sstabellini@kernel.org \
    --cc=vikrams@codeaurora.org \
    --cc=wei.chen@linaro.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).