linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Emil Medve <Emilian.Medve@Freescale.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Xie Shaohui-B21989 <Shaohui.Xie@Freescale.com>,
	Liberman Igal-B31950 <Igal.Liberman@Freescale.com>
Subject: Re: [PATCH] [v2] power/fsl: add MDIO dt binding for FMan
Date: Mon, 22 Dec 2014 03:42:10 -0600	[thread overview]
Message-ID: <1419241330.5581.162.camel@freescale.com> (raw)
In-Reply-To: <5497E645.7010500@Freescale.com>

On Mon, 2014-12-22 at 03:37 -0600, Emil Medve wrote:
> Hello Scott,
> 
> 
> On 12/22/2014 02:32 AM, Scott Wood wrote:
> > On Mon, 2014-12-22 at 02:20 -0600, Emil Medve wrote:
> >> For the purpose of an example in the binding document, I suggest we just
> >> stick with the IEEE standard frequency.
> > 
> > The whole reason for this property existing in the device tree is
> > non-standard frequencies.
> 
> While the standard claims 2.5 MHz, most MDIO controllers and PHY devices
> support frequencies well beyond the standard. Specifying a lower then
> the standard frequency for the benefit of some errata is just one side
> of this property

The erratum was (until now) the only claimed reason for it.  If there
are other reasons why one would specify a different frequency (in
particular, that relate to hardware description), please elaborate.

> >> We can continue this conversation about errata handling when we submit
> >> the code relevant to this binding (and the FMan v3 support)
> > 
> > It affects the binding, so let's discuss it now please.
> 
> I think this specific (unpublished yet) errata has less bearing on the
> binding then you might believe. This is mostly about providing a
> common/default frequency supported by all the devices on some board

What reason other than an erratum would there be for the standard
frequency not being supported?

-Scott

  reply	other threads:[~2014-12-22  9:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  9:53 [PATCH] [v2] power/fsl: add MDIO dt binding for FMan shh.xie
2014-11-20 13:00 ` Shaohui Xie
2014-11-26  1:49 ` Scott Wood
2014-11-26  2:10   ` Shaohui Xie
2014-12-18 12:53   ` Shaohui Xie
2014-12-18 22:01     ` Scott Wood
2014-12-19  7:23       ` Shaohui Xie
2014-12-19 23:15         ` Scott Wood
2014-12-22  2:31           ` Shaohui Xie
2014-12-22  8:20             ` Emil Medve
2014-12-22  8:32               ` Scott Wood
2014-12-22  8:56                 ` Shaohui Xie
2014-12-22  9:37                 ` Emil Medve
2014-12-22  9:42                   ` Scott Wood [this message]
2014-12-22 11:08                     ` Emil Medve
2014-12-22 21:25                       ` Scott Wood
2014-12-23  7:35                         ` Shaohui Xie
2014-12-23  8:08                           ` Scott Wood
2014-12-23  8:17                             ` Shaohui Xie

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=1419241330.5581.162.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=Emilian.Medve@Freescale.com \
    --cc=Igal.Liberman@Freescale.com \
    --cc=Shaohui.Xie@Freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linuxppc-dev@lists.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).