All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Jakobi <liquid.acid@gmx.net>
To: Tomasz Stanislawski <t.stanislaws@samsung.com>,
	linux-samsung-soc@vger.kernel.org
Subject: Re: exynos4412: porting hdmiddc and hdmiphy node entries
Date: Mon, 05 May 2014 22:55:53 +0200	[thread overview]
Message-ID: <5367FAD9.9080705@gmx.net> (raw)
In-Reply-To: <53675932.30306@samsung.com>

Hello Tomasz,

thanks a lot for the support!

> The meaning of hdmiphy is ambiguous.
> In exynos4 spec there are _TWO_ components named HDMIPHY.
> The first one is a PLL that generates a clock for HDMI subsystem.
> This PLL is controlled by I2C.
> 
> You can find an example of its bindings at:
> http://lists.freedesktop.org/archives/dri-devel/2013-October/047687.html
OK, that looks exactly like the bindings I currently have in the dts.


> The second one is HDMI's physical interface located in PMU unit.
> 
> The exynos-simple-phy is dedicated to controller the former (component of PMU).
> 
> The 'phy' attribute in DT refers to the PLL.
> There is a debate if 'phy' should refer to I2C device itself or
> rather to I2C bus. Currently it refers to driverless instance
> of I2C device.
By 'driverless' you mean that the node isn't probed by any specific
driver code / the 'compatible' string isn't used anywhere in the kernel
(like it's currently the situation?)


>> Somehow this doesn't look right. And indeed:
>> https://patchwork.kernel.org/patch/4021121/
>>
>> At least for exynos5250 this node is not a child on an i2c adapter.
> 
> This is a completely different HDMIPHY.
I'm not sure I understand. Different from the PPL and the PMU HDMIPHY?


>> And yes, I would still have to add 'phys' and 'phy-names' to the hdmi
>> node. This looks wrong again. Why do I have to specify 'phys' when I
>> already have 'phy' there? Isn't that redundant?
> 
> 'phys' and 'phy-names' refers to PHY interfaces delivered by phy-core.
> The attribute named 'phy' refers to I2C device used to controller HDMI's PLL.
> The naming convention is very misleading.
Hmm, indeed this is very confusing. So with the move to
exynos-simple-phy, I guess I need these entries as well, am I correct?


>> Well, you see, lots of confusion here. I would appreciate any kind of
>> help on how to proceed here.
> 
> The documentation for HDMI's bindings should be fixed.
Well, I can agree with that :)


With best wishes,
Tobias

  reply	other threads:[~2014-05-05 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-27  0:33 exynos4412: porting hdmiddc and hdmiphy node entries Tobias Jakobi
2014-05-05  9:26 ` Tomasz Stanislawski
2014-05-05 20:55   ` Tobias Jakobi [this message]
2014-05-19  0:18   ` Tobias Jakobi

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=5367FAD9.9080705@gmx.net \
    --to=liquid.acid@gmx.net \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=t.stanislaws@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.