All of lore.kernel.org
 help / color / mirror / Atom feed
From: jorge.ramirez-ortiz@linaro.org (Jorge Ramirez-Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: amba uarts - arm type uarts fifo size provided by device tree
Date: Wed, 18 Feb 2015 14:33:42 -0500	[thread overview]
Message-ID: <54E4E916.1010009@linaro.org> (raw)
In-Reply-To: <20150218190601.GI29429@leverpostej>

On 02/18/2015 02:06 PM, Mark Rutland wrote:
> Hi,
>
> Please Cc lakml for patches in this area in future.
>
> On Wed, Feb 18, 2015 at 06:53:11PM +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
>>
>>
>> These patches aim at resolving an issue present on some of the amba pl011
>> uarts.  
> Which systems are affected? Neither of your two patches add the property
> to any dts file.


yes, the system affected is still under revision (I should have mentioned)
https://lkml.org/lkml/2015/2/5/144

this is the board I am using to test
https://www.96boards.org/products/hikey/

>
>> Some of these arm type uarts have their fifo sizes not defined in terms of the
>> amba_rev register. 
> What does said register actually contain?

the amba_rev contains '1' for the Hisilicon Hi6220 SoC

>
> Is this a full PL011, or a cut-down SBSA UART?

I believe is full PL011 (ARM type) - that is what is being run in my tests.

>
> Mark.
>
>> Those uarts should be able to declare their fifo sizes using the optional
>> property "fifo-size" in the device tree. This device tree setting shall take
>> precedence over any other values. 
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe devicetree" in
>> the body of a message to majordomo at vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>

WARNING: multiple messages have this Message-ID (diff)
From: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: amba uarts - arm type uarts fifo size provided by device tree
Date: Wed, 18 Feb 2015 14:33:42 -0500	[thread overview]
Message-ID: <54E4E916.1010009@linaro.org> (raw)
In-Reply-To: <20150218190601.GI29429@leverpostej>

On 02/18/2015 02:06 PM, Mark Rutland wrote:
> Hi,
>
> Please Cc lakml for patches in this area in future.
>
> On Wed, Feb 18, 2015 at 06:53:11PM +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
>>
>>
>> These patches aim at resolving an issue present on some of the amba pl011
>> uarts.  
> Which systems are affected? Neither of your two patches add the property
> to any dts file.


yes, the system affected is still under revision (I should have mentioned)
https://lkml.org/lkml/2015/2/5/144

this is the board I am using to test
https://www.96boards.org/products/hikey/

>
>> Some of these arm type uarts have their fifo sizes not defined in terms of the
>> amba_rev register. 
> What does said register actually contain?

the amba_rev contains '1' for the Hisilicon Hi6220 SoC

>
> Is this a full PL011, or a cut-down SBSA UART?

I believe is full PL011 (ARM type) - that is what is being run in my tests.

>
> Mark.
>
>> Those uarts should be able to declare their fifo sizes using the optional
>> property "fifo-size" in the device tree. This device tree setting shall take
>> precedence over any other values. 
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe devicetree" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-02-18 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 18:53 amba uarts - arm type uarts fifo size provided by device tree Jorge Ramirez-Ortiz
     [not found] ` <1424285593-2886-1-git-send-email-jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-02-18 18:53   ` [PATCH 1/2] Documentation: bindings: add optional fifo size property to AMBA UARTs Jorge Ramirez-Ortiz
2015-02-18 18:53   ` [PATCH 2/2] drivers/tty: pl011: read fifo size from OF if present Jorge Ramirez-Ortiz
2015-02-18 19:08     ` Mark Rutland
2015-02-18 19:08       ` Mark Rutland
2015-02-18 19:06 ` amba uarts - arm type uarts fifo size provided by device tree Mark Rutland
2015-02-18 19:06   ` Mark Rutland
2015-02-18 19:33   ` Jorge Ramirez-Ortiz [this message]
2015-02-18 19:33     ` Jorge Ramirez-Ortiz
2015-02-19  0:34     ` Russell King - ARM Linux
2015-02-19  0:34       ` Russell King - ARM Linux
2015-02-19  0:48       ` Jorge Ramirez-Ortiz
2015-02-19  0:48         ` Jorge Ramirez-Ortiz

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=54E4E916.1010009@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.