Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3159624pxk; Mon, 5 Oct 2020 02:39:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx0fA99I5wvv1MhuXIsy0SH5DInn3yArIzVWqpiFE5x6dk0g9OZazRv7paDi+hDthwmZ+9C X-Received: by 2002:a17:907:2089:: with SMTP id pv9mr10236824ejb.427.1601890786064; Mon, 05 Oct 2020 02:39:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601890786; cv=none; d=google.com; s=arc-20160816; b=OvSKvZM9/Lz3cpvq/kAVoGBJWi1JtfJ79gI1YOMfwbgsxnI6orYi0FbbDnzg5knmGq KhwcvRO6vNIPH0Ral+6Xcr6ppA6Z5vtbH0Y1CsaLxoA9UodmT4ag5NChAa1DA1qUW1EC WzPfXw1qSJOWkmg2/Utn3Z44YjM8F5/hLR00GgZzQg9SuiihEPZC6x4sKKhE2YV21G7q vyO2/nJzNG2rpfU9sKzfLil4p+XuMaC7nxfkZVJZrc6sdruOH7sVOslKM/+ETAUJD9l/ q+xeXtSdQuibakfdoI1Ggdb2gt4eQ1u09AvWj5+jd7hX3mrrF8ONRQ/t/GiXwZqkmFsz xtSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=QsaBfZFa2dvXngI+qikBeYVIehcnUn/8wXHfmURCQEA=; b=SqusX+L2sjU6rz2HGZ4hMy0GsaXUxSBgC6CSMXm5DRDyz7CRiYbWjRzvrYhBULxiZn t3rfdyoboOrL7ERr1d+pcPAvCD6we2N10g+AoWzpBI1oHXcg4XQhXKtuqbqmvzpTQw4r HPnJ4GnASfSI2sCM0rMvO/rX3Vj4SPynQfu0k/ZgBoDuIoqug1Iz6b+RTixX5cJ9eEU4 rz60fZ1laUgpOUJP2uJp3YArA+MLKC/vWhJJVFcwpEv2cmmg4xFuNoKVyliLGbKVOhHZ J54obOXkqPu64qfernqcIVdKouoExn3o/rstVtwL8TebOnY2Xs56tBNK6f3DkueKuCat B6Mw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Pgk0M12g; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d8si7075141edj.569.2020.10.05.02.39.23; Mon, 05 Oct 2020 02:39:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Pgk0M12g; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725934AbgJEJiY (ORCPT + 99 others); Mon, 5 Oct 2020 05:38:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50816 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725917AbgJEJiY (ORCPT ); Mon, 5 Oct 2020 05:38:24 -0400 Received: from mail-lf1-x142.google.com (mail-lf1-x142.google.com [IPv6:2a00:1450:4864:20::142]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0A415C0613CE; Mon, 5 Oct 2020 02:38:24 -0700 (PDT) Received: by mail-lf1-x142.google.com with SMTP id y2so10015533lfy.10; Mon, 05 Oct 2020 02:38:23 -0700 (PDT) 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=QsaBfZFa2dvXngI+qikBeYVIehcnUn/8wXHfmURCQEA=; b=Pgk0M12g2DtRJ1kAa1PGSelgbsxYQlS2lso0eKSxlD4N1cVf5e20H+glqExrxAqrUI 9Nf6vAtoA4YEhEfnQnopMNWK72mArJ5RrpqbeYqVmC6P3cX5k744sYEV/PS5FqaLm7OA +wiU38Q3ioB+Hm6EiKqGBN9sGquqVgdGhu4XY7IEDQE6DZnfkat7Pt7hrcf+7xAJet9n MlATvl5Cj2DSe+EVz0BzED9ODORqqYSsjRWGTATd2sLePQt+qYY4A14HXi1mX07cXfrL umwgYoAWFk7Nm+x7gWS7G8Z2sS/3sxzTuNxWDEu1qQNknleKhir7JYA2xNJNWoXbxVID uCqA== 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=QsaBfZFa2dvXngI+qikBeYVIehcnUn/8wXHfmURCQEA=; b=rtayqCpsNSgLmYo3+73qSPPETv/f50j7/AnN+qlne0qtDsVoCiAi8B5cxVtSi7nTtL c/nLuXje/xOMNe3KCy8MCFm1zMrt1eBGPd+cufqS/rtDh/FElTfVGmi1mvHfQNHCp/47 96+/TApwJaUpUAEM/HAB739IOuE2Uh8DYSwWf+AoIBi3g0MOk2wBzH/7kmG0cLIX7s/K j5Wbx/ivX3p2uM8atdg2U3vUmRMSHXN0XTGX3YIB2MaFX09ra7P2R9ciW75oNXe6S+Ig WNqcNuYsaEjPubnC80QO/LYVX2D1b379pCbSJDImZ0VgUCAurBksbvHD5xx9YvVINsvM +YTw== X-Gm-Message-State: AOAM531xAXWXtGVVKl2H4lLjtvYXjGYkWDR0Dvwas19V1UWVf9NZtWMi D6Xfks6+zg0vonc2UP/BrCLZGx3n8N4= X-Received: by 2002:ac2:4c88:: with SMTP id d8mr5071687lfl.428.1601890702324; Mon, 05 Oct 2020 02:38:22 -0700 (PDT) Received: from [192.168.2.145] ([109.252.91.252]) by smtp.googlemail.com with ESMTPSA id n3sm2627012lfq.274.2020.10.05.02.38.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 05 Oct 2020 02:38:21 -0700 (PDT) Subject: Re: [PATCH v3 2/3] iommu/tegra-smmu: Rework .probe_device and .attach_dev To: Thierry Reding Cc: Nicolin Chen , joro@8bytes.org, krzk@kernel.org, vdumpa@nvidia.com, jonathanh@nvidia.com, linux-tegra@vger.kernel.org, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org References: <20200930084258.25493-1-nicoleotsuka@gmail.com> <20200930084258.25493-3-nicoleotsuka@gmail.com> <20200930153131.GB3833404@ulmo> <20200930160626.GD3833404@ulmo> <20200930164707.GB3852280@ulmo> <35115ac1-fb25-7226-7b50-61193669e696@gmail.com> <20201001075811.GA3919720@ulmo> <4dbf5bcb-76af-53c5-31cf-880debbcebf3@gmail.com> <20201005091610.GC425362@ulmo> From: Dmitry Osipenko Message-ID: <1adede6e-ecbd-eea4-bd40-4969cd8719cc@gmail.com> Date: Mon, 5 Oct 2020 12:38:20 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20201005091610.GC425362@ulmo> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 05.10.2020 12:16, Thierry Reding пишет: ... >> I think you meant regmap in regards to protecting IO accesses, but this >> is not what regmap is about if IO accesses are atomic by nature. > > Then why is there regmap-mmio? To protect programming sequences for example, actually that's the only real use-case I saw in kernel drivers once. In our case there are no sequences that require protection, at least I'm not aware about that. >> Secondly, you're missing that tegra30-devfreq driver will also need to >> perform the MC lookup [3] and then driver will no longer work for the >> older DTs if phandle becomes mandatory because these DTs do not have the >> MC phandle in the ACTMON node. >> >> [3] >> https://github.com/grate-driver/linux/commit/441d19281f9b3428a4db1ecb3a02e1ec02a8ad7f >> >> So we will need the fall back for T30/124 as well. > > No, we don't need the fallback because this is new functionality which > can and should be gated on the existence of the new phandle. If there's > no phandle then we have no choice but to use the old code to ensure old > behaviour. You just repeated what I was trying to say:) Perhaps I spent a bit too much time touching that code to the point that lost feeling that there is a need to clarify everything in details.