From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] PMAG-AA frame buffer driver rework
Date: Mon, 22 Feb 2016 01:54:54 +0000 [thread overview]
Message-ID: <alpine.LFD.2.20.1602220110330.7431@eddie.linux-mips.org> (raw)
Hi,
This is an update to the PMAG-AA frame buffer driver to adapt it to our
current APIs, which I promised a while ago (too much of a while, which I
apologise for).
This series starts with a change that makes the driver build and retains
its previous functionality. A bunch of further clean-ups follow, each of
which is explained individually. There's a potential in this code for
further clean-ups and improvements, but the weekend is running out quick
now, so I had to stop somewhere. Next time then.
A couple of checkpatch.pl warnings are noted.
First on using `printk(KERN_ERR ...' rather tha `pr_err'. I could
probably fix it, but I think it's not worth it by itself, the interface is
not wrong and the issue is mainly cosmetical. I think I'll just go across
all the pmag* drivers at once and bulk convert these calls sometime.
Second on using `mb()' (without a comment). This is not a new problem as
the driver has lots of these calls throughout. Fixing them is blocked on
the unavailability of generic cross-platform MMIO synchronisation and
completion barriers. See the discussion at:
<http://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-mips&i=alpine.LFD.2.11.1404280048540.11598%40eddie.linux-mips.org>
for details. Most TURBOchannel drivers suffer from this problem due to
the complexities around many MIPS processors being weakly ordered,
including in particular those used in TURBOchannel systems. Once the
generic issue of MMIO barriers has been sorted out the hacks to use memory
barriers (which just happen to DTRT on the MIPS platform, because there's
just a single underlying mechanism for all kinds of barriers in the MIPS
architecture) in their place can be removed.
All of these pieces have been visually tested with a live specimen. VT
only however at this point, no X11.
Please apply,
Maciej
next reply other threads:[~2016-02-22 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 1:54 Maciej W. Rozycki [this message]
2016-02-22 1:54 ` [PATCH 1/7] video: fbdev: pmag-aa-fb: Adapt to current APIs Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 2/7] video: fbdev: pmag-aa-fb: Enable building as a module Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 3/7] video: fbdev: pmag-aa-fb: Report video timings Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 4/7] video: fbdev: bt455: Remove unneeded colormap helpers for cursor support Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 5/7] video: fbdev: pmag-ba-fb: Fix and rework Bt455 colormap handling Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 6/7] video: fbdev: pmag-ba-fb: Optimize Bt455 colormap addressing Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 7/7] video: fbdev: bt431: Correct cursor format control macro Maciej W. Rozycki
2016-02-26 11:15 ` [PATCH 0/7] PMAG-AA frame buffer driver rework Tomi Valkeinen
2016-02-27 22:23 ` Maciej W. Rozycki
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=alpine.LFD.2.20.1602220110330.7431@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).