public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] parisc: use the asm-generic version for writeX()
Date: Mon, 16 Apr 2018 19:15:37 -0400	[thread overview]
Message-ID: <a7b59f43-cea5-0ead-f528-61899570e353@codeaurora.org> (raw)
In-Reply-To: <a727e74f-610c-4722-76e9-c1aca2f9e9bd@bell.net>

On 4/16/2018 7:09 PM, John David Anglin wrote:
> On 2018-04-16 6:01 PM, Sinan Kaya wrote:
>> parisc architecture seems to be mapping writeX() and writeX_relaxed() APIs
>> to __raw_writeX() API.
>>
>> __raw_writeX() API doesn't provide any kind of ordering guarantees.
>> commit 755bd04aaf4b ("io: define stronger ordering for the default writeX()
>> implementation") changed asm-generic implementation to use a more
>> conservative approach towards the writeX() API.
>>
>> Drop the arch specific version and rely on the asm-generic version for
>> parisc since parisc version doesn't seem to do anything special with these
>> macros.
> ? HOSTLD? scripts/mod/modpost
> In file included from ./arch/parisc/include/asm/hardirq.h:13:0,
> ???????????????? from ./include/linux/hardirq.h:9,
> ???????????????? from arch/parisc/kernel/asm-offsets.c:34:
> ./include/linux/irq.h: In function 'irq_reg_writel':
> ./include/linux/irq.h:1114:3: error: implicit declaration of function 'writel' [-Werror=implicit-function-declaration]
> ?? writel(val, gc->reg_base + reg_offset);
> ?? ^~~~~~
> ./include/linux/irq.h: In function 'irq_reg_readl':
> ./include/linux/irq.h:1123:10: error: implicit declaration of function 'readl' [-Werror=implicit-function-declaration]
> ?? return readl(gc->reg_base + reg_offset);
> ????????? ^~~~~
> cc1: some warnings being treated as errors
> make[1]: *** [Kbuild:58: arch/parisc/kernel/asm-offsets.s] Error 1
> 
> Dave
> 

Thanks for testing. Can you add this on top and see if it helps?

--- a/arch/parisc/include/asm/io.h
+++ b/arch/parisc/include/asm/io.h
@@ -259,6 +259,7 @@ extern void outsl (unsigned long port, const void *src, unsigned long count);
  * value for either 32 or 64 bit mode */
 #define F_EXTEND(x) ((unsigned long)((x) | (0xffffffff00000000ULL)))
 
+#include <asm-generic/io.h>
 #include <asm-generic/iomap.h>


-- 
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2018-04-16 23:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 22:01 [PATCH 1/2] parisc: use the asm-generic version for writeX() Sinan Kaya
2018-04-16 22:01 ` [PATCH 2/2] parisc: use the asm-generic version for readX() Sinan Kaya
2018-04-17  4:57   ` kbuild test robot
2018-04-16 23:09 ` [PATCH 1/2] parisc: use the asm-generic version for writeX() John David Anglin
2018-04-16 23:15   ` Sinan Kaya [this message]
2018-04-16 23:37     ` John David Anglin
2018-04-16 23:44       ` Sinan Kaya
2018-04-16 23:48         ` Sinan Kaya
2018-04-17  4:11           ` Sinan Kaya
2018-04-17  4:30 ` kbuild test robot

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=a7b59f43-cea5-0ead-f528-61899570e353@codeaurora.org \
    --to=okaya@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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