linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Emil Medve <Emilian.Medve@Freescale.com>
To: Scott Wood <scottwood@Freescale.com>,
	Xie Shaohui-B21989 <Shaohui.Xie@Freescale.com>
Cc: Kanetkar Shruti-B44454 <Shruti@Freescale.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2 1/7] dt: Introduce the FMan 10 Gb/s MDIO binding
Date: Sat, 26 Jul 2014 03:17:45 -0500	[thread overview]
Message-ID: <53D36429.4020106@Freescale.com> (raw)
In-Reply-To: <1406318092.29414.116.camel@snotra.buserror.net>

Hello Scott,


On 07/25/2014 02:54 PM, Scott Wood wrote:
> On Thu, 2014-07-24 at 22:11 -0500, Xie Shaohui-B21989 wrote:
>> Hello, Scott, Shruti,
>>
>> There are two types MDIO controllers, each MAC has a corresponding MDIO
>> controller to access internal PHYs inside Serdes, another is dedicated
>> MDIO controller to access external PHYs (PHYs on board or riser card,
>> etc). Current MDIO driver does not distinguish the two controllers, if
>> we need to distinguish the controllers, what could be the proper way?
>> Perhaps a new property is needed in dts?
> 
> Are these different programming models, or just two instances of the
> same type of device, with different things attached?

The controllers are very similar; the FMan v3 MDIO controller is a newer
revision of the FMan v2 10 Gb/s MDIO controller


Cheers,


> -Scott
> 
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2014-07-26  8:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 20:17 [PATCH v2 1/7] dt: Introduce the FMan 10 Gb/s MDIO binding Shruti Kanetkar
2014-07-16 20:17 ` [PATCH v2 2/7] net/fsl_pq_mdio: Document supported compatibles Shruti Kanetkar
2014-07-16 20:17 ` [PATCH v2 3/7] powerpc/corenet: Create the dts components for the DPAA FMan Shruti Kanetkar
2014-07-21 22:13   ` Scott Wood
2014-07-16 20:17 ` [PATCH v2 4/7] powerpc/corenet: Add DPAA FMan support to the SoC device tree(s) Shruti Kanetkar
2014-07-16 20:17 ` [PATCH v2 5/7] powerpc/corenet: Add MDIO bus muxing support to the board " Shruti Kanetkar
2014-07-21 22:45   ` Scott Wood
2014-07-28  6:51     ` Emil Medve
2014-07-29 19:58       ` Scott Wood
2014-07-30 21:52         ` Emil Medve
2014-07-31  2:30           ` Scott Wood
2014-07-31  4:35             ` Emil Medve
2014-07-31  5:28               ` Scott Wood
2014-07-31  5:48                 ` Emil Medve
2014-07-31 18:30                   ` Scott Wood
2014-07-31 18:49                     ` Emil Medve
2014-08-13  8:44                     ` Shaohui Xie
2014-07-16 20:17 ` [PATCH v2 6/7] powerpc/corenet: Enable muxing MDIO buses via GPIO Shruti Kanetkar
2014-07-16 20:17 ` [PATCH v2 7/7] powerpc/corenet: Enable muxing MDIO buses via FPGA Shruti Kanetkar
2014-07-25  3:11 ` [PATCH v2 1/7] dt: Introduce the FMan 10 Gb/s MDIO binding Shaohui Xie
2014-07-25 19:54   ` Scott Wood
2014-07-26  8:17     ` Emil Medve [this message]
2014-07-25 20:00   ` Emil Medve

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=53D36429.4020106@Freescale.com \
    --to=emilian.medve@freescale.com \
    --cc=Shaohui.Xie@Freescale.com \
    --cc=Shruti@Freescale.com \
    --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 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).