[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ae2d934-1054-cdd1-7eaa-e9758276cf51@deltatee.com>
Date: Thu, 22 Jun 2017 15:10:20 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Alan Cox <gnomes@...rguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>,
linux-ntb@...glegroups.com, linux-alpha@...r.kernel.org,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
linux-crypto@...r.kernel.org,
dri-devel <dri-devel@...ts.freedesktop.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Stephen Bates <sbates@...thlin.com>,
Richard Henderson <rth@...ddle.net>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Matt Turner <mattst88@...il.com>
Subject: Re: [PATCH 4/7] alpha: provide ioread64 and iowrite64 implementations
On 6/22/2017 3:03 PM, Arnd Bergmann wrote:
> Drivers that want a non-atomic variant should include either
> include/linux/io-64-nonatomic-hi-lo.h or include/linux/io-64-nonatomic-lo-hi.h
> depending on what they need. Drivers that require 64-bit I/O should
> probably just depend on CONFIG_64BIT and maybe use readq/writeq.
Ok, I will work something like that up.
We'll still need a patch similar to patch 2 (less the non-atomic
versions) seeing even CONFIG_GENERIC_IOMAP arches don't actually have a
working ioread64/iowrite64 implementation.
Thanks,
Logan
Powered by blists - more mailing lists