From: jorge.ramirez-ortiz@linaro.org (Jorge Ramirez-Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [version 2] amba uarts - arm type uarts fifo size provided by device tree
Date: Wed, 04 Mar 2015 15:52:59 -0500 [thread overview]
Message-ID: <54F770AB.8090004@linaro.org> (raw)
In-Reply-To: <20150303165534.GB10239@leverpostej>
On 03/03/2015 11:55 AM, Mark Rutland wrote:
> On Wed, Feb 18, 2015 at 08:07:47PM +0000, Jorge Ramirez-Ortiz wrote:
>> [PATCH 1/2] Documentation: bindings: add optional fifo size property
>> [PATCH 2/2] drivers/tty: pl011: read fifo size from OF if present [updated]
>>
>> These patches aim at resolving an issue present on some of the amba pl011 uarts.
>>
>> They were developed for the Hisilicon Hi6220 SoC where the fifo size on the
>> uarts is 64 despite the amba revision having been set to 1.
> Are we certain that the FIFO length is the only difference between the
> HI6220 PL011 and a regular PL011?
I am trying to get an answer from the hardware designers.
>
> It may be worth adding a compatible string in addition, just in case.
>
> Mark.
next prev parent reply other threads:[~2015-03-04 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <amba uarts - arm type uarts fifo size provided by device tree>
2015-02-18 20:07 ` [version 2] amba uarts - arm type uarts fifo size provided by device tree Jorge Ramirez-Ortiz
2015-02-18 20:07 ` [PATCH 1/2] Documentation: bindings: add optional fifo size property to AMBA UARTs Jorge Ramirez-Ortiz
2015-02-18 21:17 ` Rob Herring
2015-02-18 20:07 ` [PATCH 2/2] drivers/tty: pl011: read fifo size from OF if present Jorge Ramirez-Ortiz
2015-03-03 15:39 ` Jorge Ramirez-Ortiz
2015-03-03 16:55 ` [version 2] amba uarts - arm type uarts fifo size provided by device tree Mark Rutland
2015-03-04 20:52 ` Jorge Ramirez-Ortiz [this message]
2015-03-09 12:25 ` Jorge Ramirez-Ortiz
2015-03-09 12:29 ` Russell King - ARM Linux
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=54F770AB.8090004@linaro.org \
--to=jorge.ramirez-ortiz@linaro.org \
--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).