From: Andy Gross <andy.gross@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: David Brown <david.brown@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-mtp: Mark protected gcc clocks
Date: Fri, 9 Nov 2018 17:21:49 -0600 [thread overview]
Message-ID: <20181109232149.GA8686@hector.attlocal.net> (raw)
In-Reply-To: <20181106055013.11271-1-bjorn.andersson@linaro.org>
On Mon, Nov 05, 2018 at 09:50:13PM -0800, Bjorn Andersson wrote:
> As of v4.20-rc1 probing the GCC driver on a SDM845 device with the
> standard security implementation causes an access violation and an
> immediate system restart. Use the protected-clocks property to mark the
> offending clocks protected for the MTP, in order to allow it to boot.
>
> Cc: Stephen Boyd <sboyd@kernel.org>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
This looks fine to me.
Acked-by: Andy Gross <andy.gross@linaro.org>
next prev parent reply other threads:[~2018-11-09 23:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 19:40 [PATCH 0/2] Introduce a 'protected-clocks' property Stephen Boyd
2018-11-05 19:40 ` [PATCH 1/2] dt-bindings: clk: Introduce " Stephen Boyd
2018-11-06 1:04 ` Bjorn Andersson
2018-11-08 5:44 ` Bjorn Andersson
2018-11-08 18:11 ` Stephen Boyd
2018-11-21 9:00 ` Stephen Boyd
2018-11-05 19:40 ` [PATCH 2/2] clk: qcom: Support " Stephen Boyd
2018-11-06 1:05 ` Bjorn Andersson
2018-11-21 9:00 ` Stephen Boyd
2018-11-06 5:50 ` [PATCH] arm64: dts: qcom: sdm845-mtp: Mark protected gcc clocks Bjorn Andersson
2018-11-09 23:21 ` Andy Gross [this message]
2018-11-21 9:01 ` Stephen Boyd
2018-11-22 7:30 ` Bjorn Andersson
2018-11-28 6:33 ` Stephen Boyd
2018-11-21 9:07 ` Stephen Boyd
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=20181109232149.GA8686@hector.attlocal.net \
--to=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.