From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christopher Covington <cov@codeaurora.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
Russell King <linux@arm.linux.org.uk>,
Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Timur Tabi <timur@codeaurora.org>, Jon Masters <jcm@redhat.com>,
Mark Langsdorf <mlangsdo@redhat.com>,
Dave Martin <dave.martin@linaro.org>,
Aleksey Makarov <aleksey.makarov@linaro.org>
Subject: Re: [PATCH] tty: amba-pl011: Use 32-bit accesses for SBSA UART
Date: Wed, 30 Mar 2016 09:55:51 -0700 [thread overview]
Message-ID: <20160330165551.GB23817@kroah.com> (raw)
In-Reply-To: <56FBC6EA.6080909@codeaurora.org>
On Wed, Mar 30, 2016 at 08:30:34AM -0400, Christopher Covington wrote:
> Hi Greg,
>
> On 03/15/2016 06:08 AM, Andre Przywara wrote:
> > Hi Christopher,
> >
> > On 11/03/16 06:35, Christopher Covington wrote:
> >> 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>
> >
> > So I gave this a try on a Juno and a Midway. Both have a normal PL011,
> > but I changed the DT to advertise an SBSA UART instead.
> > This worked fine with the 32bit accessors.
> > Also according to some research on the hardware size at least the
> > current ARM PL011 implementation are totally fine with 32-bit (as well
> > as 16-bit) accesses.
> > There is some reluctance about whether this is true for _every_ older
> > PL011 implementation, but they are out of scope here, as we are talking
> > about the SBSA only.
> > So:
> >
> > Tested-by: Andre Przywara <andre.przywara@arm.com>
> > Acked-by: Andre Przywara <andre.przywara@arm.com>
> >
> > You can add Juno and Midway to the list of tested systems.
>
> >> Changes new in v2:
>
> Apologies for omitting the v2 prefix in the second version of the patch
> that I sent out.
>
> >> * 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,
> >>
>
> Do you consider this patch suitable to be included in a 4.6 release
> candidate? It fixes an issue running this driver on certain hardware,
> and with gracious assistance we've performed due diligence to check that
> it does not adversely affect the driver running on other hardware. Would
> it be useful to send a v3 collecting the acks and tested-bys?
If this isn't a bug fix or regression fix, it's not ok for 4.6-final, it
will have to wait for 4.7-rc1.
And yes, collecting the acks and tested-bys would be great, I'm always
glad to see that, it makes my job easier. Now that 4.6-rc1 is out, I'll
start to dig through the list of pending patches here, give me a few
weeks to get all of them, especially due to the conference travel I'm
currently doing...
thanks,
greg k-h
next prev parent reply other threads:[~2016-03-30 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 5:43 Christopher Covington
2016-03-08 14:51 ` Mark Langsdorf
2016-03-11 6:35 ` Christopher Covington
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 [this message]
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=20160330165551.GB23817@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aleksey.makarov@linaro.org \
--cc=andre.przywara@arm.com \
--cc=cov@codeaurora.org \
--cc=dave.martin@linaro.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
all inboxes | Powered by JetHome®