From: Matthias Kaehlcke <mka@chromium.org>
To: Taniya Das <quic_tdas@quicinc.com>
Cc: "Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette " <mturquette@baylibre.com>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v3 3/3] clk: qcom: lpass: Add support for resets & external mclk for SC7280
Date: Tue, 31 May 2022 15:51:19 -0700 [thread overview]
Message-ID: <Ypab50H+Y9W9XnnU@google.com> (raw)
In-Reply-To: <20220526042601.32064-4-quic_tdas@quicinc.com>
On Thu, May 26, 2022 at 09:56:01AM +0530, Taniya Das wrote:
> The clock gating control for TX/RX/WSA core bus clocks would be required
> to be reset(moved from hardware control) from audio core driver. Thus
> add the support for the reset clocks.
>
> Also add the external mclk to interface external MI2S.
>
> Fixes: 2b75e142523e ("clk: qcom: lpass: Add support for LPASS clock controller for SC7280").
This commit doesn't exist either:
git show 2b75e142523e
fatal: ambiguous argument '2b75e142523e': unknown revision or path not in the working tree.
You probably mean:
a9dd26639d05 clk: qcom: lpass: Add support for LPASS clock controller for SC7280
It seems you got these commit ids from a downstream branch, instead of an
upstream/maintainer branch.
prev parent reply other threads:[~2022-05-31 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 4:25 [PATCH v3 0/3] Add support for audio clock gating resets for SC7280 Taniya Das
2022-05-26 4:25 ` [PATCH v3 1/3] dt-bindings: clock: Add resets for LPASS audio clock controller " Taniya Das
2022-05-31 22:45 ` Matthias Kaehlcke
2022-05-26 4:26 ` [PATCH v3 2/3] dt-bindings: clock: Add support for external MCLKs for LPASS on SC7280 Taniya Das
2022-05-26 4:26 ` [PATCH v3 3/3] clk: qcom: lpass: Add support for resets & external mclk for SC7280 Taniya Das
2022-05-31 22:51 ` Matthias Kaehlcke [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=Ypab50H+Y9W9XnnU@google.com \
--to=mka@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
/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).