Linux clock framework development
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Fabio Estevam <festevam@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>,
	linux-clk@vger.kernel.org, Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH] clk: mxs: ensure that i.MX28's ref_io clks are not operated too fast
Date: Fri, 5 May 2017 09:49:10 +0200	[thread overview]
Message-ID: <a5bfc04e-15cf-2b24-17f9-c9b60c1052cc@i2se.com> (raw)
In-Reply-To: <20170505072529.a3z4gonsygg3wqfx@pengutronix.de>

Hello Uwe,

Am 05.05.2017 um 09:25 schrieb Uwe Kleine-König:
> Hello Stefan,
>
> On Thu, May 04, 2017 at 02:25:07PM +0200, Stefan Wahren wrote:
>>        ref_io1                            1            1  
>> 320000000          0 0
> That means your ref_io1 is running at 320 MHz which my patch should
> prevent. Are you sure it is applied?

sorry for the mess in the dumps.

Your patch works fine regarding to ref_io1. I made 3 dumps:

1. without any patch ( ref_io1 320000000 )
2. with my ref_xtal patch ( ref_io1 288000000 )
3. with your patch ( ref_io1 288000000 )

I assume you looked at the wrong dump.

>  What is the register FRAC0
> (0x800401b0) set to? Given that ref_io1 is reported as running at
> 320000000 I'd expect that IO1FRAC is set to 27 which should be
> impossible with my patch given that clk_misc_init() in
> drivers/clk/mxs/clk-imx28.c initializes IO1FRAC0 to 30 and my patch
> should prevent it being set to something smaller than 30.
>
> Something I just noticed now is that the description of FRAC0 includes:
>
> 	NOTE: This register can only be addressed by byte instructions.
> 	Addressing word or half-word are not allowed.
>
> which is not respected by the clock driver.

I already tried it with no luck. Please follow the discussions [1] and [2].

Maybe the reason why [1] didn't work, was the missing memory barriers?

Please don't get me wrong, i'm very interested in fixing this issue.

Regards Stefan

[1] -
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/318644.html
[2] -
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/323720.html

>
> Best regards
> Uwe
>

  reply	other threads:[~2017-05-05  7:49 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 [this message]
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
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=a5bfc04e-15cf-2b24-17f9-c9b60c1052cc@i2se.com \
    --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