From: Stefan Wahren <stefan.wahren@i2se.com>
To: "Fabio Estevam" <festevam@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-clk@vger.kernel.org, Sascha Hauer <kernel@pengutronix.de>,
Michael Turquette <mturquette@baylibre.com>,
Shawn Guo <shawnguo@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH] clk: mxs: ensure that i.MX28's ref_io clks are not operated too fast
Date: Mon, 29 May 2017 23:06:42 +0200 (CEST) [thread overview]
Message-ID: <1092654219.601654.1496092002868@email.1und1.de> (raw)
In-Reply-To: <20170526120638.2dfvy4nbzjzbampc@pengutronix.de>
Hi Uwe,
> Uwe Kleine-K=C3=B6nig <u.kleine-koenig@pengutronix.de> hat am 26. Mai 201=
7 um 14:06 geschrieben:
>=20
>=20
> Hello,
>=20
> On Wed, May 03, 2017 at 04:53:09PM -0300, Fabio Estevam wrote:
> > On Wed, May 3, 2017 at 3:56 PM, Uwe Kleine-K=C3=B6nig
> > <u.kleine-koenig@pengutronix.de> wrote:
> > > Since commits 7d81397cd93d ("clk: mxs: add clock support for imx28") =
and
> > > 64e2bc413047 ("clk: mxs: imx28: decrease the frequency of ref_io1 for
> > > SSP2 and SSP3") the frequencies for ref_io0 and ref_io1 are initializ=
ed
> > > to 288 MHz because the initial frequency "seems too high to be ssp cl=
ock
> > > source directly". However this isn't enough to ensure that the freque=
ncy
> > > isn't increased later again. In fact this happens on my machine as th=
e
> > > mxs-spi driver calls clk_set_rate(ssp->clk, 160000000) with ssp being
> > > ssp2 which is resolved to
> > >
> > > ref_io1.rate =3D 320 MHz
> > > ssp2_sel.parent =3D ref_io1
> > > ssp2_div.divider =3D 2
> > >
> > > . The observed effect is that reading MISO reliably fails: Instead of
> > > the least significant bit the second least significant bit is reporte=
d
> > > twice. This is probably related to the reports
> > >
> > > https://community.nxp.com/thread/290209
> > > https://community.nxp.com/thread/310434
> >=20
> > Adding Stefan on Cc in he could help testing this patch, as he was the
> > one that created this thread.
>=20
> Even though my patch doesn't help Stefan, I think it should be applied
> nevertheless as it makes my machine work, just completes the
> workaround/fix that is already in mainline and nobody who still has the
> issue has the time to debug this further.
i like to see at least a comment within the code that the change is a worka=
round.
Thanks
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:[~2017-05-29 21:06 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 [this message]
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
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=1092654219.601654.1496092002868@email.1und1.de \
--to=stefan.wahren@i2se.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