From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: zynq: DT: Add Ethernet phys
Date: Fri, 22 Aug 2014 10:48:25 -0600 [thread overview]
Message-ID: <20140822164825.GA1733@obsidianresearch.com> (raw)
In-Reply-To: <d31d72f2-acac-4aa3-b992-fc244ac6db4e@BY2FFO11FD005.protection.gbl>
On Fri, Aug 22, 2014 at 09:31:20AM -0700, S?ren Brinkmann wrote:
> > > - the marvell compatible strings are used in our vendor tree. They
> > > aren't used anywhere but in our vendor tree. I though keeping them is
> > > nice since it identifies the PHY fully. And in case that level of
> > > detail is needed at some point it is already there.
> >
> > DT is complex enough already, don't include useless compatible strings
> > in mainline - people will see and tend to blindly copy. Ideally your
> > vendor tree would use the standard property :|
>
> There are different opinions on this. I also heard to just add such
> strings, so in case this level of differentiation becomes necessary at
> some later point, it is already existing.
In some cases, yes, and they should be docuemented in the binding, of
course.
But there is already a standard compatible string format to uniquely
identify a phy, so in this case another string is not justified, and
just creates confusion about what is correct.
Jason
next prev parent reply other threads:[~2014-08-22 16:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 15:56 [PATCH 1/3] ARM: zynq: DT: Fix Ethernet phy modes Soren Brinkmann
2014-08-20 15:56 ` [PATCH 2/3] ARM: zynq: DT: Move size/address properties to dtsi Soren Brinkmann
2014-08-20 16:00 ` Andreas Färber
2014-08-21 8:42 ` Michal Simek
2014-08-20 15:56 ` [PATCH 3/3] ARM: zynq: DT: Add Ethernet phys Soren Brinkmann
2014-08-21 8:41 ` Michal Simek
2014-08-21 11:32 ` Andreas Färber
2014-08-21 15:49 ` Sören Brinkmann
2014-08-22 16:20 ` Jason Gunthorpe
2014-08-22 16:31 ` Sören Brinkmann
2014-08-22 16:48 ` Jason Gunthorpe [this message]
2014-08-22 20:47 ` Florian Fainelli
2014-08-25 17:46 ` Jason Gunthorpe
2014-08-25 20:21 ` Florian Fainelli
2014-08-29 14:08 ` Michal Simek
2014-08-29 15:18 ` Andreas Färber
2014-08-29 15:35 ` Sören Brinkmann
2014-08-29 15:46 ` Andreas Färber
2014-08-29 17:31 ` Jason Gunthorpe
2014-08-29 18:23 ` Florian Fainelli
2014-08-29 23:22 ` Jason Gunthorpe
2014-08-30 0:43 ` Florian Fainelli
2014-09-01 11:26 ` Michal Simek
2014-08-21 8:42 ` [PATCH 1/3] ARM: zynq: DT: Fix Ethernet phy modes Michal Simek
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=20140822164825.GA1733@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.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).