From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 351FCC3279B for ; Wed, 4 Jul 2018 17:22:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D146F23C6A for ; Wed, 4 Jul 2018 17:22:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Q+tbJn1v" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D146F23C6A Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752921AbeGDRWD (ORCPT ); Wed, 4 Jul 2018 13:22:03 -0400 Received: from mail-ua0-f195.google.com ([209.85.217.195]:34106 "EHLO mail-ua0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752251AbeGDRWA (ORCPT ); Wed, 4 Jul 2018 13:22:00 -0400 Received: by mail-ua0-f195.google.com with SMTP id r10-v6so3857833uao.1; Wed, 04 Jul 2018 10:21:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=j+6Sp+K9kUz8dK1lUhikjijSH30SNgaMDD/lO178fiM=; b=Q+tbJn1vzAw8F3IPO7Nfi8w4AjPZ/3aZHzzkpEg+ScHXDO2lC3z1ZaLOG4YhhGrltv m2xjFdHtjO3Z2NnYAXZKvMsgUxN7L39WZYIae97sSjer6PKYwN1nQDNh0HXKQ12HBuaT 7BCzCW0hy9pcPFMOtsk248Okc8drbo+lf1jgqoqSElIDdKMGXXZ8rjvaNZCkpmIQ3OSI XWthsq05vNNSFUaE08w91gEywCzdf9/5jysRvo8Q7qmdwBuraY0uzWnHh/Jn76ZVW2Wy LURKhynQRotMm3BbOh/cmUFJS23ebYhvF/8L5Z7Fjot99LJtTQViJfBqJSwYduHsS67O IqVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=j+6Sp+K9kUz8dK1lUhikjijSH30SNgaMDD/lO178fiM=; b=inmQKAeWy4BV5ZOQZ1wz8HcjvW4qZmZUVZVL4yeNuqj7S+193+FUkKf3EWrdyMiBdZ FEy4E7DxpD7P4UviiVfVR7PJqqXFLXE4eiNTpRUGSZi3B5C8hCdwDeEzLhqD8+Dsah/F tkjzGU6+C4DT0xLd2wMDm43VS4QmQLJvIUmw7Cyveh+Rx96mlsr+0EV+TzGJaT1wmKiv lkwZIISR3WUn4VlXoAZJy8mOaT6t6dJpE9ow8zS0B8ZAPRUS5faoxUU1z3nSN+52DM5o F/nSuleojgQXkrf29mJBwoqI8TxoAQ8XE06AENEsZjvvBTRcS4SmStPVMQd22QumzruK 3Apw== X-Gm-Message-State: APt69E1KifUwK1Phyk5DPoomtARPobS07bWVSuSl9ztSjJADb5ja9YAu nmcN41z/2huRVip/zQOLHrsoEBBEkGmizM9hJ0RY2GKo X-Google-Smtp-Source: AAOMgpcT0CW/ErcN5yM9kdppTDhw4fXmpnqvBvD+tD3zYiTRXHqmixpGlK6hWjE+aYke0udBHFMW6ESk8yuyz2aMznI= X-Received: by 2002:ab0:1a23:: with SMTP id a35-v6mr1700047uai.47.1530724919164; Wed, 04 Jul 2018 10:21:59 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a67:2149:0:0:0:0:0 with HTTP; Wed, 4 Jul 2018 10:21:58 -0700 (PDT) In-Reply-To: References: <20180622194752.11221-1-logang@deltatee.com> <13ea3f97-4a33-3a24-1b7e-b819be73d867@deltatee.com> <6e5224b9-343f-990c-19bd-fe37c6fbdc9b@deltatee.com> <7ddda181-6337-32cc-7a0d-43fc6a7ba78b@deltatee.com> <991b2298-bb3f-dad3-c93b-b43ee5f372de@deltatee.com> <55236e2b-a2a5-493a-5696-19c5926885b3@deltatee.com> From: Andy Shevchenko Date: Wed, 4 Jul 2018 20:21:58 +0300 Message-ID: Subject: Re: [PATCH v18 6/7] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 To: Logan Gunthorpe Cc: Fabio Estevam , Horia Geanta , Aymen Sghaier , Andrew Morton , linux-kernel , Linux-Arch , "linux-ntb@googlegroups.com" , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , Arnd Bergmann , Greg Kroah-Hartman , Dan Douglass , Herbert Xu , "David S. Miller" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 4, 2018 at 8:16 PM, Andy Shevchenko wrote: > On Wed, Jul 4, 2018 at 8:13 PM, Logan Gunthorpe wrote: >> On 7/4/2018 11:10 AM, Andy Shevchenko wrote: >>> We have an iDMA 32-bit hardware (see drivers/dma/dw/) which has an >>> extension 64-bit registers where only one of them has a specific bit >>> to "commit" the changes written to all of them. And by some very >>> unknown reason that bit is in lo part which automatically means we >>> must to write it last. >> >> And it supports both BE and LE? And in both cases it's the lo part? > > It's only LE for now. > > P.S. If you more interested in code in kernel look for idma32_fifo_partition() > (While the bit is set in each of 32-bit part, it's actually present in > only one place) I think it doesn't contradict with what you are saying rather supports it. I would expect to have lo-hi and hi-lo semantics done according to the data flow, not to the address. -- With Best Regards, Andy Shevchenko