From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Kalle Valo <kvalo@codeaurora.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 0/2] ath10k: Enable QDSS clock on sm8150
Date: Mon, 27 Jan 2020 15:42:23 -0800 [thread overview]
Message-ID: <20200127234223.GA202699@yoga> (raw)
In-Reply-To: <20200127184037.3BFB620CC7@mail.kernel.org>
On Mon 27 Jan 10:40 PST 2020, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2019-12-22 21:48:53)
> > On SM8150 the WiFi firmware depends on the QDSS clock ticking, or the system
> > will reset due to an NoC error. So this adds an optional clock to the ath10k
> > binding and makes sure it's enabled while the WiFi firmware needs it.
>
> Hopefully this isn't a requirement in production firmware? Seems
> wasteful to keep the debug clk enabled in the field when nobody is
> debugging anything.
>
I'm confused about this as well, but I'm told that it was fixed
post-8150.
Regards,
Bjorn
prev parent reply other threads:[~2020-01-27 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 5:48 [PATCH 0/2] ath10k: Enable QDSS clock on sm8150 Bjorn Andersson
2019-12-23 5:48 ` [PATCH 1/2] ath10k: Add optional qdss clk Bjorn Andersson
2020-01-08 16:25 ` Rob Herring
2020-01-26 10:25 ` Kalle Valo
2019-12-23 5:48 ` [PATCH 2/2] arm64: dts: qcom: sm8150: Specify qdss clock for wifi Bjorn Andersson
2020-01-10 7:16 ` [PATCH 0/2] ath10k: Enable QDSS clock on sm8150 Kalle Valo
2020-01-15 9:04 ` Kalle Valo
2020-01-15 19:19 ` Bjorn Andersson
[not found] ` <20200127184037.3BFB620CC7@mail.kernel.org>
2020-01-27 23:42 ` Bjorn Andersson [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=20200127234223.GA202699@yoga \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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).