From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Airlie <airlied@gmail.com>
Cc: YC Chen <yc_chen@aspeedtech.com>, dri-devel@lists.freedesktop.org
Subject: Re: ast2400 woes
Date: Sat, 07 Jun 2014 09:20:12 +1000 [thread overview]
Message-ID: <1402096812.3247.274.camel@pasglop> (raw)
In-Reply-To: <1402054302.3247.242.camel@pasglop>
On Fri, 2014-06-06 at 21:31 +1000, Benjamin Herrenschmidt wrote:
> The spec is pretty tricky to read but seems to indicate that the above
> offset should also work for PIO if needed, however, it seems like the
> X driver is pretty happy to use MMIO unconditionally for them.
>
> Any objection on me sending you a patch to send (almost) everybody to
> use the MMIO path ?
>
> The only remaining "issues" with PIO is the EnableVGA / IsVGAEnabled
> path which still uses PIO in X.
>
> Now, at least on the AST2400, the register in question is also on MMIO
> (3c3, aka VGA_ENABLE_PORT in the above list), but I don't know whether
> that works on all the older chipsets. (YC Chen on CC might have an opinion).
Ok, I think we need YC Chen answers here. Basically from what I can
tell those old "IO" registers and those new "MMIO" ones only differ
by that offset of 0x340.
The question thus boils down to:
- Are the "3xx" versions only MMIO or PIO as well ?
- Are the "3xx" version always available on all chips ?
- Is MMIO always available on all chips ?
IE. Is there a reason why bASTIsVGAEnabled() and vASTEnableVGAMMIO
use the IO ports ? The latter reads 0x43 and writes 0x43 and 0x42,
can it be made to always use MMIO 0x3c3 and write 0x3c3 and 0x3c2 ?
On my AST2400 at least, even when MMIO is disabled, 0x3c3 still
responds so it works but is that valid for all chips ? Or do I need
to favor the PIO path if PIO is available in that case for older
chipsets ?
Thanks !
Cheers,
Ben.
next prev parent reply other threads:[~2014-06-06 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 11:31 ast2400 woes Benjamin Herrenschmidt
2014-06-06 23:20 ` Benjamin Herrenschmidt [this message]
2014-06-07 7:16 ` Benjamin Herrenschmidt
2014-06-09 2:41 ` YC Chen
2014-06-09 4:09 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2014-06-06 11:31 Benjamin Herrenschmidt
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=1402096812.3247.274.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=yc_chen@aspeedtech.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