All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Olof Johansson <olof@lixom.net>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
	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: Fri, 03 Aug 2012 01:40:51 +0200	[thread overview]
Message-ID: <501B1003.1090003@gmail.com> (raw)
In-Reply-To: <CAOesGMiZMrv4GY=v1WPn_qGZgg=vduO2TbsUOQ6sCah-ZvOg_A@mail.gmail.com>

On 08/02/2012 06:33 PM, Olof Johansson wrote:
> On Wed, Aug 1, 2012 at 12:03 PM, Sylwester Nawrocki
> <sylvester.nawrocki@gmail.com>  wrote:
> 
>> 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";
> 
> In this particular case, since you're saying that there are subtle
> differences between different part numbers, I'm guessing there's good
> reason to go specific, but in general there's no need to avoid
> exynos5-gsc.
> 
> Your example is also false, since the strings would be in reverse
> order (from specific to generic). That would look perfectly normal.

You're right, but my intention was more to say that there would have been 
two entries in the driver's of_match_table, where "samsung,exynos5-gsc"
wouldn't have obvious meaning. Devices within these SoCs tend to differ 
across part numbers and usually there is one common driver handling them.

I can't tell for sure now there are differences, but I would have been
surprised if there wouldn't.

> So, bottom line: I agree in this particular instance, but I disagree
> that it's a hard generic rule.

Thanks, sorry if it sounded like I'm advocating it as a general rule. 
I'm no DT expert whatsoever, but in this particular case it just sounded 
messy to use only exynos5-gsc.

--
Regards,
Sylwester

  reply	other threads:[~2012-08-02 23:40 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
     [not found]             ` <50197D66.1050108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-02 16:33               ` Olof Johansson
2012-08-02 23:40                 ` Sylwester Nawrocki [this message]
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=501B1003.1090003@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=olof@lixom.net \
    --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 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.