From mboxrd@z Thu Jan 1 00:00:00 1970 From: Logan Gunthorpe Subject: Re: [PATCH 4/7] alpha: provide ioread64 and iowrite64 implementations Date: Thu, 22 Jun 2017 15:10:20 -0600 Message-ID: <3ae2d934-1054-cdd1-7eaa-e9758276cf51@deltatee.com> References: <20170622164817.25515-1-logang@deltatee.com> <20170622164817.25515-5-logang@deltatee.com> <20170622210828.27304f6a@alans-desktop> <401cdb64-6fdb-be30-b8bc-bf51c1a35074@deltatee.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-alpha-owner@vger.kernel.org To: Arnd Bergmann Cc: Alan Cox , Linux Kernel Mailing List , linux-arch , linux-ntb@googlegroups.com, linux-alpha@vger.kernel.org, linuxppc-dev , linux-crypto@vger.kernel.org, dri-devel , Greg Kroah-Hartman , Stephen Bates , Richard Henderson , Ivan Kokshaysky , Matt Turner List-Id: linux-arch.vger.kernel.org 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ale.deltatee.com ([207.54.116.67]:54887 "EHLO ale.deltatee.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751221AbdFVVKf (ORCPT ); Thu, 22 Jun 2017 17:10:35 -0400 References: <20170622164817.25515-1-logang@deltatee.com> <20170622164817.25515-5-logang@deltatee.com> <20170622210828.27304f6a@alans-desktop> <401cdb64-6fdb-be30-b8bc-bf51c1a35074@deltatee.com> From: Logan Gunthorpe Message-ID: <3ae2d934-1054-cdd1-7eaa-e9758276cf51@deltatee.com> Date: Thu, 22 Jun 2017 15:10:20 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PATCH 4/7] alpha: provide ioread64 and iowrite64 implementations Sender: linux-arch-owner@vger.kernel.org List-ID: To: Arnd Bergmann Cc: Alan Cox , Linux Kernel Mailing List , linux-arch , linux-ntb@googlegroups.com, linux-alpha@vger.kernel.org, linuxppc-dev , linux-crypto@vger.kernel.org, dri-devel , Greg Kroah-Hartman , Stephen Bates , Richard Henderson , Ivan Kokshaysky , Matt Turner Message-ID: <20170622211020.Ab6S6JiO_WMCdU3o374FvSO2Fu9J6ZxaoZwYVyFAujE@z> 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