From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Christian Neubert" <christian.neubert.86@gmail.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
"Mike Turquette" <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Jason Cooper" <jason@lakedaemon.net>,
"Andrew Lunn" <andrew@lunn.ch>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
"Antoine Tenart" <antoine.tenart@bootlin.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] clk: mvebu: armada-37xx-periph: Fix initialization for cpu clocks
Date: Thu, 25 Apr 2019 15:33:03 +0300 [thread overview]
Message-ID: <20190425123303.GA12659@apalos> (raw)
In-Reply-To: <20190424093015.rcr5auamfccxf6ei@vireshk-i7>
Hi Viresh,
> > > Also, during this week-end, Christian suggested that the issue might
> > > come from the AVS support.
> > >
> > > Could you disable it and check you still have the issue?
> > >
> > > For this, you just have to remove the avs node in
> > > arch/arm64/boot/dts/marvell/armada-37xx.dtsi and rebuild the dtb.
> > Sure. You'll have to wait for a week though. Currently on a trip. I'll run that
> > once i return
>
> @Ilias: Can you please try this now and confirm to Gregory ?
I am more overloaded than usual and totally forgot about this. Apologies.
I'll try finding some time and do this.
Thanks
/Ilias
next prev parent reply other threads:[~2019-04-25 12:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 16:35 [PATCH] clk: mvebu: armada-37xx-periph: Fix initialization for cpu clocks Gregory CLEMENT
2019-03-14 12:15 ` Ilias Apalodimas
[not found] ` <CAC5LXJcCs4nr-qFOWzUJpUBAJ9ngG-cgeTCVCFBKFc1SPzHMuQ@mail.gmail.com>
2019-03-14 13:44 ` Ilias Apalodimas
[not found] ` <CAC5LXJf=f2bZLroSXFkGiF2W=1XzAgb_wwtpvZY7O9xv28wbVA@mail.gmail.com>
2019-03-14 14:15 ` Ilias Apalodimas
2019-03-14 14:20 ` Gregory CLEMENT
2019-03-18 11:28 ` Ilias Apalodimas
2019-03-18 11:40 ` Gregory CLEMENT
2019-03-18 12:21 ` Ilias Apalodimas
2019-04-24 9:30 ` Viresh Kumar
2019-04-24 9:30 ` Viresh Kumar
2019-04-25 12:33 ` Ilias Apalodimas [this message]
2019-04-25 12:33 ` Ilias Apalodimas
2019-05-20 11:20 ` Viresh Kumar
2019-05-22 7:03 ` Ilias Apalodimas
2019-05-22 7:06 ` Viresh Kumar
2019-06-10 10:19 ` Viresh Kumar
2019-07-17 10:33 ` Viresh Kumar
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=20190425123303.GA12659@apalos \
--to=ilias.apalodimas@linaro.org \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=christian.neubert.86@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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).