linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: Russell King <linux@arm.linux.org.uk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Timur Tabi <timur@codeaurora.org>, Jon Masters <jcm@redhat.com>,
	Mark Langsdorf <mlangsdo@redhat.com>,
	Andre Przywara <andre.przywara@arm.com>,
	Dave Martin <dave.martin@linaro.org>,
	Aleksey Makarov <aleksey.makarov@linaro.org>,
	Christopher Covington <cov@codeaurora.org>
Subject: [PATCH] tty: amba-pl011: Use 32-bit accesses for SBSA UART
Date: Fri, 11 Mar 2016 01:35:53 -0500	[thread overview]
Message-ID: <1457678154-2272-1-git-send-email-cov@codeaurora.org> (raw)
In-Reply-To: <1457415800-8799-1-git-send-email-cov@codeaurora.org>

Version 2 of the Server Base System Architecture (SBSAv2) describes the
Generic UART registers as 32 bits wide. At least one implementation, found
on the Qualcomm Technologies QDF2432, only supports 32 bit accesses.
SBSAv3, which describes supported access sizes in greater detail,
explicitly requires support for both 16 and 32 bit accesses to all
registers (and 8 bit accesses to some but not all). Therefore, for broad
compatibility, simply use 32 bit accessors for the SBSA UART.

Tested-by: Mark Langsdorf <mlangsdo@redhat.com>
Signed-off-by: Christopher Covington <cov@codeaurora.org>
---
Changes new in v2:
* Fixed from address
* Elaborated on forward (SBSAv3) compatibility in commit message
* Included Mark Langsdorf's Tested-by, which now covers:
    QDF2432
    Seattle
    X-Gene 1
---
 drivers/tty/serial/amba-pl011.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c
index c0da0cc..ffb5eb8 100644
--- a/drivers/tty/serial/amba-pl011.c
+++ b/drivers/tty/serial/amba-pl011.c
@@ -121,6 +121,7 @@ static struct vendor_data vendor_arm = {
 
 static struct vendor_data vendor_sbsa = {
 	.reg_offset		= pl011_std_offsets,
+	.access_32b		= true,
 	.oversampling		= false,
 	.dma_threshold		= false,
 	.cts_event_workaround	= false,
-- 
Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  parent reply	other threads:[~2016-03-11  6:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  5:43 [PATCH] tty: amba-pl011: Use 32-bit accesses for SBSA UART Christopher Covington
2016-03-08 14:51 ` Mark Langsdorf
2016-03-11  6:35 ` Christopher Covington [this message]
2016-03-11 15:02   ` Peter Hurley
2016-03-11 23:38     ` [PATCH v2] " Christopher Covington
2016-03-15 10:08   ` [PATCH] " Andre Przywara
2016-03-30 12:30     ` Christopher Covington
2016-03-30 16:55       ` Greg Kroah-Hartman
2016-03-30 17:01         ` Timur Tabi
2016-03-30 18:01           ` Greg Kroah-Hartman
2016-03-30 18:11             ` Timur Tabi
2016-04-01 21:23         ` [PATCH v3] " Christopher Covington

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=1457678154-2272-1-git-send-email-cov@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=aleksey.makarov@linaro.org \
    --cc=andre.przywara@arm.com \
    --cc=dave.martin@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jcm@redhat.com \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mlangsdo@redhat.com \
    --cc=timur@codeaurora.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).