From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Rahul Sharma' <r.sh.open@gmail.com>,
'Sylwester Nawrocki' <sylvester.nawrocki@gmail.com>
Cc: 'Rahul Sharma' <rahul.sharma@samsung.com>,
linux-samsung-soc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, inki.dae@samsung.com,
joshi@samsung.com,
'Tomasz Stanislawski' <t.stanislaws@samsung.com>,
'Tomasz Figa' <t.figa@samsung.com>,
thomas.ab@samsung.com
Subject: RE: [PATCH 1/4] ARM: dts: add support for hdmi to exynos4
Date: Thu, 31 Jan 2013 14:25:49 -0800 [thread overview]
Message-ID: <0aff01ce0001$edc8f320$c95ad960$@samsung.com> (raw)
In-Reply-To: <CAPdUM4NxRkE_g36yPPjhFO8jHYdBwQ6cNk+pndyO+h9fcwn-8w@mail.gmail.com>
Rahul Sharma wrote:
[...]
> >>>> + hdmi {
> >>>> + compatible = "samsung,exynos4-hdmi14";
> >>>
> >>>
> >>>
> >>> What "-hdmi14" signifies here ? And to which Exynos4 SoC revisions
this
> >>> compatible property is supposed to apply ?
> >>>
> >>
> >> -hdmi14 signifies 1.4 compliant Hdmi IP like in Exynos4412, while
> >> Exynos4210 has 1.3
> >> compliant HDMI block. I have done a mistake here. I should have kept
> >> it in 4412.dtsi. OR
> >> I can move it to 4x12.dtsi but not sure whether all 4x12 socs have 1.4
> >> hdmi.
> >
> >
> > Exynos4210 also have the HDMI IP. I'm not sure how much common those
> IP's
> > are
> > among Exynos4 series SoCs. I suppose it makes sense to create a hdmi
> node in
> > exynos4.dtsi and override what's required either in exynos4x12.dtsi or
> > exynos4412.dtsi file.
> >
> > What is worring me is that you're trying to just append the supported
> > HDMI standard version to the string, and there might be more differences
> > in the IPs across all Exynos4 SoC series. What if there are two
different
> > SoCs that support e.g. HDMI v1.4 but there are some differences in the
> > HDMI IPs ? You would likely need to invent new properties and pass them
> > to the driver. Appending specific SoC name to the compatible string
looks
> > like a better alternative to me.
> >
>
> I agree to it. Putting compatible string with first soc having the IP,
> is a better
> approach altogether. I will incorporate the change in next version.
>
Well, in this case, why should we use the SoC name? If just we need specific
name here. I think, putting SoC name in compatible is a way to identify and
when the version of IP is available, we can the version instead...like
following, as some guy said before.
compatible = "samsung,hdmi-1.4"
If there is for hdmi 1.4a,
compatible = "samsung,hdmi-1.4a"
Thanks.
- Kukjin
next prev parent reply other threads:[~2013-01-31 22:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 10:39 [PATCH 0/4] 0/4] ARM: dts: add support for hdmi to exynos4412 Rahul Sharma
2013-01-25 10:39 ` [PATCH 1/4] ARM: dts: add support for hdmi to exynos4 Rahul Sharma
[not found] ` <1359110384-28402-2-git-send-email-rahul.sharma-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-01-25 17:40 ` Thomas Abraham
2013-01-28 6:55 ` Rahul Sharma
2013-01-28 8:44 ` Tomasz Figa
2013-01-28 9:23 ` Rahul Sharma
2013-01-28 18:48 ` Tomasz Figa
2013-01-27 20:54 ` Sylwester Nawrocki
2013-01-28 6:19 ` Rahul Sharma
2013-01-29 20:42 ` Sylwester Nawrocki
2013-01-31 8:09 ` Rahul Sharma
2013-01-31 22:25 ` Kukjin Kim [this message]
2013-02-01 4:04 ` Rahul Sharma
2013-01-25 10:39 ` [PATCH 2/4] ARM: dts: add support for mixer " Rahul Sharma
2013-01-27 21:04 ` Sylwester Nawrocki
2013-01-28 6:44 ` Rahul Sharma
2013-01-28 8:38 ` Tomasz Figa
2013-01-29 20:15 ` Sylwester Nawrocki
2013-01-29 20:24 ` Sylwester Nawrocki
2013-01-31 8:33 ` Rahul Sharma
2013-01-25 10:39 ` [PATCH 3/4] ARM: dts: add support for hdmi-ddc to exynos4412-origen Rahul Sharma
2013-01-27 20:37 ` Sylwester Nawrocki
2013-01-25 10:39 ` [PATCH 4/4] ARM: dts: add support for hdmi-phy to exynos4412 Rahul Sharma
2013-01-27 20:43 ` [PATCH 0/4] 0/4] ARM: dts: add support for hdmi " Sylwester Nawrocki
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='0aff01ce0001$edc8f320$c95ad960$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=inki.dae@samsung.com \
--cc=joshi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=r.sh.open@gmail.com \
--cc=rahul.sharma@samsung.com \
--cc=sylvester.nawrocki@gmail.com \
--cc=t.figa@samsung.com \
--cc=t.stanislaws@samsung.com \
--cc=thomas.ab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox