Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PATCH] clk: Remove global clk traversal on fetch parent index
References: <20181221003100.157581-1-dbasehore@chromium.org>
User-Agent: alot/0.8
Cc:     linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
        Derek Basehore <dbasehore@chromium.org>
From:   Stephen Boyd <sboyd@kernel.org>
In-Reply-To: <20181221003100.157581-1-dbasehore@chromium.org>
Message-ID: <154835742949.136743.9149540159914235850@swboyd.mtv.corp.google.com>
To:     Derek Basehore <dbasehore@chromium.org>, mturquette@baylibre.com
Date:   Thu, 24 Jan 2019 11:17:09 -0800
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Quoting Derek Basehore (2018-12-20 16:31:00)
> It's not required to traverse the entire clk tree when the parents
> array contains a NULL value. You already have the parent clk_core
> pointer, so you can just compare the parent->name and parent_names[i]
> pointers.
>=20
> In cases where clk names are never registered, this can be
> a substantial power improvement since a mux having an unregistered
> parent name will traverse the clk tree on every set_rate. This can
> happen hundreds of times a second on CPU clks.
>=20
> Change-Id: I85499d2e576249568ff508e424ca8d5009e6e2b1
> Signed-off-by: Derek Basehore <dbasehore@chromium.org>
> ---

Applied to clk-fixes + some commit text and comment updates.