From: Emil Medve <Emilian.Medve@Freescale.com>
To: Scott Wood <scottwood@Freescale.com>
Cc: devicetree@vger.kernel.org,
Kanetkar Shruti-B44454 <Shruti@Freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 5/6] powerpc/corenet: Add DPAA FMan support to the SoC device tree(s)
Date: Thu, 8 May 2014 00:18:00 -0500 [thread overview]
Message-ID: <536B1388.2070006@Freescale.com> (raw)
In-Reply-To: <1399504442.15726.353.camel@snotra.buserror.net>
Hello Scott,
On 05/07/2014 06:14 PM, Scott Wood wrote:
> On Tue, 2014-05-06 at 01:28 -0500, Emil Medve wrote:
>> Hello Scott,
>>
>>
>> On 05/05/2014 06:34 PM, Scott Wood wrote:
>>> On Sun, 2014-05-04 at 05:59 -0500, Emil Medve wrote:
>>>> Anyway, most days PHYs can be discovered so they don't use/need
>>>> compatible properties. That's I guess part of the reason we don't have
>>>> bindings for them PHY nodes
>>>
>>> I don't see why there couldn't be a compatible that describes the
>>> standard programming interface.
>>
>> Because it can be detected at runtime and I guess stuff like that should
>> stay out of the device tree. I'm using PCI as an analogy here
>
> But in this case aren't you using a standardized component of the
> programming model itself to probe the specific PHY type? I think a
> better analogy is the "cfi-flash" compatible.
Well, to speak your language,
Documentation/devicetree/bindings/net/phy.txt claims the 'compatible' to
be optional, case in which at least 'ethernet-phy-ieee802.3-c22' is
implied. 'ethernet-phy-ieee802.3-c22' (1 Gb/s MDIO/PHY) conveys the
standardized programming model that allows probing
Cheers,
WARNING: multiple messages have this Message-ID (diff)
From: Emil Medve <Emilian.Medve-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
To: Scott Wood <scottwood-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
Cc: Kanetkar Shruti-B44454
<Shruti-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: [PATCH 5/6] powerpc/corenet: Add DPAA FMan support to the SoC device tree(s)
Date: Thu, 8 May 2014 00:18:00 -0500 [thread overview]
Message-ID: <536B1388.2070006@Freescale.com> (raw)
In-Reply-To: <1399504442.15726.353.camel-88ow+0ZRuxG2UiBs7uKeOtHuzzzSOjJt@public.gmane.org>
Hello Scott,
On 05/07/2014 06:14 PM, Scott Wood wrote:
> On Tue, 2014-05-06 at 01:28 -0500, Emil Medve wrote:
>> Hello Scott,
>>
>>
>> On 05/05/2014 06:34 PM, Scott Wood wrote:
>>> On Sun, 2014-05-04 at 05:59 -0500, Emil Medve wrote:
>>>> Anyway, most days PHYs can be discovered so they don't use/need
>>>> compatible properties. That's I guess part of the reason we don't have
>>>> bindings for them PHY nodes
>>>
>>> I don't see why there couldn't be a compatible that describes the
>>> standard programming interface.
>>
>> Because it can be detected at runtime and I guess stuff like that should
>> stay out of the device tree. I'm using PCI as an analogy here
>
> But in this case aren't you using a standardized component of the
> programming model itself to probe the specific PHY type? I think a
> better analogy is the "cfi-flash" compatible.
Well, to speak your language,
Documentation/devicetree/bindings/net/phy.txt claims the 'compatible' to
be optional, case in which at least 'ethernet-phy-ieee802.3-c22' is
implied. 'ethernet-phy-ieee802.3-c22' (1 Gb/s MDIO/PHY) conveys the
standardized programming model that allows probing
Cheers,
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-08 5:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 12:21 [PATCH 1/6] powerpc/corenet: Enable muxing MDIO buses via GPIO Shruti Kanetkar
2014-04-18 12:21 ` Shruti Kanetkar
2014-04-18 12:21 ` [PATCH 2/6] powerpc/corenet: Enable muxing MDIO buses via FPGA Shruti Kanetkar
2014-04-18 12:21 ` Shruti Kanetkar
2014-04-18 12:21 ` [PATCH 3/6] net/fsl_pq_mdio: Document supported compatibles Shruti Kanetkar
2014-04-18 12:21 ` Shruti Kanetkar
2014-04-18 12:21 ` [PATCH 4/6] powerpc/corenet: Create the dts components for the DPAA FMan Shruti Kanetkar
2014-04-18 12:21 ` Shruti Kanetkar
2014-04-21 22:11 ` Scott Wood
2014-04-21 22:11 ` Scott Wood
[not found] ` <1398118262.1694.188.camel__8135.6513932862$1398128944$gmane$org@snotra.buserror.net>
2014-05-03 10:02 ` Emil Medve
2014-05-03 10:02 ` Emil Medve
2014-05-05 23:25 ` Scott Wood
2014-05-05 23:25 ` Scott Wood
2014-05-06 5:54 ` Emil Medve
2014-05-06 5:54 ` Emil Medve
2014-05-07 2:54 ` Scott Wood
2014-05-07 2:54 ` Scott Wood
2014-05-08 3:23 ` Emil Medve
2014-05-08 3:23 ` Emil Medve
2014-05-08 3:36 ` Scott Wood
2014-05-08 3:36 ` Scott Wood
2014-05-08 4:31 ` Emil Medve
2014-05-08 4:31 ` Emil Medve
2014-04-18 12:21 ` [PATCH 5/6] powerpc/corenet: Add DPAA FMan support to the SoC device tree(s) Shruti Kanetkar
2014-04-18 12:21 ` Shruti Kanetkar
2014-04-21 22:14 ` Scott Wood
2014-04-21 22:14 ` Scott Wood
[not found] ` <1398118442.1694.190.camel__272.432543761347$1398129129$gmane$org@snotra.buserror.net>
2014-05-04 10:59 ` Emil Medve
2014-05-04 10:59 ` Emil Medve
2014-05-05 23:34 ` Scott Wood
2014-05-05 23:34 ` Scott Wood
2014-05-06 6:28 ` Emil Medve
2014-05-06 6:28 ` Emil Medve
2014-05-06 7:40 ` Joakim Tjernlund
2014-05-06 7:40 ` Joakim Tjernlund
2014-05-07 23:14 ` Scott Wood
2014-05-07 23:14 ` Scott Wood
2014-05-08 5:18 ` Emil Medve [this message]
2014-05-08 5:18 ` Emil Medve
2014-04-18 12:21 ` [PATCH 6/6] powerpc/corenet: Add MDIO bus muxing support to the board " Shruti Kanetkar
2014-04-18 12:21 ` Shruti Kanetkar
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=536B1388.2070006@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=Shruti@Freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@Freescale.com \
/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.