From: Mars Cheng <mars.cheng@mediatek.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: mturquette@baylibre.com, sean.wang@mediatek.com,
linux-kernel@vger.kernel.org, kevin-cw.chen@mediatek.com,
jasu@njomotys.info, matthias.bgg@kernel.org,
matthias.bgg@gmail.com, linux-mediatek@lists.infradead.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 3/3] clk: mediatek: Mark bus and DRAM related clocks as critical
Date: Wed, 27 Feb 2019 18:36:31 +0800 [thread overview]
Message-ID: <1551263791.9274.1.camel@mtkswgap22> (raw)
In-Reply-To: <155120371334.260864.14503820089028591730@swboyd.mtv.corp.google.com>
Hi Stephen
On Tue, 2019-02-26 at 09:55 -0800, Stephen Boyd wrote:
> Quoting matthias.bgg@kernel.org (2019-02-14 08:32:42)
> > From: Jasper Mattsson <jasu@njomotys.info>
> >
> > Currently, DRAM-related clocks are not marked with CLK_IS_CRITICAL
> > for MT6797. This causes memory corruption when the system is
> > booted without clk_ignore_unused.
> > This patch marks MUX ddrphycfg_sel as well as gates infra_dramc_f26m
> > and infra_dramc_b_f26m as CLK_IS_CRITICAL.
> >
> > Signed-off-by: Jasper Mattsson <jasu@njomotys.info>
> > Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
> > ---
>
> Applied to clk-next
>
> Would be nice to get someone from mediatek to ack it, but I can't wait
> forever.
Acked-by:Mars Cheng <mars.cheng@mediatek.com>
Thanks a lot.
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-27 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 16:32 [PATCH v4 3/3] clk: mediatek: Mark bus and DRAM related clocks as critical matthias.bgg
2019-02-26 17:55 ` Stephen Boyd
2019-02-27 10:36 ` Mars Cheng [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=1551263791.9274.1.camel@mtkswgap22 \
--to=mars.cheng@mediatek.com \
--cc=jasu@njomotys.info \
--cc=kevin-cw.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=matthias.bgg@kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=sean.wang@mediatek.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).