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=-4.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,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 7BEE4C352A4 for ; Wed, 12 Feb 2020 23:03:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4FD042168B for ; Wed, 12 Feb 2020 23:03:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1581548620; bh=fU30PkEF5AzebTofCICkBipjj6UxPaHZSLK931dkXp4=; h=In-Reply-To:References:Subject:From:Cc:To:Date:List-ID:From; b=X59MPC47ynkrwXvIIEvD5j8IMCEQsNKnrrS0IPCMBbyxKhOXd14OvlSTJGZOuF4ID I2Zn844caE/QCR5T0HyPRdPo05nLDiWmc2DcQQz/GpFjGlF8v3M4EwqkOnTsY12IGg tNSp/WmZvwGuARDlYhxsLFasTbINwrzUj1m4Jz7w= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729103AbgBLXDk (ORCPT ); Wed, 12 Feb 2020 18:03:40 -0500 Received: from mail.kernel.org ([198.145.29.99]:46802 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728447AbgBLXDj (ORCPT ); Wed, 12 Feb 2020 18:03:39 -0500 Received: from kernel.org (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2E3DE21569; Wed, 12 Feb 2020 23:03:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1581548619; bh=fU30PkEF5AzebTofCICkBipjj6UxPaHZSLK931dkXp4=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=E83cguvoAQC5HFH0GrNnwtJUxEEOFnZ7gorksbX3QSdB/S1P8myeRnzTqSyM7quor ygBTInUWmYxUSatmw6no5B5HC/oZ84l/WoepqBi7Wb92GnlhxKuQLEYqXYzBLsFyS3 TtqFSzDf9CCSoabSoU6ptcoTv3lNDP4HgjnL6H00= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <1581423236-21341-1-git-send-email-tdas@codeaurora.org> References: <1581423236-21341-1-git-send-email-tdas@codeaurora.org> Subject: Re: [PATCH v1 1/2] clk: qcom: videocc: Update the clock flag for video_cc_vcodec0_core_clk From: Stephen Boyd Cc: David Brown , Rajendra Nayak , linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, Andy Gross , devicetree@vger.kernel.org, robh+dt@kernel.org, Doug Anderson , Taniya Das To: Michael Turquette , Taniya Das , robh@kernel.org Date: Wed, 12 Feb 2020 15:03:38 -0800 Message-ID: <158154861845.184098.5172409402237427332@swboyd.mtv.corp.google.com> User-Agent: alot/0.9 Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Quoting Taniya Das (2020-02-11 04:13:55) > The clock disable signal for video_cc_vcodec0_core_clk is tied to > vcodec0_gdsc which is supported in the HW control mode. Thus turning off > the clock would be taken care automatically when the GDSC turns OFF by > hardware and clock driver does not require to poll on the CLK_OFF bit. >=20 > Signed-off-by: Taniya Das > --- Applied to clk-fixes