From: Ji Zhang <ji.zhang@mediatek.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com,
Ji Zhang <ji.zhang@mediatek.com>,
shadanji@163.com
Subject: [PATCH] fbdev: arm64 use __raw I/O memory api
Date: Thu, 30 Nov 2017 08:17:22 +0000 [thread overview]
Message-ID: <1512029842-10939-1-git-send-email-ji.zhang@mediatek.com> (raw)
Since arm64 also has __raw I/O accessors, add __aarch64__ in fb.h.
This is a supplement for commmit
981409b25e2a99409b26daa67293ca1cfd5ea0a0
Signed-off-by: Ji Zhang <ji.zhang@mediatek.com>
---
include/linux/fb.h | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/linux/fb.h b/include/linux/fb.h
index bc24e48..cea8a2c 100644
--- a/include/linux/fb.h
+++ b/include/linux/fb.h
@@ -564,7 +564,10 @@ static inline struct apertures_struct *alloc_apertures(unsigned int max_num) {
#define fb_memcpy_fromfb sbus_memcpy_fromio
#define fb_memcpy_tofb sbus_memcpy_toio
-#elif defined(__i386__) || defined(__alpha__) || defined(__x86_64__) || defined(__hppa__) || defined(__sh__) || defined(__powerpc__) || defined(__avr32__) || defined(__bfin__) || defined(__arm__)
+#elif defined(__i386__) || defined(__alpha__) || defined(__x86_64__) || \
+ defined(__hppa__) || defined(__sh__) || defined(__powerpc__) || \
+ defined(__avr32__) || defined(__bfin__) || defined(__arm__) || \
+ defined(__aarch64__)
#define fb_readb __raw_readb
#define fb_readw __raw_readw
--
1.9.1
next reply other threads:[~2017-11-30 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171130081731epcas1p1bdd2f9a3e55307bf732ba4c7cbbd8f01@epcas1p1.samsung.com>
2017-11-30 8:17 ` Ji Zhang [this message]
2018-01-04 14:40 ` [PATCH] fbdev: arm64 use __raw I/O memory api Bartlomiej Zolnierkiewicz
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=1512029842-10939-1-git-send-email-ji.zhang@mediatek.com \
--to=ji.zhang@mediatek.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=shadanji@163.com \
--cc=wsd_upstream@mediatek.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).