From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/4 v2] powerpc: document max-speed and interface-type properties
Date: Wed, 18 Apr 2007 12:34:27 +0200 [thread overview]
Message-ID: <524e7cf7aec7be8289ab2f99df8a0776@kernel.crashing.org> (raw)
In-Reply-To: <20070417201350.12727df7.kim.phillips@freescale.com>
>>> sorry, I disagree; for me, a compatible entry in the PHY node would
>>> look
>>> something like "marvell"
>>
>> which would be completely wrong
>>
> that depends on what degree the manufacturer's PHYs are compatible.
No, if all there PHYs are compatible (and you have some
guarantee that all there future PHYs will be as well!)
it should read "marvell-phy" (or better, "MRVL,ethernet-phy"
or something similar).
>>> or "m88e11x1".
>>
>> It should be something like "m88e11x1\0m88e1xxx\0rgmii" instead.
>
> m88e11x1 implies rgmii, including all the other interfaces the PHY
> supports (gmii, mii, tbi, etc.).
If you don't put the less-specific entries there, only clients
(OSes) that know about the exact name can use that PHY. So if
there is a minor upgrade of you board and it has a m88e11x2
instead, your OS needs an update to work with your new device
tree. Not an ideal situation.
> ..but I'm not interested in specifying what interfaces the PHY
> supports.
But you *have* to. The device tree describes the hardware,
it is not a configuration file for Linux to use as it sees fit.
>>>> max-speed of connection = min(max-speed of enet, max-speed
>>>> of PHY) -- and both of those are implied by their respective
>>>> "compatible" properties.
>>>
>>> Again, max-speed is exclusively for configuring the UCC itself,
>>> regardless of the connection speed.
>>
>> If that is really true, and the value of that property
>> has nothing to do with the MAC<->PHY data channel, it should
>> have a different (not that generic) name.
>
> can you elaborate on why, including an example of what you'd think
> would
> be a better one?
Very generic names should only be used by very generic bindings.
If a very specific device binding (like yours) uses a property
name like that, there is a high chance it will clash with a more
generic binding it uses (PCI, ethernet, network, ...) -- perhaps
with a *future* version of such a binding.
Also, it isn't a great name /an sich/: "max-speed" -- maximum
speed of what?
Segher
next prev parent reply other threads:[~2007-04-18 10:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 6:25 [PATCH 1/4 v2] powerpc: document max-speed and interface-type properties Kim Phillips
2007-04-13 17:00 ` Kumar Gala
2007-04-13 17:36 ` Kim Phillips
2007-04-13 17:42 ` Kumar Gala
2007-04-13 17:52 ` Kim Phillips
2007-04-13 17:59 ` Kumar Gala
2007-04-13 19:02 ` Segher Boessenkool
2007-04-16 15:25 ` Kim Phillips
2007-04-16 15:34 ` Kumar Gala
2007-04-16 15:47 ` Segher Boessenkool
2007-04-16 16:57 ` Kim Phillips
2007-04-16 23:18 ` Segher Boessenkool
2007-04-17 0:31 ` Kim Phillips
2007-04-17 10:25 ` Segher Boessenkool
2007-04-17 20:27 ` Kim Phillips
2007-04-17 23:18 ` Segher Boessenkool
2007-04-18 1:13 ` Kim Phillips
2007-04-18 10:34 ` Segher Boessenkool [this message]
2007-04-18 21:48 ` Kim Phillips
2007-04-20 8:34 ` Segher Boessenkool
2007-04-20 19:13 ` Andy Fleming
2007-04-21 17:22 ` Segher Boessenkool
2007-04-23 16:58 ` Andy Fleming
2007-04-23 21:24 ` Segher Boessenkool
2007-04-16 18:40 ` Andy Fleming
2007-04-16 23:25 ` Segher Boessenkool
2007-04-17 7:04 ` Andy Fleming
2007-04-17 10:40 ` Segher Boessenkool
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=524e7cf7aec7be8289ab2f99df8a0776@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=kim.phillips@freescale.com \
--cc=linuxppc-dev@ozlabs.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).