public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: javier.martinez@collabora.co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 9/9] drm/exynos: add support for 'hdmi' clock
Date: Thu, 22 Jan 2015 13:51:11 +0100	[thread overview]
Message-ID: <54C0F23F.3030804@collabora.co.uk> (raw)
In-Reply-To: <54C0EFEB.6080201@samsung.com>

Hello Marek,

On 01/22/2015 01:41 PM, Marek Szyprowski wrote:
>>>   
>>> +	mixer_res->hdmi = devm_clk_get(dev, "hdmi");
>> You need to update the Documentation/devicetree/bindings/video/exynos_mixer.txt
>> DT binding docs to also mention the "hdmi" clock in the list of clocks.
> 
> Right, I've send an updated version of the patch.
>

Great thanks.
 
>> But as I mentioned in "[PATCH v2 0/6] Enable HDMI support on Exynos platforms"
>> thread, while this seems to be enough to prevent the issue on Exynos4 is not
>> enough on the Exynos5420/5422/5800 boards I've tested.
>>
>> So I wonder if $subject is fixing the root cause or just fixing a symptom and
>> the cause is that the exynos_hdmi DPMS handler has to be executed before the
>> exynos_mixer DPMS handler for DRM_MODE_DPMS_ON like is the case for DPMS_OFF
>> after commit 245f98f269714 ("drm/exynos: hdmi: fix power order issue").
> 
> I'm aware of the issues with Exynos542x, I've tested it with Odroid XU3, 
> but I
> really have no idea how to fix it. The reference manual (both for power 
> domain
> and mixer/hdmi modules) also doesn't provide any useful information for this
> case.
>

Yeah, I'm in the same situation. All the documentation I had access to doesn't
now explain what's happening.
 
> The issue with power on/off sequence definitely IS related to clock 
> configuration,
> but we didn't figure out how to solve it in a generic way. This will be 
> handled in
> Exynos HDMI and mixer drivers anyway, so the DTS part (at least for 
> Exynos4 SoC)
> will not change.
>
> We would really like to have HDMI support for Exynos4 merged, especially 
> that the
> first version of the HDMI patches was posted in v3.16 times and now we 
> are close
> to v3.20 -next merge window end...
>

Sorry, I didn't mean to imply that $subject should be blocked. I agree with
you that the power on/off sequence has to be fixed in the hdmi and mixer
drivers and is orthogonal to the DTS changes. That's why I also decided to
finally post my "Add HDMI support for Exynos5420 platform" [0] series too.

> Best regards
> 

Best regards,
Javier

[0]: https://lkml.org/lkml/2015/1/20/235

  reply	other threads:[~2015-01-22 12:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 12:16 [PATCH v4 0/9] Enable HDMI support on Exynos platforms Marek Szyprowski
2015-01-20 12:16 ` [PATCH v4 1/9] PM / Domains: Add a note about power domain subdomains Marek Szyprowski
2015-01-20 12:16 ` [PATCH v4 2/9] ARM: Exynos: add support for sub-power domains Marek Szyprowski
2015-01-20 12:16 ` [PATCH v4 3/9] ARM: dts: exynos4: add hdmi related nodes Marek Szyprowski
2015-01-20 12:16 ` [PATCH v4 4/9] ARM: dts: exynos4: add dependency between TV and LCD0 power domains Marek Szyprowski
2015-01-20 12:16 ` [PATCH v4 5/9] ARM: dts: exynos4412-odroid: enable hdmi support Marek Szyprowski
2015-01-20 12:16 ` [PATCH v4 6/9] ARM: dts: exynos4210-universal_c210: " Marek Szyprowski
2015-01-20 12:16 ` [PATCH v4 7/9] ARM: dts: Exynos: add 'hdmi' clock to mixer nodes Marek Szyprowski
2015-01-20 12:16 ` [PATCH v4 8/9] ARM: dts: exynos5250: add display power domain Marek Szyprowski
2015-01-20 12:16 ` [PATCH v4 9/9] drm/exynos: add support for 'hdmi' clock Marek Szyprowski
2015-01-20 12:52   ` Javier Martinez Canillas
2015-01-22 12:28     ` [PATCH v4 RESEND " Marek Szyprowski
2015-01-22 13:11       ` Javier Martinez Canillas
2015-01-22 12:41     ` [PATCH v4 " Marek Szyprowski
2015-01-22 12:51       ` Javier Martinez Canillas [this message]
2015-01-22 13:20         ` Marek Szyprowski
2015-01-22 13:00   ` Fabio Estevam
2015-02-02 12:54     ` Marek Szyprowski

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=54C0F23F.3030804@collabora.co.uk \
    --to=javier.martinez@collabora.co.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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