Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp596775ybm;
        Wed, 27 May 2020 03:21:15 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJyGXuAeJgqAO24zgikrEKtM9vxH6bkygB8vyuWa90iN+tFDofh0e9h8vn46NSPa7E57Re+2
X-Received: by 2002:a50:ace4:: with SMTP id x91mr23200281edc.361.1590574875461;
        Wed, 27 May 2020 03:21:15 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1590574875; cv=none;
        d=google.com; s=arc-20160816;
        b=Yn66/IGD3WnX6s7HaVYUJysEpV10AfGVrfFxUjAnKSmhOS0ZYU5agcl2th3Tae/2VS
         GjEIOxtyoaHliTC0cdUmw5aLU9CP0kRqAvmqoybPeMMKgeigm1Dlh7KMOUDvwZbUk2XQ
         5mPtJvQ8lkAwEqByFzFR+vPPddczoExHE5lN7cHIixmVZHU1pW/AnyuEulpTS5NhPpBc
         2jTajRTYNJ66BQdH85UOcLDF24V/wI9Ty7NlfPVt0Pe1aaYi6HidBhKEnm5dNVNbhi4j
         XwlJKnSMhpsYQUAFQSurxdeIC5sAFE9sIQU2xaxyEDlMqDexx/tTq8J72pt2Mg4xMdQa
         bkgg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:user-agent:message-id:date:to:cc:from
         :subject:references:in-reply-to:content-transfer-encoding
         :mime-version:dkim-signature;
        bh=aV8A8sLjaDOj/7AanTn0RtlrOOIqsNKRPjRHYtq5vE0=;
        b=Q+f7ci1FBJug7DbSn+Gb1BuW8hs1YTwhIaOTNQevfmFSvuftLf1c9YJJzMnRWWaZ4o
         90tIIB9WYOEp128DfWQObcBiqnZRw126mg24awwVsK9qg04uAcMxvH0iPXFGGGkIJT+O
         aWzUvWGE31dOHLwP2VLW2DXMzHXfOOyGMwhMALDnzlrzD0zuv1gKpQCHbdj9vOPYWKqS
         84QDPvvr6OsCtviEI3vauLmeli58Hvu5idAxtpxcNlhsCLRdB7MhFQQGPY5DE+xohlN1
         AZ5ZcLtkNrQOPJjZAF34Ub3DQlwaUzNSqATPj8t2SQ6W3kcx2SYiyB2DFQ/a54S+n+Zp
         nj3g==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@kernel.org header.s=default header.b=o2RaZcvL;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18])
        by mx.google.com with ESMTP id f15si1716587ejd.359.2020.05.27.03.20.52;
        Wed, 27 May 2020 03:21:15 -0700 (PDT)
Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@kernel.org header.s=default header.b=o2RaZcvL;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1728707AbgE0Glj (ORCPT <rfc822;epopevad@gmail.com> + 99 others);
        Wed, 27 May 2020 02:41:39 -0400
Received: from mail.kernel.org ([198.145.29.99]:58290 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1725613AbgE0Gli (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 27 May 2020 02:41:38 -0400
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 49DA920776;
        Wed, 27 May 2020 06:41:38 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1590561698;
        bh=aV8A8sLjaDOj/7AanTn0RtlrOOIqsNKRPjRHYtq5vE0=;
        h=In-Reply-To:References:Subject:From:Cc:To:Date:From;
        b=o2RaZcvLGicVzdZAfBKYyCE0fgf5suFvdUtUTwKyZ7ckeSIcUDkYS9LY7YIwgBIxD
         HUEfkBOEtQbsQUFQFiIMPyyA/6q4t89VaDVJPT0YyS8qLgImWsmCfqdHiP3OF0AvFA
         4ZAQGOB94XhgaH13WSXjll1GEF9o0BqY4Toy5CJ8=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20200527053638.31439-2-zhang.lyra@gmail.com>
References: <20200527053638.31439-1-zhang.lyra@gmail.com> <20200527053638.31439-2-zhang.lyra@gmail.com>
Subject: Re: [RESEND PATCH v2 1/4] clk: sprd: check its parent status before reading gate clock
From:   Stephen Boyd <sboyd@kernel.org>
Cc:     linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
        Orson Zhai <orsonzhai@gmail.com>,
        Baolin Wang <baolin.wang7@gmail.com>,
        Chunyan Zhang <chunyan.zhang@unisoc.com>,
        Chunyan Zhang <zhang.lyra@gmail.com>
To:     Chunyan Zhang <zhang.lyra@gmail.com>
Date:   Tue, 26 May 2020 23:41:37 -0700
Message-ID: <159056169760.88029.12084641394538099454@swboyd.mtv.corp.google.com>
User-Agent: alot/0.9
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Quoting Chunyan Zhang (2020-05-26 22:36:35)
> From: Chunyan Zhang <chunyan.zhang@unisoc.com>
>=20
> Some clocks only can be accessed if their parent is enabled. mipi_csi_xx
> clocks on SC9863A are an examples. We have to ensure the parent clock is
> enabled when reading those clocks.
>=20
> Signed-off-by: Chunyan Zhang <chunyan.zhang@unisoc.com>
> ---

Applied to clk-next