Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20221018-clk-rate-request-tracing-v2-1-5170b363c413@cerno.tech>
References: <20221018-clk-rate-request-tracing-v2-0-5170b363c413@cerno.tech> <20221018-clk-rate-request-tracing-v2-1-5170b363c413@cerno.tech>
Subject: Re: [PATCH v2 1/2] clk: Store clk_core for clk_rate_request
From:   Stephen Boyd <sboyd@kernel.org>
Cc:     Maxime Ripard <maxime@cerno.tech>, linux-kernel@vger.kernel.org,
        linux-clk@vger.kernel.org
To:     Masami Hiramatsu <mhiramat@kernel.org>,
        Michael Turquette <mturquette@baylibre.com>,
        Steven Rostedt <rostedt@goodmis.org>, maxime@cerno.tech
Date:   Wed, 07 Dec 2022 13:48:38 -0800
User-Agent: alot/0.10
Message-Id: <20221207214840.AFC6AC433D6@smtp.kernel.org>
Precedence: bulk

Quoting maxime@cerno.tech (2022-10-26 06:46:58)
> The struct clk_rate_request is meant to store the context around a rate
> request such as the parent, boundaries, and so on.
>=20
> However, it doesn't store the clock the rate request is submitted to,
> which makes debugging difficult.
>=20
> Let's add a pointer to the relevant clk_core instance in order to
> improve the debugging of rate requests in a subsequent patch.
>=20
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---

Applied to clk-next