devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@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 19:48:39 -0500	[thread overview]
Message-ID: <54E532E7.8090008@linaro.org> (raw)
In-Reply-To: <20150219003409.GX8656-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>

On 02/18/2015 07:34 PM, Russell King - ARM Linux wrote:
> On Wed, Feb 18, 2015 at 02:33:42PM -0500, Jorge Ramirez-Ortiz wrote:
>> 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
> Sorry, I can't follow that thread.  What FIFO size do your UARTs have?
> What is the full ID of the UARTs?
>

I just added a temporary printk to my logs for clarity

[    3.328845] name = f7111000.uart, id = 0x241011, amba_rev = 2, fifo size = 64

--
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

      parent reply	other threads:[~2015-02-19  0:48 UTC|newest]

Thread overview: 8+ 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
     [not found]     ` <1424285593-2886-3-git-send-email-jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
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:33     ` Jorge Ramirez-Ortiz
2015-02-19  0:34       ` Russell King - ARM Linux
     [not found]         ` <20150219003409.GX8656-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2015-02-19  0:48           ` Jorge Ramirez-Ortiz [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=54E532E7.8090008@linaro.org \
    --to=jorge.ramirez-ortiz-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.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).