From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Christian Marangi <ansuelsmth@gmail.com>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Christian Marangi <ansuelsmth@gmail.com>
Subject: Re: [PATCH v2 1/2] clk: introduce (devm_)hw_register_mux_parent_data_table API
Date: Mon, 03 Oct 2022 20:51:07 -0700 [thread overview]
Message-ID: <20221004035109.42F3EC433D6@smtp.kernel.org> (raw)
In-Reply-To: <20220914144743.17369-1-ansuelsmth@gmail.com>
Quoting Christian Marangi (2022-09-14 07:47:42)
> Introduce (devm_)hw_register_mux_parent_data_table new API. We have
> basic support for clk_register_mux using parent_data but we lack any API
> to provide a custom parent_map. Add these 2 new API to correctly handle
> these special configuration instead of using the generic
> __(devm_)clk_hw_register_mux API.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2022-10-04 3:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 14:47 [PATCH v2 1/2] clk: introduce (devm_)hw_register_mux_parent_data_table API Christian Marangi
2022-09-14 14:47 ` [PATCH v2 2/2] clk: qcom: kpss-xcc: convert to parent data API Christian Marangi
2022-09-30 19:39 ` Dmitry Baryshkov
2022-10-04 3:51 ` Stephen Boyd
2022-09-30 19:19 ` [PATCH v2 1/2] clk: introduce (devm_)hw_register_mux_parent_data_table API Stephen Boyd
2022-10-04 3:51 ` Stephen Boyd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221004035109.42F3EC433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).