From: Matthias Brugger <matthias.bgg@gmail.com>
To: matthias.bgg@kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, kevin-cw.chen@mediatek.com,
mars.cheng@mediatek.com
Cc: sean.wang@mediatek.com, jasu@njomotys.info,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Matthias Brugger <mbrugger@suse.com>
Subject: Re: [PATCH v4 0/3] Mark clocks as critical for MT6797
Date: Tue, 26 Feb 2019 13:59:44 +0100 [thread overview]
Message-ID: <f7ed0750-665a-76bc-df1a-95af39fef8ec@gmail.com> (raw)
In-Reply-To: <20190214163026.26073-1-matthias.bgg@kernel.org>
On 14/02/2019 17:30, matthias.bgg@kernel.org wrote:
> From: Matthias Brugger <mbrugger@suse.com>
>
> Jasper send this series some month ago. As there was no reaction from
> his side, I'll do a friendly take-over.
> I tested the patches on my Helios X20 boards and they fix the issue.
> I didn't add a Tested-by tag as I added my Signed-off-by.
>
> Changes since v3:
> - add comments explaining why the clock muxer and gates are marked
> as critical
>
> Changes since v2 (https://patchwork.kernel.org/patch/10686759/):
> - axi_sel is not needed, drop CLK_IS_CRITICAL for it.
> - update commit message
> - add Acked-by from Mars
>
> Changes since v1:
> - add a fixes tag.
>
Steven, Mike any comments on this?
Regards,
Matthias
> ---
>
> Currently, DRAM-related clocks and the axi_sel MUX are not marked with
> CLK_IS_CRITICAL for MT6797. This causes memory corruption when the
> system is booted without clk_ignore_unused.
>
> This patchset
>
> 1. Makes it possible to mark outputs of MUXes as critical by introducing
> a new macro, MUX_FLAGS,
> 2. Makes it possible to mark gates as critical by adding flags to
> mtk_gate, and
> 3. Marks axi_sel, ddrphycfg_sel, infra_dramc_f26m and infra_dramc_b_f26m
> as critical.
>
> The addition of flags to mtk_gate also exists in the patch series "Add
> basic and clock support for Mediatek MT8183 SoC" [1]. The type of
> flags is unsigned int in that series, but the real type is unsigned
> long, so my patch differs from that patch.
>
> [1] https://patchwork.kernel.org/patch/10549953/
>
> Jasper Mattsson (3):
> clk: mediatek: Add MUX_FLAGS macro
> clk: mediatek: Add flags to mtk_gate
> clk: mediatek: Mark bus and DRAM related clocks as critical
>
> drivers/clk/mediatek/clk-gate.c | 4 +-
> drivers/clk/mediatek/clk-gate.h | 3 +-
> drivers/clk/mediatek/clk-mt6797.c | 68 +++++++++++++++++++------------
> drivers/clk/mediatek/clk-mtk.c | 2 +-
> drivers/clk/mediatek/clk-mtk.h | 9 +++-
> 5 files changed, 56 insertions(+), 30 deletions(-)
>
next prev parent reply other threads:[~2019-02-26 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 16:30 [PATCH v4 0/3] Mark clocks as critical for MT6797 matthias.bgg
2019-02-26 12:59 ` Matthias Brugger [this message]
2019-02-26 17:53 ` 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=f7ed0750-665a-76bc-df1a-95af39fef8ec@gmail.com \
--to=matthias.bgg@gmail.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=mars.cheng@mediatek.com \
--cc=matthias.bgg@kernel.org \
--cc=mbrugger@suse.com \
--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