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=-6.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,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 EA699C47092 for ; Wed, 2 Jun 2021 15:00:08 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A8065613B4 for ; Wed, 2 Jun 2021 15:00:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A8065613B4 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=canonical.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Reply-To:Content-ID:Content-Description :Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=GF5QkAIuHky5LuUnL1WcrzzODc16z7eBCQuCqSoCvKE=; b=wb1LGBzut7J5HN h8A3RnyiOopclqlJBTn/XDsVEg18bAPgib6LoD2pPoBGylNwvzzB2rmgwLD+cQA81WBSOJNJBUgIQ cpGXWD3q1uP3DzGVVzlUESUwuiufJ07tPXf2dSUTvBYk18Og7Jl6lJkMnM9fbzkcL5dqGWU6DpPXr xOaSetvpdMY3icLh2vXT4hWH5iCVNovYMM+jCUzUTPCH/gz5YI/1g5IcRoLrADs3q0aRqDMFeRSIU cX10/lY5xzkXaQzeZK9QC6s3QXocf28pJR9xTDe/aO5uQlccUUnudlWpawT7jHcdOvMGqDwOxvpdI CFCqmAYVEWkI21uLx1lw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1loSK4-004ipO-7z; Wed, 02 Jun 2021 14:58:20 +0000 Received: from youngberry.canonical.com ([91.189.89.112]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1loSJy-004inf-VA for linux-arm-kernel@lists.infradead.org; Wed, 02 Jun 2021 14:58:16 +0000 Received: from mail-ej1-f72.google.com ([209.85.218.72]) by youngberry.canonical.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1loSJx-0006Ci-NS for linux-arm-kernel@lists.infradead.org; Wed, 02 Jun 2021 14:58:13 +0000 Received: by mail-ej1-f72.google.com with SMTP id jz28-20020a17090775fcb02903dc26615f46so787472ejc.8 for ; Wed, 02 Jun 2021 07:58:13 -0700 (PDT) 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=752p4tr8om9PZTkMN+y5OaTny2tseRBiO4Qw5qPX/uc=; b=m/4FN+MAzgZ8uahCBujeqEWDjwO7GmKlZalAxQY3XoydQPBhq9s/HvTFIz7jdxSHY0 ZWs/ZggNLDhZjMDTwYc9Ff4hiWaNexUpP6yJfftIRfBorWjb7DOZZmoOUQ9Yh9b0MUYU yCD6yKSauD76iM+LLtwnZ7fbZWdOe4aR4GBek6267bhjVhVM5FwkU4KcFVBiQsEQSA0l +90ErTAdmzvG5d2IFwUKghWYVT+ZFJMufy2McBfhBCInZW2/Wjshelxy0p0XmSCZtpX4 MsDG7TfSexeEkxtdLlpMLUwOz7xEZLiCDViQvNFI/B5Bvy3sEpBzQ2gU9T+5LDXtnyMM hafQ== X-Gm-Message-State: AOAM533aXU4EZwjPN4Z1wpaPgh6BXdi8uu3UaIg3I6/bwKW0Uy4sdRDJ KcdBCJ0V8YWm9rZ3eDUZE+V81S1X8wVgos6qbUhfDqNCtVR6PyUcMbvL2EDeMtKyPDI70Xq5Nu6 0M0qFEfq41jzaYx7xuvSzGBWp2ykqZwmhjahSCO46hkhlwZ3nLS8b X-Received: by 2002:a17:906:c0da:: with SMTP id bn26mr34977224ejb.437.1622645892871; Wed, 02 Jun 2021 07:58:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwkFWWKXUi9uF3fTYTqDvU90HNZjSch1pOOs5UUihZd7KkSvKKBSG8U5eE+iM6V9QT5ZvntNg== X-Received: by 2002:a17:906:c0da:: with SMTP id bn26mr34977219ejb.437.1622645892708; Wed, 02 Jun 2021 07:58:12 -0700 (PDT) Received: from [192.168.1.115] (xdsl-188-155-185-9.adslplus.ch. [188.155.185.9]) by smtp.gmail.com with ESMTPSA id u15sm115179edy.29.2021.06.02.07.58.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 02 Jun 2021 07:58:12 -0700 (PDT) Subject: Re: [PATCH v2 00/10] arm64: tegra: Prevent early SMMU faults To: Thierry Reding , Will Deacon References: <20210420172619.3782831-1-thierry.reding@gmail.com> <20210601122646.GB27832@willie-the-truck> <6826d892-d1ac-e3b1-ebee-68392d11d7c5@canonical.com> <8c70f82f-0db9-2312-7fc4-c079899c25a0@canonical.com> <20210602114049.GF30593@willie-the-truck> From: Krzysztof Kozlowski Message-ID: Date: Wed, 2 Jun 2021 16:58:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210602_075815_055313_AFAED1DB X-CRM114-Status: GOOD ( 34.86 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Joerg Roedel , iommu@lists.linux-foundation.org, Jon Hunter , Nicolin Chen , linux-tegra@vger.kernel.org, Robin Murphy , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 02/06/2021 16:58, Thierry Reding wrote: > On Wed, Jun 02, 2021 at 12:40:49PM +0100, Will Deacon wrote: >> On Wed, Jun 02, 2021 at 12:44:58PM +0200, Krzysztof Kozlowski wrote: >>> On 02/06/2021 10:52, Thierry Reding wrote: >>>> On Wed, Jun 02, 2021 at 09:35:13AM +0200, Krzysztof Kozlowski wrote: >>>>> On 02/06/2021 09:33, Krzysztof Kozlowski wrote: >>>>>> On 01/06/2021 20:08, Thierry Reding wrote: >>>>>>> On Tue, Jun 01, 2021 at 01:26:46PM +0100, Will Deacon wrote: >>>>>>>> On Fri, May 28, 2021 at 07:05:28PM +0200, Thierry Reding wrote: >>>>>>>>> On Tue, Apr 20, 2021 at 07:26:09PM +0200, Thierry Reding wrote: >>>>>>>>>> From: Thierry Reding >>>>>>>>>> >>>>>>>> Probably best if I queue 3-6 on a separate branch once you send a v3, >>>>>>>> then Krzysztof can pull that in if he needs it. >>>>>>> >>>>>>> Patch 5 has a build-time dependency on patch 1, so they need to go in >>>>>>> together. The reason why I suggested Krzysztof pick these up is because >>>>>>> there is a restructuring series that this depends on, which will go into >>>>>>> Krzysztof's tree. So in order to pull in 3-6, you'd get a bunch of other >>>>>>> and mostly unrelated stuff as well. >>>>>> >>>>>> I missed that part... what other series are needed for this one? Except >>>>>> Dmitry's power management set I do not have anything in my sight for >>>>>> Tegras memory controllers. >>>>>> >>>>>> Anyway, I can take the memory bits and provide a stable tag with these. >>>>>> Recently there was quite a lot work around Tegra memory controllers, so >>>>>> this makes especially sense if new patches appear. >>>>> >>>>> OK, I think I have now the patchset you talked about - "memory: tegra: >>>>> Driver unification" v2, right? >>>> >>>> Yes, that's the one. That series is fairly self-contained, but Dmitry's >>>> power management set has dependencies that pull in the regulator, clock >>>> and ARM SoC trees. >>>> >>>> I did a test merge of the driver unification series with a branch that >>>> has Dmitry's patches and all the dependencies and there are no conflicts >>>> so that, fortunately, doesn't further complicates things. >>>> >>>> Do you want me to send you a pull request with Dmitry's memory >>>> controller changes? You could then apply the unification series on top, >>>> which should allow this SMMU series to apply cleanly on top of that. >>> >>> Makes sense and it looks quite bulletproof for future changes. Let's do >>> like this. I will apply your patch 1/10 from this v2 on top of it and >>> driver unification later. >> >> Okey doke. Thierry -- please let me know which patches I can queue. Having >> the SMMU driver changes in the IOMMU tree really helps in case of conflicts >> with other SMMU changes. As I say, I can put stuff on a separate branch for >> you if it helps. > > Given that the SMMU patches have a build-time dependency on the first > patch in the series, and the series depends on the unification series, I > think Krzysztof would have to pull the memory controller branch that I > have with Dmitry's work, apply the unification series on top and then > take patch 1 of this series on top of that. That's the state that you'd > have to pull into the SMMU tree to get the right dependencies. > > The SMMU pieces are the leaf of the dependency tree, so technically no > separate branch is needed, because I don't think anybody would have to > pull from it. However, a separate branch might make it easier to back > any of this work out if we have to. > > Krzysztof, I do plan on sending out a v3 of the unification series to > address the two cleanups that Dmitry and you have pointed out. After > that I can send out v3 of this series to fix the ordering issue that > Krishna had mentioned. After all of those are applied, would you be able > to provide a stable branch for Will's SMMU tree? Yes, I will provide a stable branch/tag. Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel