From: Stefan Wahren <stefan.wahren@i2se.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-clk <linux-clk@vger.kernel.org>,
Krummsdorf Michael <Michael.Krummsdorf@tq-group.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH] clk: mxs: ensure that i.MX28's ref_io clks are not operated too fast
Date: Wed, 8 Aug 2018 10:23:37 +0200 (CEST) [thread overview]
Message-ID: <758892002.155298.1533716617448@email.1und1.de> (raw)
In-Reply-To: <20180801093113.wnjeg5a3rjbh7yc4@pengutronix.de>
Hi,
> > On Thu, Jul 26, 2018 at 11:50 AM, Stefan Wahren <stefan.wahren@i2se.com=
> wrote:
> >=20
> > > I only want to note that we are using this ugly hack for Duckbill to =
avoid
> > > this issue:
> > >
> > > https://github.com/I2SE/linux/commit/e457d5e0309c07e30e8dd8b17c32f7b3=
cbdd9547
> >=20
> > Do you see the problem on TQMa28L with Stefan's hack applied?
>=20
> With this change by Stefan the bug is not reproducible. Your change to
> set the bypass bits only later doesn't help though.
i can confirm that Fabio's patch doesn't fix the clock issue on Duckbill. B=
ut the idea seems to be right. If i remove all write access to CLKSEQ and F=
RAC0 in clk_misc_init() instead of swap them, i don't need the ref_xtal hac=
k anymore. I think Fabio's patch doesn't work because the bootloader (U-Boo=
t in my case) is already feeding SSP from ref_io.
Regards
Stefan
>=20
> Best regards
> Uwe
>=20
> --=20
> Pengutronix e.K. | Uwe Kleine-K=C3=B6nig =
|
> Industrial Linux Solutions | http://www.pengutronix.de/ =
|
next prev parent reply other threads:[~2018-08-08 8:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 18:56 [PATCH] clk: mxs: ensure that i.MX28's ref_io clks are not operated too fast Uwe Kleine-König
2017-05-03 19:53 ` Fabio Estevam
2017-05-04 12:25 ` Stefan Wahren
2017-05-05 7:25 ` Uwe Kleine-König
2017-05-05 7:49 ` Stefan Wahren
2017-05-05 15:49 ` Stefan Wahren
2017-05-05 20:10 ` Uwe Kleine-König
2017-05-07 11:51 ` Stefan Wahren
2017-05-08 8:24 ` Uwe Kleine-König
2017-05-10 13:39 ` Stefan Wahren
2017-05-10 14:13 ` Uwe Kleine-König
2017-05-10 20:26 ` Uwe Kleine-König
2017-05-08 9:53 ` AW: " Krummsdorf Michael
2017-05-08 10:14 ` Uwe Kleine-König
2017-05-10 18:05 ` Uwe Kleine-König
2017-05-26 12:06 ` Uwe Kleine-König
2017-05-29 21:06 ` Stefan Wahren
2017-05-29 21:21 ` Fabio Estevam
2017-05-30 6:54 ` Uwe Kleine-König
2017-05-30 8:04 ` Stefan Wahren
2017-05-30 11:13 ` Fabio Estevam
2018-07-26 14:32 ` Uwe Kleine-König
2018-07-26 14:50 ` Stefan Wahren
2018-07-26 15:02 ` Fabio Estevam
2018-08-01 9:31 ` Uwe Kleine-König
2018-08-02 8:33 ` Uwe Kleine-König
2018-08-03 9:09 ` Uwe Kleine-König
2018-08-08 8:23 ` Stefan Wahren [this message]
2018-08-08 9:09 ` Uwe Kleine-König
2018-07-26 15:04 ` Fabio Estevam
2018-07-26 15:18 ` Fabio Estevam
2019-03-22 21:51 ` Uwe Kleine-König
2019-05-02 12:37 ` Uwe Kleine-König
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=758892002.155298.1533716617448@email.1und1.de \
--to=stefan.wahren@i2se.com \
--cc=Michael.Krummsdorf@tq-group.com \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=shawnguo@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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