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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id AECEFC433EF for ; Fri, 10 Dec 2021 20:32:53 +0000 (UTC) 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:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date: Message-ID:From:References:Cc:To:Subject:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Owner; bh=hmcW7+UV4/vE4ItgT6NzjeUQkW8pr+simcPCzp4sZok=; b=zx+kre5USNsfPPYD6OVKxT/NIR L3KUPcHC3ZGuj6UqJL2/FPhjNfydM+UtX/EFs1nOiloVmRi5mxsad4QA5k07b+EWknXlGjHCBl1Nv Gj2TDC/rDBqFWY3wClW9oYQ/GcUFFhAqEknHGowzWBC/5fEBW0GScZGFeg9DlKAE95BDipTjXbHyI RfPofPqccTCwYfmQX3M5BwUs7oytGNAzAEs9GdDowBLR9CDQ9MQ44R37IBx7hEeXf0sbJQe+7aHw2 il/3kugAmMRECwfiAbjIcMhcwQVoPjUhgFNHCDcFbnT9RbG4TZpxMhSLGclFVolzg3ocf/WDKTMRo TRPvAz4Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mvmY5-003lR8-Bo; Fri, 10 Dec 2021 20:31:21 +0000 Received: from mail-pl1-x62a.google.com ([2607:f8b0:4864:20::62a]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mvmY1-003lQQ-17; Fri, 10 Dec 2021 20:31:18 +0000 Received: by mail-pl1-x62a.google.com with SMTP id v19so7009334plo.7; Fri, 10 Dec 2021 12:31:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=jw1R+y/hcHxw2PT0p++dPCEF0COGjgzOAfMrHqXYnmM=; b=Bj+eXpOd8SzmrJr7YedQ/prWz5Nhb/UwYzn4LYbYC36INmkJgXTghx2tdmOgL51KpZ /NMu5KRvGw6V/m3A81JqHlgtdx0VwVYcS1qmRcwsxnxxQ1mctQXAHoAIGvp5cplvrgLu oGsDF+VTRyiY7OIaz/t2SwS32w4Ab/92XtjcZ8UgvbUQIUjp9d2JJa0h1oQDDpVg0SnS 5WcE6IcGXwGx3JcCw4uuBDKQoJ1FDnoNeYvK1/D7i5mp3wCbZIMdFTM5JrZCkKMJWavw v6Ig7kgp4cQxi9sQs4wAAf/gEPRhgqNdInYf9Hw6F6bEGgAPnNV8KBREpolxKgqZe2gv 8E/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=jw1R+y/hcHxw2PT0p++dPCEF0COGjgzOAfMrHqXYnmM=; b=zdVR29wyXuhZQzg+HlqmyYs8g3+1dQEpfgWTBQ1onXx5UCkiT50JvF9WqrN4Pd+1Hs zQjN8gxy4Py6ez4P+KMjpVOHiTvhx+HMGNEMW37gK58/10yrtEQySpCPlv5Ifr5cgxfE krUQduYw01iK9rwnWzq/Cvp7nVxZ72OARjXjqtBoAgB9lJRY0g9h/23msBLyinMpJPF0 KcVr5a4vE+GNyeVzb/4ykM7TXBy81/eC53ZW4kzkFhiz+PqQ97KrKDIrZ9z9Ike24sPR PUZeXpCM09jHAji9nm+fUrPXurcEilooYHLJSsCgXG3sajYhHpy7SzM9txIs/eOgFigD k1zg== X-Gm-Message-State: AOAM5336+gbIM1fn+blXImD+Y7V6z4/gL5NWb4VyLIyWfhx666MUrvgl gQ8jnHzYNoOHbarBU46KGHk= X-Google-Smtp-Source: ABdhPJxTn8cdjm0nDrmj3G2/X5TV7UORnvYHQW3Jxaa+vjIKePL9ujp9yEQXIZ3Pnlrd8hZuQYmxdw== X-Received: by 2002:a17:90b:1e07:: with SMTP id pg7mr26302078pjb.185.1639168276271; Fri, 10 Dec 2021 12:31:16 -0800 (PST) Received: from [10.67.48.245] ([192.19.223.252]) by smtp.googlemail.com with ESMTPSA id s19sm4434823pfu.137.2021.12.10.12.31.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Dec 2021 12:31:15 -0800 (PST) Subject: Re: [PATCH v10 0/7] PCI: brcmstb: root port turns on sub-device power To: Rob Herring , Jim Quinlan Cc: linux-pci@vger.kernel.org, Bjorn Helgaas , Nicolas Saenz Julienne , Mark Brown , bcm-kernel-feedback-list@broadcom.com, james.quinlan@broadcom.com, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , =?UTF-8?Q?Krzysztof_Wilczy=c5=84ski?= , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , open list , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , Saenz Julienne References: <20211209211407.8102-1-jim2101024@gmail.com> From: Florian Fainelli Message-ID: Date: Fri, 10 Dec 2021 12:31:10 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 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-20211210_123117_126836_5B4FE1C2 X-CRM114-Status: GOOD ( 23.36 ) 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: , 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 12/10/21 10:44 AM, Rob Herring wrote: > On Thu, Dec 09, 2021 at 04:13:58PM -0500, Jim Quinlan wrote: >> v10 -- Bindings commit example: in comment, refer to bridge under >> controller node as a root port. (Pali) >> -- Bindings commit example: remove three properties that are not >> appropriate for a PCIe endpoint node. (Rob) >> >> v9 -- Simplify where this mechanism works: instead of looking for >> regulators below every bridge, just look for them at the >> bridge under the root bus (root port). Now there is no >> modification of portdrv_{pci,core}.c in this submission. >> -- Although Pali is working on support for probing native >> PCIe controller drivers, this work may take some time to >> implement and it still might not be able to accomodate >> our driver's requirements (e.g. vreg suspend/resume control). >> -- Move regulator suspend/resume control to Brcm RC driver. It >> must reside there because (a) in order to know when to >> initiate linkup during resume and (b) to turn on the >> regulators before any config-space accesses occur. > > You now have a mixture of 'generic' add/remove_bus hooks and the host > controller suspend/resume managing the regulators. I think long term, > the portdrv is going to be the right place for all of this with some > interface defined for link control. So I think this solution moves > sideways rather than towards anything common. > > Unfortunately, the only leverage maintainers have to get folks to care > about any refactoring is to reject features. We're lucky to find anyone > to test refactoring when posted if done independently. There's a long > list of commits of PCI hosts that I've broken to prove that. So it's > up to Lorenzo and Bjorn on what they want to do here. After version 10, it would seem pretty clear that we are still very much committed to and interested in getting that set merged and do it the most acceptable way possible. Common code with a single user is always a little bit of a grey area to me as it tends to be developed to cater for the specific needs of that single user, so the entire common aspect is debatable. I suppose as long as we have the binding right, the code can change at will. Not trying to coerce Bjorn and Lorenzo into accepting these patches if they don't feel comfortable, but what about getting it included so we can sort of move on from that topic for a little bit (as we have other PCIe changes coming in, supporting additional chips etc.) and we work with Pali on a common solution and ensure it works on our pcie-brcmstb.c based devices? We are not going to vanish and not come back looking at this. -- Florian _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel