devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Sylwester Nawrocki' <s.nawrocki@samsung.com>,
	'Thomas Abraham' <thomas.abraham@linaro.org>,
	'Shaik Ameer Basha' <shaik.ameer@samsung.com>,
	linux-samsung-soc@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org, sy0816.kang@samsung.com,
	olofj@google.com, thomas.ab@samsung.com, sachin.kamat@linaro.org,
	joshi@samsung.com, shaik.samsung@gmail.com,
	sungchun.kang@samsung.com, Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH v3 2/2] ARM: EXYNOS: Add Gscaler device from DT
Date: Wed, 01 Aug 2012 21:03:02 +0200	[thread overview]
Message-ID: <50197D66.1050108@gmail.com> (raw)
In-Reply-To: <036f01cd6fc4$120a9910$361fcb30$%kim@samsung.com>

Hi Kgene,

Cc: Rob Herring

On 08/01/2012 11:00 AM, Kukjin Kim wrote:
>>>>> +* Samsung Exynos5 Gscaler device
>>>>> +
>>>>> +Gscaler is used for scaling and color space conversion on EXYNOS5
>> SoCs.
>>>>> +
>>>>> +Required properties:
>>>>> +- compatible: should be "samsung,exynos5250-gsc"
>>>>
>>>> IMO, should be "samsung,exynos5-gsc" because upcoming EXYNOS5 SoCs can
>> use
>>>> same gscaler driver.
>>
>> In addition to the below explanation, perhaps it's obvious, but the driver
>> can claim compatibility with multiple devices, i.e. match with multiple
>> 'compatible' properties.
>>
> 
> The name of exact model is 'gscaler' for EXYNOS5 SoCs not only for
> EXYNOS5250. So the driver which has been submitted is also 'exynos-gsc' not
> 'exynos5250-gsc'. Note that there is no gscaler on EXYNOS4 SoCs now, it can
> be either 'exynos5-gsc' or 'exynos-gsc'. In addition, since some
> peripherals/drivers can be used for multiple SoCs and actually it does, I'm
> still thinking the compatible should be represent its usage. I don't know
> why restricted name is much clearer. And if multiple 'compatible' is
> required, we can add it later.

Sorry, but I cannot agree with that. :) There is no exynos5 SoC, it's just
a common name for the whole series that includes: exynos5250, exynos5450 ones 
and more. We shouldn't use such common name for just a subset of exynos5 chips, 
in case different GScaler versions get deployed in future SoCs.

It wouldn't be clear what specific SoCs the "samsung,exynos5-gsc" compatible 
string applies to, would it ? I believe there are already minor differences
in GScaler parameters on currently available exynos5 SoC. The variant data
structures are used to handle this and the compatible string determines which
variant data structure is selected during driver's initialization.
If you use a wildcard 'compatible' string this won't be possible any more.

Also it would look odd IMO to have two compatible strings like:
compatible = "samsung,exynos5-gsc", "samsung,exynos5400-gsc";

Please also see:
http://devicetree.org/Device_Tree_Usage#Understanding_the_compatible_Property

--

Regards,
Sylwester

  reply	other threads:[~2012-08-01 19:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 13:08 [PATCH v3 0/2] Add device tree and clock support for Gscaler Shaik Ameer Basha
2012-07-20 13:08 ` [PATCH v3 1/2] ARM: EXYNOS: Add " Shaik Ameer Basha
2012-08-01  6:24   ` Kukjin Kim
2012-08-01  7:07     ` Shaik Ameer Basha
2012-07-20 13:08 ` [PATCH v3 2/2] ARM: EXYNOS: Add Gscaler device from DT Shaik Ameer Basha
2012-08-01  6:40   ` Kukjin Kim
2012-08-01  7:10     ` Shaik Ameer Basha
2012-08-01  7:48     ` Thomas Abraham
2012-08-01  8:15       ` Kukjin Kim
2012-08-01  8:18       ` Sylwester Nawrocki
2012-08-01  9:00         ` Kukjin Kim
2012-08-01 19:03           ` Sylwester Nawrocki [this message]
     [not found]             ` <50197D66.1050108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-02 16:33               ` Olof Johansson
2012-08-02 23:40                 ` Sylwester Nawrocki
2012-08-06  6:27                   ` Shaik Ameer Basha
2012-08-06 19:09                     ` Sylwester Nawrocki
2012-08-07 10:01                       ` Kukjin Kim
2012-08-11  4:08                       ` Kukjin Kim

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=50197D66.1050108@gmail.com \
    --to=sylvester.nawrocki@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=joshi@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olofj@google.com \
    --cc=rob.herring@calxeda.com \
    --cc=s.nawrocki@samsung.com \
    --cc=sachin.kamat@linaro.org \
    --cc=shaik.ameer@samsung.com \
    --cc=shaik.samsung@gmail.com \
    --cc=sungchun.kang@samsung.com \
    --cc=sy0816.kang@samsung.com \
    --cc=thomas.ab@samsung.com \
    --cc=thomas.abraham@linaro.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;
as well as URLs for NNTP newsgroup(s).