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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 14256C48BE5 for ; Tue, 15 Jun 2021 15:35:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E9673615A0 for ; Tue, 15 Jun 2021 15:35:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231688AbhFOPhp (ORCPT ); Tue, 15 Jun 2021 11:37:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55302 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230076AbhFOPho (ORCPT ); Tue, 15 Jun 2021 11:37:44 -0400 Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0901AC061574 for ; Tue, 15 Jun 2021 08:35:39 -0700 (PDT) Received: by mail-vk1-xa2a.google.com with SMTP id n25so1065230vkl.8 for ; Tue, 15 Jun 2021 08:35:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=12lusgJKqZ+mFXJMQojBCjBzeRiohhHShT1Rj6cPMlA=; b=KdTeL4xhOG1Ni08Mf6x0ZpT6rt9j9qQv+4GuFufpy9Ao2aplllacUO3i6KB3Pr9Rgk cjToMFZjWR8QRk/rF8v8/zAq0KQUiUUIut6Il99rIFXXsL0A6iRURQpQwmP7JLNU9dGV 16lYhsXZqzVIHA6Nd1LZ3FHGpIGSUOztR2O2pGXx+032trMRf7rBFhneKGe4kPt95zFV R5FllI9cUcq7JTYkk0/oNUCDgZZyvZOQzcsEvNMaJTtmrS27nJcDGWbx0svynNj/g3zd 0znOSVeB+ZGyrQQqpqmr5qg1dHMHomeu919bunVoA21KJ2U2g4qqzTFVRE0g/iSNt6nA khZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=12lusgJKqZ+mFXJMQojBCjBzeRiohhHShT1Rj6cPMlA=; b=VXOWKwD0MmapJfqxd6wvkwQWKleB4A6oPrYWVJJmTBLcFGgceEXLqqnfC2DuPBrL1y kjIQltcF5MNaHQs/LxyH6buflG5JujD94VbN5fNwTLJHZyQK/C1BtQIdgzD2eJdOh8Pc aauQKhPjvkJKZ1mCotJpXu6Ug2qdBZQ6OlgQ9FRGIXBdpKGJ5D/I8+nNpvP/jZDLGM0Q G0c6wGg6XBii6WqEN+xgJDVcTbE64MVUAOp26UUU2KOJqm6atPU/2HRldSLoq3OWxtuq 46BokX76CCmQOOiaphu5gNEEIZWArXJydMo809jNH+ZozefYRWQRt3VVNsR+FDMzX9VZ a7ew== X-Gm-Message-State: AOAM533+zkSWBTR4mgAQC7lo4N/ztzgAztHqSpxZydWSAZavcXLxRe8i GXocpyldTLYMEkagsNNM0y6Db9hEk0L/O7ePefzmhw== X-Google-Smtp-Source: ABdhPJyEAEOe6I6qtvLHO5Hm3e/awBYGqKLv+Jhmw2CzujYFMTLYGKPub/BltgkGnQPNw58/mXrSs/TP1Z6+jggvyRM= X-Received: by 2002:a1f:3dd8:: with SMTP id k207mr4287282vka.7.1623771338193; Tue, 15 Jun 2021 08:35:38 -0700 (PDT) MIME-Version: 1.0 References: <20210611101540.3379937-1-dmitry.baryshkov@linaro.org> <20210611101540.3379937-3-dmitry.baryshkov@linaro.org> <20210615111012.GA5149@sirena.org.uk> <20210615152620.GH5149@sirena.org.uk> In-Reply-To: <20210615152620.GH5149@sirena.org.uk> From: Ulf Hansson Date: Tue, 15 Jun 2021 17:35:01 +0200 Message-ID: Subject: Re: [PATCH 2/2] PM: domain: use per-genpd lockdep class To: Mark Brown Cc: Dmitry Baryshkov , Stephen Boyd , "Rafael J. Wysocki" , Kevin Hilman , Greg Kroah-Hartman , Bjorn Andersson , Linux PM , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 15 Jun 2021 at 17:26, Mark Brown wrote: > > On Tue, Jun 15, 2021 at 04:55:24PM +0200, Ulf Hansson wrote: > > On Tue, 15 Jun 2021 at 13:10, Mark Brown wrote: > > > On Tue, Jun 15, 2021 at 12:17:20PM +0200, Ulf Hansson wrote: > > > > > Beyond this, perhaps we should consider removing the > > > > "regulator-fixed-domain" DT property, as to avoid similar problems > > > > from cropping up? > > > > > Mark, what do you think? > > > > We need to maintain compatibility for existing users... > > > Normally, yes, I would agree. > > > In this case, it looks like there is only one user, which is somewhat > > broken in regards to this, so what's the point of keeping this around? > > Only one user in mainline and you were just suggesting removing the > property (you mean binding I think?) - at the very least we'd need to > transition that upstream user away to something else before doing > anything. Yes, I am referring to the binding. Let's see where we end up with this. My concern at this point is that it could spread to more users, which would make it even more difficult to remove. Kind regards Uffe