devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Inki Dae <inki.dae@samsung.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
	"patches@linaro.org" <patches@linaro.org>,
	Sachin Kamat <sachin.kamat@linaro.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH 2/2] drm/exynos: Add device tree based discovery support for G2D
Date: Tue, 05 Feb 2013 10:33:14 +0100	[thread overview]
Message-ID: <5110D1DA.6000100@samsung.com> (raw)
In-Reply-To: <CAAQKjZNLTZSJ8Y0tt2aZPKFESbLGxQ1Z92zkhV_u8nvSXekgtw@mail.gmail.com>

On 02/05/2013 04:03 AM, Inki Dae wrote:
[...]
>> Exynos4210 has same g2d IP (v3.0) as C110 or V210; so the same
>> comptible string will be used for this one too.
>>
>>> And please check if exynos4212 and 4412 SoCs have same fimg-2d ip. 
>>> If it's different, we might need to add ip version property or compatible
>>> string to each dtsi file to identify the ip version.
>>
>> AFAIK, they both have the same IP (v4.1).
>>
> 
> Ok, let's use the below,
> 
> For exynos4210 SoC,
> compatible = "samsung,exynos4210-g2d"

Since S5PV210 (Exynos3110 ??) seems to have same G2D IP, I guess
something like "samsung,s5pv210-g2d" could be used for both
S5PV210 (S5PC110) and Exynos4210 (S5PC210, S5PV310) ?
I'm fine with using "samsung,exynos4210-g2d" for Exynos4210 though.

For instance for tegra SoCs a conventions like "nvidia,tegra<chip>-<ip>",
is used (e.g. "nvidia,tegra20-gr2d").

> For exynos4x12 SoCs,
> compatible = "samsung,exynos4212-g2d"

I'm not sure how well exynos4212 is going to be supported in the kernel.
As Mr Park pointed out, if it is going to be nearly not existent then we
could perhaps go with "samsung,exynos4412-g2d" for Exynos4412 and
"samsung,exynos4212-g2d" for Exynos4212 (as needed). Anyway, I fine
with using "samsung,exynos4212-g2d" for both. I'd like to hear Mr Kim's
opinion on this as well though.

> For exynos5250, 5410 (In case of Exynos5440, I'm not sure that the SoC
> has same ip)
> compatible = "samsung,exynos5250-g2d"
> 
> To other guys,
> The device tree is used by not only v4l2 side but also drm side so we
> should reach an arrangement. So please give me ack if you agree to my
> opinion. Otherwise please, give me your opinions.

It looks good to me, please just see the two remarks above.

--
Regards,
Sylwester

  parent reply	other threads:[~2013-02-05  9:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25  9:55 [PATCH 1/2] [media] s5p-g2d: Add DT based discovery support Sachin Kamat
2013-01-25  9:55 ` [PATCH 2/2] drm/exynos: Add device tree based discovery support for G2D Sachin Kamat
2013-01-30  8:50   ` Inki Dae
2013-01-30 20:51     ` Sylwester Nawrocki
2013-01-31  1:30       ` Inki Dae
2013-01-31 23:47         ` Sylwester Nawrocki
2013-02-01  0:15           ` Kukjin Kim
2013-02-01  1:27             ` Inki Dae
2013-02-01  2:26               ` Stephen Warren
2013-02-01  8:33               ` Sachin Kamat
     [not found]                 ` <CAK9yfHxqqumg-oqH_Ku8Zkf8biWVknF91Su0VkWJJXjvWQ3Jhw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-01 10:54                   ` Sylwester Nawrocki
2013-02-01 11:12                     ` Sachin Kamat
2013-02-01 11:32                       ` Inki Dae
2013-02-01 11:40                         ` Sachin Kamat
2013-02-01 11:52                           ` Inki Dae
2013-02-01 12:58                             ` Inki Dae
     [not found]                               ` <E382E0B5-2695-4293-B264-FB4C54FE4F9D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-02-04 12:04                                 ` Sachin Kamat
2013-02-05  3:03                                   ` Inki Dae
2013-02-05  4:21                                     ` Kyungmin Park
2013-02-05  7:56                                     ` 김승우
2013-02-05  8:32                                     ` Joonyoung Shim
2013-02-05  9:33                                     ` Sylwester Nawrocki [this message]
2013-02-06  4:14                                       ` Sachin Kamat
2013-02-01 17:35                     ` Kukjin Kim
2013-02-01 18:06                     ` Kukjin Kim
2013-01-30 21:38 ` [PATCH 1/2] [media] s5p-g2d: Add DT based discovery support Sylwester Nawrocki
2013-01-31  6:29   ` Sachin Kamat
  -- strict thread matches above, loose matches on Subject: below --
2013-02-06  5:29 [PATCH v2 " Sachin Kamat
2013-02-06  5:29 ` [PATCH v2 2/2] drm/exynos: Add device tree based discovery support for G2D Sachin Kamat
2013-02-12 13:17   ` Inki Dae
     [not found]     ` <CAAQKjZNmUVZnDcy3fbWkairnneOK7dooJT2gn=9++tzS=uhhzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-12 17:22       ` [PATCH " Sachin Kamat

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=5110D1DA.6000100@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=sachin.kamat@linaro.org \
    --cc=sylvester.nawrocki@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).