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 EED3EC4332F for ; Wed, 23 Nov 2022 10:55:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236923AbiKWKzZ (ORCPT ); Wed, 23 Nov 2022 05:55:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55618 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237013AbiKWKy7 (ORCPT ); Wed, 23 Nov 2022 05:54:59 -0500 Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D68DE134115 for ; Wed, 23 Nov 2022 02:43:47 -0800 (PST) Received: by mail-lf1-x135.google.com with SMTP id c1so27560837lfi.7 for ; Wed, 23 Nov 2022 02:43:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:references:cc:to:from :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=rT3zcQTdiqIKVUqVpCnTTdj/c8j+Nk1Lz6ur5IXMJOA=; b=EMg9kUC1+ELdZg4dG/mu5U5HWqIDh2zj38EIiGc6PXb/Tty6+0y+tysqOb/UfVwY5V x+jqoABT4qC7m+d2D+qZIuJGDBvjwhIaki6eJzLfUwG9UPwBezsZC+HHNrtLOhAPsi9G n+oMu50QndXYVCXfr1tDzmvtdQ/IN29K0FVG5FYtUED/0g/8utJpV1zn7xcTCYMgGR4J l10oL16UVwKsVpgczL+gjXjSw+ZYXMtOb0ixi1qk8ayBVOo931PfdomB9ADSW1LF3pWf 9aYRiIeKAAao8GdC7AA84m8EOfzTsjpSc9fTW4gFHYo+/ifquaDVtOKCeK+NQtAqyJwS yi8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:references:cc:to:from :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rT3zcQTdiqIKVUqVpCnTTdj/c8j+Nk1Lz6ur5IXMJOA=; b=rIdCtsirvfolWJyory434qCToVF2YA7JW3Fyb5Cwpevn6uwtGXn4jW6GnnFtNfGIYx Gb+EWSms4c+jXP2kEF11FdDg8lo9icGJ4PJS7/nZ7EKV6fvVzuPI0BJijs0WkN4N2xrn ggUpY9H7LdCkOyFw8V3UabgSY3GI2dXjL7SZvObHIyo/90pvKWVfEqGgyarqHRc+hLGl 8CFwTnbbCkZdkUkeBG7krDnGA0zHZRT/RYfSVWOILhIQ7CbOywEA7ZA/npMBpMDLc4Qt DHcaKVuoM5FHJjESnxk6FCnS6iXUSfcHcJrtfGRfUefs4S9YiyiEQsXMoyv3N0TA05Ix g8Yg== X-Gm-Message-State: ANoB5pkUdMTxAX8apIWT4/eO/BQTP4bH19WwYODf4IPa3/JFzj4YCtf8 R5Kq7v4xbOyUtSzKszZEp4h4pQ== X-Google-Smtp-Source: AA0mqf6VYlXsQaHR4cbFjaN5eV+7fCtvNBbhQ7J0rfydPqrSvO6VpNFGGC42MRUUxP2ujuSxtVP06g== X-Received: by 2002:ac2:4558:0:b0:494:6bb2:485f with SMTP id j24-20020ac24558000000b004946bb2485fmr3581244lfm.451.1669200226234; Wed, 23 Nov 2022 02:43:46 -0800 (PST) Received: from ?IPV6:2001:14ba:a302:5f12::1? (dzpbg0ftyyyyyyyyyyyyt-3.rev.dnainternet.fi. [2001:14ba:a302:5f12::1]) by smtp.gmail.com with ESMTPSA id g4-20020a056512118400b0049e9122bd0esm2037454lfr.114.2022.11.23.02.43.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Nov 2022 02:43:45 -0800 (PST) Message-ID: Date: Wed, 23 Nov 2022 12:43:45 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: [PATCH v8 0/4] phy: qcom-qmp-ufs: add symbol clocks support Content-Language: en-GB From: Dmitry Baryshkov To: Andy Gross , Bjorn Andersson , Konrad Dybcio , Vinod Koul , Kishon Vijay Abraham I , Rob Herring , Krzysztof Kozlowski Cc: Johan Hovold , Philipp Zabel , linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, devicetree@vger.kernel.org References: <20221123104215.3414528-1-dmitry.baryshkov@linaro.org> In-Reply-To: <20221123104215.3414528-1-dmitry.baryshkov@linaro.org> 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 23/11/2022 12:42, Dmitry Baryshkov wrote: > Register UFS symbol clocks in the Qualcomm QMP PHY driver. Some of the > platforms (msm8996, sc7280, sm8350/sm8450) expect them to be defined (to > be used as GCC clock parents). > > Changes since v7: > - Rebased on top of phy/next > - Renamed the clock registration function (Johan) > - Dropped rogue qcom_qmp_ufs_ops (Johan) > - Fixed the comment following Johan's suggestion. Ugh, this went total crazy with me sending the patches from the wrong commit. Please excuse me, I'll send v9 instead. -- With best wishes Dmitry