From: Sasha Levin <sashal@kernel.org>
To: Ryder Lee <ryder.lee@mediatek.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Weijie Gao <weijie.gao@mediatek.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH v1 3/3] arm64: dts: mt7622: Drop the general purpose timer node
Date: Sun, 11 Nov 2018 21:45:56 -0500 [thread overview]
Message-ID: <20181112024556.GI2642@sasha-vm> (raw)
In-Reply-To: <17fde639c7d37f9cfabab230379913e652cf869a.1541643419.git.ryder.lee@mediatek.com>
On Mon, Nov 12, 2018 at 09:28:08AM +0800, Ryder Lee wrote:
>The crash http://termbin.com/zitb is caused by the timer register
>into system in early pahse during kernel boot, but the clock
>sources didn't get ready at that time.
>
>A better way is to switch to use CLK_OF_DECLARE() in driver for things
>that need them early, but this node is actually useless in MT7622.
>So we drop it.
>
>Fixes: 9cc7f0de9e67 ("arm64: dts: mt7622: add timer, CCI-400 and PMU nodes")
>Cc: stable@vger.kernel.org
>Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
To confirm: the patch this fixes was added in v4.20-rc1, which means
that this current patch doesn't apply to any of the stable trees.
Did we miss something?
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-11-12 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 1:28 [PATCH v1 1/3] arm64: dts: mt7622: fix no more console output on rfb1 Ryder Lee
2018-11-12 1:28 ` [PATCH v1 2/3] arm64: dts: mt7622: fix no more console output on BPI-R64 board Ryder Lee
2018-11-12 1:28 ` [PATCH v1 3/3] arm64: dts: mt7622: Drop the general purpose timer node Ryder Lee
2018-11-12 2:45 ` Sasha Levin [this message]
2018-11-12 3:33 ` Ryder Lee
2018-11-12 3:49 ` Ryder Lee
2018-11-23 17:07 ` Matthias Brugger
2018-11-26 3:49 ` Ryder Lee
2018-11-26 10:15 ` Matthias Brugger
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=20181112024556.GI2642@sasha-vm \
--to=sashal@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=stable@vger.kernel.org \
--cc=weijie.gao@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).