From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Ungerer <gerg@linux-m68k.org>, Helge Deller <deller@gmx.de>,
linux-m68k@lists.linux-m68k.org, netdev@vger.kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] Input: hilkbd - Add casts to HP9000/300 I/O accessors
Date: Mon, 16 Jul 2018 12:21:25 +0000 [thread overview]
Message-ID: <20180716122125.m5ycmj7xh2mmufnf@penguin> (raw)
In-Reply-To: <20180709093040.23597-4-geert@linux-m68k.org>
On Mon, Jul 09, 2018 at 11:30:38AM +0200, Geert Uytterhoeven wrote:
> Internally, hilkbd uses "unsigned long" I/O addresses everywhere.
> This works fine as:
> - On PA-RISC, hilkbd uses the gsc_{read,write}b() I/O accessors, which
> take "unsigned long" addresses,
> - On m68k, hilkbd uses {read,write}b(), which are currently mapped to
> {in,out}_8(), and convert the passed addresses to pointers
> internally.
>
> However, the asm-generic version of {read,write}b() does not perform
> such conversions, and requires passing pointers instead. Hence add
> casts to prepare for switching m68k to the asm-generic version.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
> This is a dependency for "m68k/io: Switch mmu variant to
> <asm-generic/io.h>".
>
> v2:
> - No changes.
> ---
> drivers/input/keyboard/hilkbd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/input/keyboard/hilkbd.c b/drivers/input/keyboard/hilkbd.c
> index a4e404aaf64bdb82..5c7afdec192c139b 100644
> --- a/drivers/input/keyboard/hilkbd.c
> +++ b/drivers/input/keyboard/hilkbd.c
> @@ -57,8 +57,8 @@ MODULE_LICENSE("GPL v2");
> #define HIL_DATA 0x1
> #define HIL_CMD 0x3
> #define HIL_IRQ 2
> - #define hil_readb(p) readb(p)
> - #define hil_writeb(v,p) writeb((v),(p))
> + #define hil_readb(p) readb((const volatile void __iomem *)(p))
> + #define hil_writeb(v, p) writeb((v), (volatile void __iomem *)(p))
>
> #else
> #error "HIL is not supported on this platform"
> --
> 2.17.1
>
--
Dmitry
next prev parent reply other threads:[~2018-07-16 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 9:30 [PATCH 0/5] m68k: IO Fixes and Cleanups Geert Uytterhoeven
2018-07-09 9:30 ` [PATCH 1/5] m68k/io: Add missing ioremap define guards, fix typo Geert Uytterhoeven
2018-07-09 9:30 ` [PATCH 2/5] net: mac8390: Use standard memcpy_{from,to}io() Geert Uytterhoeven
2018-07-09 9:30 ` [PATCH 3/5] Input: hilkbd - Add casts to HP9000/300 I/O accessors Geert Uytterhoeven
2018-07-16 12:21 ` Dmitry Torokhov [this message]
2018-07-09 9:30 ` [PATCH 4/5] m68k/io: Move mem*io define guards to <asm/kmap.h> Geert Uytterhoeven
2018-07-09 9:30 ` [PATCH 5/5] m68k/io: Switch mmu variant to <asm-generic/io.h> Geert Uytterhoeven
2018-07-10 1:48 ` [PATCH 0/5] m68k: IO Fixes and Cleanups Greg Ungerer
2018-07-18 11:37 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2018-07-02 13:35 Geert Uytterhoeven
2018-07-02 13:35 ` [PATCH 3/5] Input: hilkbd - Add casts to HP9000/300 I/O accessors Geert Uytterhoeven
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=20180716122125.m5ycmj7xh2mmufnf@penguin \
--to=dmitry.torokhov@gmail.com \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=netdev@vger.kernel.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