From: Rahul Sharma <rahul.sharma@samsung.com>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Inki Dae <inki.dae@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
sunil joshi <joshi@samsung.com>
Subject: Re: [PATCH] ARM: dts: remove display power domain for exynos5420
Date: Wed, 18 Jun 2014 12:06:54 +0530 [thread overview]
Message-ID: <CAPdUM4OK+ATMMRM67dV5JeeTGMu=XA7Gvi7Uif+Hypf3iP+6jg@mail.gmail.com> (raw)
In-Reply-To: <53A12EA3.5010007@samsung.com>
Hi Andrej,
On 18 June 2014 11:46, Andrzej Hajda <a.hajda@samsung.com> wrote:
> On 06/17/2014 07:49 AM, Rahul Sharma wrote:
>> Hi All,
>>
>> Please review this patch.
>>
>> Regards,
>> Rahul Sharma
>>
>> On 9 June 2014 16:58, Rahul Sharma <rahul.sharma@samsung.com> wrote:
>>> Display domain is removed due to instability issues. Explaining
>>> the problem below:
>>>
>>> exynos_init_late triggers the pm_genpd_poweroff_unused which
>>> powers off the unused power domains. This call hits before
>>> the trigger to deferred probes.
>>>
>>> DRM DP Panel defers the probe due to supply get failure. By the
>>> time, deferred probe is scheduled again, Display Power Domain is
>>> powered off by pm_genpd_poweroff_unused.
>>>
>>> FIMD and DP drivers are accessing registers during Probe and Bind
>>> callbacks. If display domain is enabled/disabled around register
>>> accesses, display domain gets unstable and we are getting Power
>>> Domain Disable fail notification. Increasing the Timeout also
>>> didn't help.
>
> As I understand the problem is that fimd and dp drivers access hw
> registers without enabling power domain. So the proper solution is to
> fix these drivers.
That is also a problem but I fixed those accesses in my local kernel before
hitting this issue. If we do register accesses in FIMD/DP probe/bind we
observes "Prefetch abort" exception. But here the problem is that 'DP
domain disable' starts failing if we enable/disable multiple times.
>
> Btw. there are already patches removing hw access from probe/bind of
> fimd. I guess removing also hw access from dp probe/bind could be a good
> solution.
Please let me know the links for posted patches. I will test with those patches.
Regards,
Rahul Sharma
>
> Regards
> Andrzej
>
>>>
>>> Signed-off-by: Rahul Sharma <rahul.sharma@samsung.com>
>>> ---
>>> based on Kukjin's for-next branch.
>>>
>>> arch/arm/boot/dts/exynos5420.dtsi | 6 ------
>>> 1 file changed, 6 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi
>>> index e385322..3d528cf 100644
>>> --- a/arch/arm/boot/dts/exynos5420.dtsi
>>> +++ b/arch/arm/boot/dts/exynos5420.dtsi
>>> @@ -262,11 +262,6 @@
>>> reg = <0x10044060 0x20>;
>>> };
>>>
>>> - disp_pd: power-domain@100440C0 {
>>> - compatible = "samsung,exynos4210-pd";
>>> - reg = <0x100440C0 0x20>;
>>> - };
>>> -
>>> msc_pd: power-domain@10044120 {
>>> compatible = "samsung,exynos4210-pd";
>>> reg = <0x10044120 0x20>;
>>> @@ -518,7 +513,6 @@
>>> };
>>>
>>> fimd: fimd@14400000 {
>>> - samsung,power-domain = <&disp_pd>;
>>> clocks = <&clock CLK_SCLK_FIMD1>, <&clock CLK_FIMD1>;
>>> clock-names = "sclk_fimd", "fimd";
>>> };
>>> --
>>> 1.7.9.5
>>>
>
next prev parent reply other threads:[~2014-06-18 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 11:28 [PATCH] ARM: dts: remove display power domain for exynos5420 Rahul Sharma
2014-06-17 5:49 ` Rahul Sharma
2014-06-18 6:16 ` Andrzej Hajda
2014-06-18 6:36 ` Rahul Sharma [this message]
2014-07-07 13:37 ` Rahul Sharma
2014-07-08 15:34 ` Tomasz Figa
[not found] ` <53BC0F8F.4010106-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-07-09 11:30 ` Rahul Sharma
2014-07-14 9:09 ` Rahul Sharma
2014-07-15 23:35 ` Kukjin Kim
2014-07-16 2:25 ` Rahul Sharma
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='CAPdUM4OK+ATMMRM67dV5JeeTGMu=XA7Gvi7Uif+Hypf3iP+6jg@mail.gmail.com' \
--to=rahul.sharma@samsung.com \
--cc=a.hajda@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=inki.dae@samsung.com \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tomasz.figa@gmail.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).