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 2B4FEC433F5 for ; Mon, 31 Jan 2022 16:16:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1380186AbiAaQQB (ORCPT ); Mon, 31 Jan 2022 11:16:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33190 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1380174AbiAaQP6 (ORCPT ); Mon, 31 Jan 2022 11:15:58 -0500 Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3A56FC06173D for ; Mon, 31 Jan 2022 08:15:58 -0800 (PST) Received: by mail-lj1-x22b.google.com with SMTP id e17so20118743ljk.5 for ; Mon, 31 Jan 2022 08:15:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=PAJsiarXhqLynLw8D9oX/LriyOgm/RU72Cl9jucAmp4=; b=v3ZkRrFDlZs2mIz3bFyv/Y0d/v3qLb1rif8VBO0qXmQwMjhx+gev5Dlw3gDkpaeJRe 8dnrQCXDqCdM5WRwH3QrJo2hPz5WLW5lSixO+zoWOzhcpFMyduzdBl/k2TIOgnnUy6qp L2d4t6zyfkAvzI4LaRR7utS9BtQSwYTsMZTF5CYcYlx7eeKC+b4A2ddw13I1TQvF4RQT A4uZg7pqYZbqvGGHHqtp/PB2iyQE4z/QLGC3BNdcgM3evN74/4mRmT/5wdoizV8EIZQR 166XKN+zyZ2M4+Z3JYoNuMtasqtm+1czdarWcqRJc/vjDH2LuqM7juCVsHYaMCDPWofi ierg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=PAJsiarXhqLynLw8D9oX/LriyOgm/RU72Cl9jucAmp4=; b=j0L6CJU5aHGCpj1vpX5Xt8HewoVyZ0a/2zPSd5uuV2HK7z6QJxffaBeTbfGxRrzq6A Xmj9Z6FnjHfn58iGOqLwjI7OQQ20qDFJ2omyGlU3pHmi7aZsttb4rpDxPhu2QpboI051 0lDOa8qf+8cjj8DIWIir8JsFlRH1c9na4jJtnUNbrsXe59KdZhQihi9k/jLo7YKhyW/W k6//zzSP+4NdRdqvWQXixaNV8ZxoQXQSPk6UQQxH/sFrO6phn8OsFPSv5akXrhgHYl1P 0tN+3u0KMrhN5SgRwcwFlABUn+eFwhBAHMSWtBOGRFWkMUnYyRTTrKScnymOeApZEjUa u11A== X-Gm-Message-State: AOAM533OxRNDj2rkCV4uZkShjJNb9d/vnJfJfSq8AzqePNmXVDDXuVHq 2yttebdUOm4/WVjJX5TmifgE/g== X-Google-Smtp-Source: ABdhPJwewMmRrBwkubc+o6bfPzhnxUBAGcHo8KgbJc+QrmnKzTqWfh0QHTVz5P55+AvuKi8MkqGljQ== X-Received: by 2002:a2e:b7d6:: with SMTP id p22mr13954610ljo.182.1643645756531; Mon, 31 Jan 2022 08:15:56 -0800 (PST) Received: from [192.168.1.211] ([37.153.55.125]) by smtp.gmail.com with ESMTPSA id a7sm3158253lff.44.2022.01.31.08.15.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 31 Jan 2022 08:15:55 -0800 (PST) Message-ID: <266f6609-94c9-704c-548c-14351a05679e@linaro.org> Date: Mon, 31 Jan 2022 19:15:55 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH v7 7/8] clk: qcom: dispcc-sm8250: stop using mmcx regulator Content-Language: en-GB To: Bjorn Andersson Cc: Andy Gross , Rob Herring , Stephen Boyd , Taniya Das , Jonathan Marek , Michael Turquette , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org, Bryan O'Donoghue , Mark Brown , Ulf Hansson , linux-kernel@vger.kernel.org References: <20210829154757.784699-1-dmitry.baryshkov@linaro.org> <20210829154757.784699-8-dmitry.baryshkov@linaro.org> From: Dmitry Baryshkov In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 07/10/2021 18:48, Bjorn Andersson wrote: > On Sun 29 Aug 08:47 PDT 2021, Dmitry Baryshkov wrote: > >> Now as the common qcom clock controller code has been taught about power >> domains, stop mentioning mmcx supply as a way to power up the clock >> controller's gdsc. >> >> Signed-off-by: Dmitry Baryshkov >> Reviewed-by: Bjorn Andersson > > Once we merge these, I expect that the boards will start crashing if > the kernel is booted using an existing DTB? > > Is it okay to just merge the first 6 patches in the series now and > postpone these two until we've had the dts change sitting for a while? Bjorn, the changes 1-6 went into 5.15. I suppose it's time to merge the last two patches? > > Regards, > Bjorn > >> --- >> drivers/clk/qcom/dispcc-sm8250.c | 1 - >> 1 file changed, 1 deletion(-) >> >> diff --git a/drivers/clk/qcom/dispcc-sm8250.c b/drivers/clk/qcom/dispcc-sm8250.c >> index 108dd1249b6a..cf0bb12eb6e1 100644 >> --- a/drivers/clk/qcom/dispcc-sm8250.c >> +++ b/drivers/clk/qcom/dispcc-sm8250.c >> @@ -1129,7 +1129,6 @@ static struct gdsc mdss_gdsc = { >> }, >> .pwrsts = PWRSTS_OFF_ON, >> .flags = HW_CTRL, >> - .supply = "mmcx", >> }; >> >> static struct clk_regmap *disp_cc_sm8250_clocks[] = { >> -- >> 2.33.0 >> -- With best wishes Dmitry