Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3738804pxf; Mon, 29 Mar 2021 10:03:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzS3/shR8smaOw8CyW1IOwlmfhuQOxHUF16sRbyC1+V2HnHvaJJXPTnhoTMjtSce2j3SP2+ X-Received: by 2002:a17:906:1985:: with SMTP id g5mr29070003ejd.285.1617037404565; Mon, 29 Mar 2021 10:03:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617037404; cv=none; d=google.com; s=arc-20160816; b=QCqjHWTVj0yJqVTkI+/YuEcrbYD89lTH5MmYOSdqZRrqnPE57JPU9M2/zFyU+1CXpF akWlnF13uZ6GdPkuMg3h+yMUPHJHGnw0l38OkX2R1EGs11Vj26QdRDs4dDLRhg8FFQe6 ehlLHPdA5htNdnH3t5H4+nxVq5QreJJatyctwKnr1YPxsexue6ay+rqbze8rF7DQsdj/ vJpm2OEn4d4M/jmt8a/b6UlyLMcoYKKOnuCAl7IlMgs7cGpe5SNAtZ+qXHc7PkvEQVYP qxP5q0AkxwlNuFF82oD1Y35Vie0CWtK8S47rWvTe8aj9DEhP90AmNJ1pKKaLJQaWnCVn v93g== 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=3KaU2X8BYBo2iEYrCYnDX7Io7zwEGngt8bXiDSOA3dU=; b=tF4QlOLA5AXcmgdE0Mai0h/WM5KYD9JAzyVcaNF6MLQEMWIKe1RQQybs0a0U/BC7xf HkxdvcSIy3wsv5vHCR0IEoD5LW5vEwwWchmH0elAMZ/IF9e27IvqycjlLSZH9nX5iQQ8 PIjpqrm3K3Sb7NWm5MtKdbDzlObIBGGe7AxAC62kS+1izbTBdYVi5oyNps/2IC+5zXaR e7q5oKaOS0TQYZIDk01xardpUA+FONouEUoUNKxobUJ2tmUkBP/mzRJrD9Pe1rFk6wIN gHvrFLD+A09sGeiogc+Kfylwyk+SizUyoIfpzYcQjVnFyW/z8biMGVlCUWkLHFvH3pyg pbkQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Kg42A+C8; 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 j20si13518326ejs.411.2021.03.29.10.03.01; Mon, 29 Mar 2021 10:03:24 -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=Kg42A+C8; 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 S230475AbhC2RCF (ORCPT + 99 others); Mon, 29 Mar 2021 13:02:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50350 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229479AbhC2RBv (ORCPT ); Mon, 29 Mar 2021 13:01:51 -0400 Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8E635C061574; Mon, 29 Mar 2021 10:01:51 -0700 (PDT) Received: by mail-pj1-x1034.google.com with SMTP id gb6so6324883pjb.0; Mon, 29 Mar 2021 10:01:51 -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=3KaU2X8BYBo2iEYrCYnDX7Io7zwEGngt8bXiDSOA3dU=; b=Kg42A+C8lwb0lncwa2RQMG/aGsCwIFedHnSNQ5tAzBoKpV7+4z32DzKBLqagztyFcR 5foEL4IWF1C2q3jlXjdsh7nliv2yDPKhtPOIpnPICy4j8l0aMeZoXyAQyrTmUcL32PAB b3XxiYzpReNucgoVjwzRn+OFrqbtj07XYipNt6AhQ8uemiICKdx+rPfhBi2AfDs7HQ4J xWAdzSQlZGkbN7nHm5QkqXUCiO9A7gorZVuGXwdS8EyAeO9CrvEH8NBGLWktcPooXpeJ q4LxzdRWU9wkxHOF0Mhl0aJKJy2nDI6nVYe6jeAVrr5lgPsx+AOfGkRFnsCHsCSEmOHH Re0Q== 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=3KaU2X8BYBo2iEYrCYnDX7Io7zwEGngt8bXiDSOA3dU=; b=Pw7docRGW/AJJl653krYWmO7Ldv5byPNrMVn4FY7Rk8kOaT7oGwPmJO9q+hZVhzcDh O7Y1NeylzqgELkM+N7+R1OK0TMWub61QrtIUWLOyiOJoTBITqerP2LNYua+JHf/+BhJw +aHyjG3lE4fIiF6Y+JCj4WhGoj4WxwlNd5TicknvmYvwALkp/MG7UjOp0Y+LsE5+hjF1 vNKQMBXPHi1kUQ66N36HWpq13euhqeBhjGvufpOT0FeUjRB5yxFQQeCmUQ5Tn1qn98gg 1c7CD5+yFyaErAmxeWF84WqSf7FSgeu5fOfYs9TgUtUs8Acf44fu3ua2sBn3SdnFfpfA z6Ig== X-Gm-Message-State: AOAM532HgDxETakxLXCrC/PvUc5XQ86cVe1BMwgPvEaEQFnDQPzpKOyM HOd0INU2snlEq/mAaJ0gsSJ+mVkOask= X-Received: by 2002:a17:90a:bb81:: with SMTP id v1mr62162pjr.123.1617037310528; Mon, 29 Mar 2021 10:01:50 -0700 (PDT) Received: from [10.67.49.104] ([192.19.223.252]) by smtp.googlemail.com with ESMTPSA id w3sm43671pjg.7.2021.03.29.10.01.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 29 Mar 2021 10:01:50 -0700 (PDT) Subject: Re: [PATCH v5 2/2] PCI: brcmstb: Use reset/rearm instead of deassert/assert To: Lorenzo Pieralisi Cc: Jim Quinlan , Bjorn Helgaas , linux-pci@vger.kernel.org, Nicolas Saenz Julienne , bcm-kernel-feedback-list@broadcom.com, james.quinlan@broadcom.com, Rob Herring , Bjorn Helgaas , Philipp Zabel , Jim Quinlan , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , open list References: <20210312204556.5387-1-jim2101024@gmail.com> <20210312204556.5387-3-jim2101024@gmail.com> <20210329161040.GB9677@lpieralisi> <71903454-c20c-31f7-aaee-0d05eb22db7f@gmail.com> <20210329165847.GA10454@lpieralisi> From: Florian Fainelli Message-ID: Date: Mon, 29 Mar 2021 10:01:48 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <20210329165847.GA10454@lpieralisi> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/29/21 9:58 AM, Lorenzo Pieralisi wrote: > On Mon, Mar 29, 2021 at 09:50:13AM -0700, Florian Fainelli wrote: >> On 3/29/21 9:10 AM, Lorenzo Pieralisi wrote: >>> On Fri, Mar 12, 2021 at 03:45:55PM -0500, Jim Quinlan wrote: >>>> The Broadcom STB PCIe RC uses a reset control "rescal" for certain chips. >>>> The "rescal" implements a "pulse reset" so using assert/deassert is wrong >>>> for this device. Instead, we use reset/rearm. We need to use rearm so >>>> that we can reset it after a suspend/resume cycle; w/o using "rearm", the >>>> "rescal" device will only ever fire once. >>>> >>>> Of course for suspend/resume to work we also need to put the reset/rearm >>>> calls in the suspend and resume routines. >>> >>> Actually - I am sorry but it looks like you will have to split the patch >>> in two since this is two logical changes. >> >> I do not believe this can be easily split, since there is currently a >> misused of the reset controller API and this patch fixes all call sites >> at once. It would not really make sense to fix probe/remove and then >> leave suspend/resume broken in the same manner. > > Right - I was reading the previous versions of the set, it makes sense > to keep it in one logical change. > > Do you want me to take it or you prefer an ACK so that it can go via > a different tree ? I would be comfortable with you taking this via the PCI driver trees, we would want an Ack from Jens that he is okay with taking the ahci_brcm.c change as well through your tree. Thank you! -- Florian