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=-2.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 EEEC2C2D0D1 for ; Thu, 19 Dec 2019 16:34:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C335124650 for ; Thu, 19 Dec 2019 16:34:07 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="fYwP12aO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727071AbfLSQeH (ORCPT ); Thu, 19 Dec 2019 11:34:07 -0500 Received: from mail-lj1-f194.google.com ([209.85.208.194]:35393 "EHLO mail-lj1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726855AbfLSQeG (ORCPT ); Thu, 19 Dec 2019 11:34:06 -0500 Received: by mail-lj1-f194.google.com with SMTP id j6so6931150lja.2; Thu, 19 Dec 2019 08:34:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=NbGUxJZschh5pU5eBUWoyfxmgLY0Jtie4Fq87j9uajM=; b=fYwP12aOi9NdXLIYBDuMsIPSrXPApDqz1POx12Skp5WX/xXXSTSsF/HVtd7Wf+G4AW A/0iKnvcDCBdN1udrsefmIgBSgvsHGMPH+bPozR/f2ZCXuR22TgnzCUey7Z3WTX4S+o1 53PkDayjk238dAMSO1Ha21+HUiLGYI1RCrorqWH8TyP0jAgeriBPEypujR22PRj9mTb6 dKJEZew4DEO3wEQQ9ncPmtx0a1F39/sVZt2iqF6ZYsO4uNPDxohorTYg/IGT/nF6AZTC w7sq1iAHf9La7k5GuZnXwUr6wJk1wAjJyWRjx/nvLWwE4oUBQC7s093m1MEvX26GuXFj /9jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=NbGUxJZschh5pU5eBUWoyfxmgLY0Jtie4Fq87j9uajM=; b=SYGwakmBD1qRWQWXX7dtnP+oQztbo7PtVWajWnaobPwRNXkAoLkyh1KDPZEdTCUDnm EYOpppi9T3vOXATh/fOk7WsyNcdtzKNgKwdqvJ6ghHr9MPzT9YbBlX2JjCSMWJFhB8di iTmxJELugFxZ+JNd2YC7mF45WTExSPPyZG83QJ1nXoI9B34gqTaSV9J+72gSEapYeamP ZK5X5AdVf873Oj6j1+MDnFpxhlTx6ZTaziqks8etHBnJk7O/xsDZe51FMUCHgJB2xgnK qaarNE7LyvNsgFdwsAoovs8l5b8djjr4Vd0LfKKqnYrreAcE01xrh9mwBemCRIqy8JmM M8Eg== X-Gm-Message-State: APjAAAXUNT2WFrL83/gbt0MaQ2eYU25rGGcqahfaVVC7y2VpPN3NVelw pvQJShpOLS8endQHvv4Di/M0xYw/ X-Google-Smtp-Source: APXvYqytljIvdSb9uKAA4Z5f9O3C9KOePxedpYlxO/c853cn0BV5XGhgglOiAUNSRF8Vr2L4UbB00A== X-Received: by 2002:a2e:91cb:: with SMTP id u11mr6801694ljg.82.1576773243568; Thu, 19 Dec 2019 08:34:03 -0800 (PST) Received: from [192.168.2.145] (79-139-233-37.dynamic.spd-mgts.ru. [79.139.233.37]) by smtp.googlemail.com with ESMTPSA id g85sm2824824lfd.66.2019.12.19.08.34.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Dec 2019 08:34:02 -0800 (PST) Subject: Re: [PATCH v1 1/3] gpio: tegra: Use generic readl_relaxed/writel_relaxed accessors To: Ben Dooks , Bartosz Golaszewski Cc: Thierry Reding , Jonathan Hunter , Linus Walleij , linux-gpio , linux-tegra@vger.kernel.org, devel@driverdev.osuosl.org, LKML References: <20191215183047.9414-1-digetx@gmail.com> <20191215183047.9414-2-digetx@gmail.com> From: Dmitry Osipenko Message-ID: Date: Thu, 19 Dec 2019 19:34:01 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 19.12.2019 18:57, Ben Dooks пишет: > On 19/12/2019 11:01, Bartosz Golaszewski wrote: >> niedz., 15 gru 2019 o 19:31 Dmitry Osipenko >> napisał(a): >>> >>> There is no point in using old-style raw accessors, the generic >>> accessors >>> do the same thing and also take into account CPU endianness. Tegra >>> SoCs do >>> not support big-endian mode in the upstream kernel, but let's switch >>> away >>> from the outdated things anyway, just to keep code up-to-date. > > Good idea, I think I got most of the way to booting a tegra jetson board > with a big endian image a few years ago, but never got time to finish > the work. > Thanks, I remember yours effort in regards to the upstreaming big endian support for Jetson :) You were pretty close back then, but Thierry had a different opinion in regards to maintaining that support in terms of having extra testing burden.