From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752919AbeDFNUo (ORCPT <rfc822;w@1wt.eu>);
        Fri, 6 Apr 2018 09:20:44 -0400
Received: from mail-qk0-f172.google.com ([209.85.220.172]:32927 "EHLO
        mail-qk0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752442AbeDFNUm (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 6 Apr 2018 09:20:42 -0400
X-Google-Smtp-Source: AIpwx48CJU7TU/hG7QjPJVthCi+jHKBwIkdLfHruw3jgxxuSsD//hwkiEnrwFxV35EnL+DYymDvqAxgF90qjK12mqVQ=
MIME-Version: 1.0
In-Reply-To: <fa0b02f16cb4cb993775518fabccfb2d@codeaurora.org>
References: <1522933753-19589-1-git-send-email-okaya@codeaurora.org>
 <CAK8P3a0Ahf9uuXYy0fxdC5_O84gmSqTUsP6xjpGQFE8n1Tw7HA@mail.gmail.com> <fa0b02f16cb4cb993775518fabccfb2d@codeaurora.org>
From: Arnd Bergmann <arnd@arndb.de>
Date: Fri, 6 Apr 2018 15:20:40 +0200
X-Google-Sender-Auth: WXoSY0bSHVpd9o6Pva4ITWe5iMU
Message-ID: <CAK8P3a3qpbPZuEhW=pYnadDtg5UGRpiD_k2=XiJanqmmTL5VzA@mail.gmail.com>
Subject: Re: [PATCH v4 1/5] io: define several IO & PIO barrier types for the
 asm-generic version
To: Sinan Kaya <okaya@codeaurora.org>
Cc: Timur Tabi <timur@codeaurora.org>, sulrich@codeaurora.org,
        linux-arm-msm@vger.kernel.org,
        Linux ARM <linux-arm-kernel@lists.infradead.org>,
        linux-arch <linux-arch@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-s390 <linux-s390@vger.kernel.org>,
        Martin Schwidefsky <schwidefsky@de.ibm.com>,
        Heiko Carstens <heiko.carstens@de.ibm.com>,
        Ley Foon Tan <lftan@altera.com>,
        "moderated list:NIOS2 ARCHITECTURE"
        <nios2-dev@lists.rocketboards.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Apr 6, 2018 at 2:50 PM,  <okaya@codeaurora.org> wrote:
> On 2018-04-06 06:19, Arnd Bergmann wrote:
>>
>> On Thu, Apr 5, 2018 at 3:09 PM, Sinan Kaya <okaya@codeaurora.org> wrote:
>>>
>>
>> I would guess that at least s390 doesn't need the barriers
>> (maintainers on Cc now), but there may be others that want to
>> override the new barriers with weaker ones where an MMIO
>> access is guaranteed to serialize against DMA, or where
>> a specialized barrier for this case exists.
>>
>> Looking over the asm-generic implementation once more now,
>> I wonder if we should change the relaxed accessors to not have
>> any barriers (back to the version before your series) rather than
>> defaulting them to having the same barriers as the regular
>> readl/writel.
>
>
> I can do a follow up patch. You want to map them to raw api without any
> barriers as before. Right?

Right, but of course with the byteswap.

      Arnd