From: Jon Masters <jcm@redhat.com>
To: Jon Mason <jon.mason@broadcom.com>,
Rafael Wysocki <rjw@rjwysocki.net>, Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
Lv Zheng <lv.zheng@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@acpica.org, bcm-kernel-feedback-list@broadcom.com,
Loc Ho <lho@apm.com>
Subject: Re: [PATCH] ACPI: SPCR: Use access width to determine mmio usage
Date: Sat, 6 May 2017 18:39:48 -0400 [thread overview]
Message-ID: <4e11bb2b-7cec-6a7b-ca2b-88be31a98b7d@redhat.com> (raw)
In-Reply-To: <1493910330-17913-1-git-send-email-jon.mason@broadcom.com>
On 05/04/2017 11:05 AM, Jon Mason wrote:
> The current SPCR code does not check the access width of the mmio, and
> uses a default of 8bit register accesses. This prevents devices that
> only do 16 or 32bit register accesses from working. By simply checking
> this field and setting the mmio string appropriately, this issue can be
> corrected. To prevent any legacy issues, the code will default to 8bit
> accesses if the value is anything but 16 or 32.
Thanks for this. Just as an FYI I've a running discussion with Microsoft
about defining additional UART subtypes in the DBG2 for special case
UARTs. Specifically, I want to address AppliedMicro's special 8250 dw IP
that also has a non-standard clock. At this time, there is general
agreement to use the access width for some cases rather than defining
yet more subtypes - so your patch is good.
Loc/Applied: please track this thread, incorporate feedback, and also
track the other general recent discussions of 8250 dw from this week.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2017-05-06 22:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 15:05 [PATCH] ACPI: SPCR: Use access width to determine mmio usage Jon Mason
2017-05-04 16:28 ` Moore, Robert
2017-05-04 17:30 ` Jon Mason
2017-05-05 3:09 ` Zheng, Lv
2017-05-05 21:54 ` Jon Mason
2017-05-06 22:39 ` Jon Masters [this message]
2017-05-08 19:11 ` Loc Ho
2017-05-08 19:50 ` Jon Masters
2017-05-08 19:57 ` Loc Ho
2017-05-08 20:34 ` Jon Mason
2017-05-08 20:51 ` Loc Ho
2017-05-08 21:23 ` Jon Mason
2017-05-08 21:28 ` Jon Masters
2017-05-08 21:32 ` Loc Ho
2017-06-20 18:33 ` Loc Ho
2017-06-20 21:27 ` Jon Mason
2017-06-20 21:41 ` Loc Ho
2017-06-20 21:43 ` Rafael J. Wysocki
2017-07-03 18:27 ` Loc Ho
2017-07-03 18:56 ` Rafael J. Wysocki
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=4e11bb2b-7cec-6a7b-ca2b-88be31a98b7d@redhat.com \
--to=jcm@redhat.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devel@acpica.org \
--cc=jon.mason@broadcom.com \
--cc=lenb@kernel.org \
--cc=lho@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
/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