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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0C7F1C54EE9 for ; Thu, 8 Sep 2022 14:49:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232395AbiIHOtE (ORCPT ); Thu, 8 Sep 2022 10:49:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54038 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232083AbiIHOtD (ORCPT ); Thu, 8 Sep 2022 10:49:03 -0400 Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 59209E0B0 for ; Thu, 8 Sep 2022 07:49:02 -0700 (PDT) Received: by mail-lj1-x234.google.com with SMTP id y29so7591743ljq.7 for ; Thu, 08 Sep 2022 07:49:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date; bh=PfSELVZI7eWUgnlVdrZZBJM8x1KhGoZtl9ybjhJG520=; b=FMEreVe18gRsXa2sOJRkMJj3INTHssHJb5O6Iraqo6GO1rP4BxA4UpRR5FlZxPsT6B dk9MP7cUybAR/PEi7HlHfv5VlBAScbSi6W9yCZqUHhjGNFEAUecunDD1vINrFWe3bqeh HXPNZa/H+d2y1BgSE4/XcMnQMeVTe8NT/mGfTYW1tq2L8lwxdzrH0W4zO2qqAd7ZnrxV eEjfQsynMZyl6TIhEO9hgsG2SZttGDvAoTE8Cg7vuZETQ2VGDBGx3MnG0ALzVkHJLt2B cMgi6Wx6blDQA/kBj80YgPaWHMucD+Uzy8azxdDk0s/dpNrYfpMKutOCAaN7Hn10NPxi MaFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date; bh=PfSELVZI7eWUgnlVdrZZBJM8x1KhGoZtl9ybjhJG520=; b=EG9nF5DTGOVdr6l7rkHi0XDgRZ6GpV6nI3NCp+65m0VjOf2jdkwMHwV1jmOFKM2Tsc CZ8cRs3RNCU5B4y5JHVw/ZfcHKIreztNC0W4DozfEhI6kleU7OoWMFOOy3qQ7BQvkgus tD/w3oQwX2y4YxfpnyF+EoTYdMQ28dpcIZzRu4GsaJCedN1n/gGmOTyvpw6Z2n9lMoD9 aVhusiAIYUXa4MC/TNeB80XyPx1yzy55/NAaBITnziU0edMwtDcQdHAt3xnVAnTk1E7C +4019YSWC0ELi2tgvOl02Kmd3ilKL8OTp+mQsFHdWozDABJoZ1t387FY//MBdwe/RcgM c4PA== X-Gm-Message-State: ACgBeo0NvTPPyLOe9qoiOJ/+lNU0NJSFW8s8Fv48cIp7mW8Qlf7GN0kU UEROeZ4oW/YHAUHVUI93eADFsQ== X-Google-Smtp-Source: AA6agR5qPzFhsQC5cI+nNt7o4Yt3qT2K8dukdCCbI0GateP+zD2zZq5d2Lz+38dWB/0Wa685d6NEUA== X-Received: by 2002:a2e:9241:0:b0:26b:daf1:293b with SMTP id v1-20020a2e9241000000b0026bdaf1293bmr843569ljg.71.1662648540749; Thu, 08 Sep 2022 07:49:00 -0700 (PDT) Received: from [192.168.0.21] (78-11-189-27.static.ip.netia.com.pl. [78.11.189.27]) by smtp.gmail.com with ESMTPSA id u14-20020a05651220ce00b004947fcf0c0bsm3055589lfr.281.2022.09.08.07.48.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 08 Sep 2022 07:49:00 -0700 (PDT) Message-ID: Date: Thu, 8 Sep 2022 16:48:59 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: [PATCH v3] regulator: dt-bindings: qcom,rpmh: Indicate regulator-allow-set-load dependencies Content-Language: en-US To: Mark Brown Cc: Doug Anderson , Andrew Halaney , Andy Gross , Bjorn Andersson , Konrad Dybcio , Liam Girdwood , Rob Herring , Krzysztof Kozlowski , linux-arm-msm , LKML , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Johan Hovold , Johan Hovold References: <20220907204924.173030-1-ahalaney@redhat.com> <168cde58-d061-97e7-54a5-5d3cccf3ce22@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 08/09/2022 16:38, Mark Brown wrote: > On Thu, Sep 08, 2022 at 04:29:29PM +0200, Krzysztof Kozlowski wrote: > >> Sorry, I don't find it related. Whether RPM has modes or not, does not >> matter to this discussion unless it sets as well allow-set-load without >> the mode... and then how does it work? In current implementation it >> shouldn't... > > It works perfectly fine, if the driver has a set_load() operation then > we call that and don't do anything to do with modes. Ah, I see now set_load() in drms_uA_update() in first if-arm. Makes sense I guess. Best regards, Krzysztof