devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: 'Sylwester Nawrocki'
	<sylvester.nawrocki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	'Vivek Gautam'
	<gautamvivek1987-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
	linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	balbi-l0cyMroinI0@public.gmane.org,
	'Rob Herring'
	<rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
	cpgs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
	'Alan Stern'
	<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
	'Vivek Gautam'
	<gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: RE: [PATCH 0/2] usb: exynos: Fix compatible strings used for device
Date: Mon, 21 Jan 2013 21:35:41 -0800	[thread overview]
Message-ID: <054601cdf862$534a8ad0$f9dfa070$@samsung.com> (raw)
In-Reply-To: <50DB811A.8010408-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Sylwester Nawrocki wrote:
> 
> On 12/24/2012 09:13 AM, Vivek Gautam wrote:
> >>>> These two changes look good to me.  For both of them:
> >>>>
> >>>> Reviewed-by: Doug Anderson<dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> >>>
> >>> Well, I have another idea. Yes, I know, specific chip name should be
used.
> >> But
> >>> you know the specific chip name in compatible can cause another
> confusion
> >>> on other SoC which has same IP. So I think, we need to consider to use
> >>> common name or any specific name not chip in compatible for IP/driver
> like
> >>> following?
> >>>
> >>> -     { .compatible = "samsung,exynos-dwc3" },
> >>> +     { .compatible = "samsung,synopsis-dwc3" },
> >>>
> >>> Or if any version or something, how about following?
> >>>
> >>> +     { .compatible = "samsung,dwc-v3" },
> >>>
> > Well, yes the newer SoCs with same IP using the chip name can cause some
> > confusion, but won't it be fine that -
> > "Newer parts using the same core can claim compatibility by
> > including the older string in the compatible list" - as quoted by Grant
Likely
> >
> > Or, can we try another option, using multiple compatible strings for
> > SoC specific
> > in of_match_table, so that we don't create any confusion by using same
> > compatible for newer SoCs also. Like,
> >
> > -     { .compatible = "samsung,exynos-dwc3" },
> > +     { .compatible = "samsung,exynos5250-dwc3" },
> > +     { .compatible =<new SoC using same IP>  },
> 
> Yes, why not just use an SoC name where given IP first appeared ? I
believe
> IP revision numbers are not always well documented. Also when an IP is
> instantiated multiple times in specific SoC, its revision number might not
> be sufficient to determine the system integration details for each
instance.
> I think having version for some devices and SoC name for others just adds
> to the confusion. Thus using specific chip name in the compatible property
> seems more clear to me.
> 
Well, I don't think so. Let's see the DMAC PL330. Its compatible is
"arm,pl330" and "arm,primecell" not SoC/Chip name. I think DWC is a same
case or at least similar.

You know, the DWC is a IP from Synopsis and I _Believe_ it has a kind of
version and it can be used for identify.

Thanks.

- Kukjin

  parent reply	other threads:[~2013-01-22  5:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 14:52 [PATCH 0/2] usb: exynos: Fix compatible strings used for device Vivek Gautam
     [not found] ` <1355410348-5129-1-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-12-13 14:52   ` [PATCH 1/2] usb: ehci-s5p/ohci-exynos: Fix compatible strings for the device Vivek Gautam
2012-12-13 16:09     ` Vivek Gautam
2012-12-19 13:47       ` Vivek Gautam
2012-12-13 14:52   ` [PATCH 2/2] usb: dwc3-exynos: " Vivek Gautam
2012-12-13 16:10     ` Vivek Gautam
2012-12-19 13:48       ` Vivek Gautam
2012-12-15  7:20   ` [PATCH 0/2] usb: exynos: Fix compatible strings used for device Grant Likely
2012-12-19 13:46     ` Vivek Gautam
     [not found]       ` <CAFp+6iHaYpinaq8K7rf1GxOJoap6Rd8kGcJn4UmHU28BjTCAsA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-21  8:14         ` Vivek Gautam
2012-12-21 17:39           ` Doug Anderson
2012-12-23 23:15             ` Kukjin Kim
2012-12-24  8:13               ` Vivek Gautam
2012-12-26 22:58                 ` Sylwester Nawrocki
     [not found]                   ` <50DB811A.8010408-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-15  8:28                     ` Vivek Gautam
2013-01-22  5:35                     ` Kukjin Kim [this message]
2013-01-22  5:48                       ` Vivek Gautam
2013-01-22  8:48                         ` Felipe Balbi
     [not found]                           ` <20130122084817.GC16143-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-01-22 22:04                             ` Kukjin Kim
2013-01-23  9:50                               ` Felipe Balbi
     [not found]                                 ` <20130123095021.GB22054-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-01-23 12:20                                   ` Vivek Gautam
2013-01-23 12:40                                     ` Sylwester Nawrocki
     [not found]                                       ` <50FFDA2B.4010506-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-01-23 13:16                                         ` Vivek Gautam
2013-01-22  8:49                       ` Sylwester Nawrocki
2012-12-13 16:07 ` Vivek Gautam

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='054601cdf862$534a8ad0$f9dfa070$@samsung.com' \
    --to=kgene.kim-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
    --cc=balbi-l0cyMroinI0@public.gmane.org \
    --cc=cpgs-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=gautamvivek1987-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
    --cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org \
    --cc=sylvester.nawrocki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).