From: Mike Turquette <mturquette@linaro.org>
To: "Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Tero Kristo" <t-kristo@ti.com>, Paul <paul@pwsan.com>
Cc: Nishanth Menon <nm@ti.com>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM: OMAP5+: Support Duty Cycle Correction(DCC)
Date: Fri, 23 May 2014 14:07:20 -0700 [thread overview]
Message-ID: <20140523210720.23136.65858@quantum> (raw)
In-Reply-To: <1400237160-25125-1-git-send-email-nm@ti.com>
Quoting Nishanth Menon (2014-05-16 03:45:57)
> Hi,
>
> This patch series has been carried over in vendor kernel for quiet
> few years now.
>
> Unfortunately, it was very recently re-discovered and upstream kernel
> is noticed to be broken for OMAP5 1.5GHz - at least we are operating
> DPLL at frequency higher than what it was intended to be when CPUFreq
> is enabled. Thankfully, with nominal voltage(we dont use AVS yet in
> upstream for the mentioned platforms) and margins in trimming, we
> have so far not crashed - but I strongly suspect this might be some
> boundary case survival.
DCC also exists in OMAP4. In some cases customers used it, in other
cases we just ran the PLL way out of spec and the mpu_clk would divide
by 2.
Is this broken for OMAP4 as well?
Regards,
Mike
>
> Verified on the following impacted platforms using 3.15-rc4 based
> vendor kernel.
>
> Before:
> OMAP5432: http://slexy.org/view/s20cs0qQFg
> DRA72x: http://slexy.org/view/s2TXtSa6mH (refused to lock)
> DRA75x: http://slexy.org/view/s20AW8MU5c
> After:
> OMAP5432: http://slexy.org/view/s21iAfWxpu
> DRA72x: http://slexy.org/view/s2hwsvGLmC (locks properly)
> DRA75x: http://slexy.org/view/s21ehw8WQn
>
> Hopefully, we can get these into some kernel revision in some form.
>
> NOTE: Support for 4470(which is the only other platform requiring
> DCC) is not present in upstream kernel and there are no plans to
> support that SoC, even if it is added at a later point, support can be
> extended as needed.
>
> Series based on v3.15-rc5 tag.
> Also available on my tree:
> https://github.com/nmenon/linux-2.6-playground/
> branch: push/clock/dcc
>
> weblink: https://github.com/nmenon/linux-2.6-playground/commits/push/clock/dcc
>
> Verification:
> 3.15-rc4 based kernel - DRA75x-evm, 72x-evm, OMAP5uevm
> 3.15-rc5 - OMAP5uEVM(only one supporting 1.5GHz atm)
>
> Andrii Tseglytskyi (1):
> ARM: OMAP5+: dpll: support Duty Cycle Correction(DCC)
>
> Nishanth Menon (2):
> clk: dpll: support OMAP5 MPU DPLL that need special handling for
> higher frequencies
> ARM: dts: OMAP5/DRA7: use omap5-mpu-dpll-clock capable of dealing
> with higher frequencies
>
> .../devicetree/bindings/clock/ti/dpll.txt | 1 +
> arch/arm/boot/dts/dra7xx-clocks.dtsi | 2 +-
> arch/arm/boot/dts/omap54xx-clocks.dtsi | 2 +-
> arch/arm/mach-omap2/dpll3xxx.c | 9 +++++++++
> drivers/clk/ti/dpll.c | 21 ++++++++++++++++++++
> include/linux/clk/ti.h | 4 ++++
> 6 files changed, 37 insertions(+), 2 deletions(-)
>
> Regards,
> Nishanth Menon
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2014-05-23 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 10:45 [PATCH 0/3] ARM: OMAP5+: Support Duty Cycle Correction(DCC) Nishanth Menon
2014-05-16 10:45 ` [PATCH 1/3] ARM: OMAP5+: dpll: support " Nishanth Menon
[not found] ` <1400237160-25125-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2014-05-16 10:45 ` [PATCH 2/3] clk: dpll: support OMAP5 MPU DPLL that need special handling for higher frequencies Nishanth Menon
2014-05-16 10:46 ` [PATCH 3/3] ARM: dts: OMAP5/DRA7: use omap5-mpu-dpll-clock capable of dealing with " Nishanth Menon
2014-05-23 11:21 ` [PATCH 0/3] ARM: OMAP5+: Support Duty Cycle Correction(DCC) Tero Kristo
2014-05-23 21:07 ` Mike Turquette [this message]
2014-05-26 6:32 ` Tero Kristo
2014-05-28 12:49 ` Nishanth Menon
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=20140523210720.23136.65858@quantum \
--to=mturquette@linaro.org \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).