From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: mvebu: Can we make the orion-mdio clock a requirement?
Date: Mon, 21 Jul 2014 22:23:26 +0200 [thread overview]
Message-ID: <20140721222326.668db913@free-electrons.com> (raw)
In-Reply-To: <53CD743D.9080700@gmail.com>
Dear Sebastian Hesselbarth,
On Mon, 21 Jul 2014 22:12:45 +0200, Sebastian Hesselbarth wrote:
> > However, yes, I tend to agree, making the clock mandatory would
> > probably be a good thing.
>
> We can always pass TCLK on Orion5x if there is a need for a mandatory
> clock. Anyway, IIRC clock framework should now properly return
> -EPROPEDEFER only if there is a clock property set. If there is none,
> the error is different and can be catched on Orion5x.
Yes, I already use tclk on Orion5x for various clock references.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Jason Cooper <jason@lakedaemon.net>,
Gregory Clement <gregory.clement@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: mvebu: Can we make the orion-mdio clock a requirement?
Date: Mon, 21 Jul 2014 22:23:26 +0200 [thread overview]
Message-ID: <20140721222326.668db913@free-electrons.com> (raw)
In-Reply-To: <53CD743D.9080700@gmail.com>
Dear Sebastian Hesselbarth,
On Mon, 21 Jul 2014 22:12:45 +0200, Sebastian Hesselbarth wrote:
> > However, yes, I tend to agree, making the clock mandatory would
> > probably be a good thing.
>
> We can always pass TCLK on Orion5x if there is a need for a mandatory
> clock. Anyway, IIRC clock framework should now properly return
> -EPROPEDEFER only if there is a clock property set. If there is none,
> the error is different and can be catched on Orion5x.
Yes, I already use tclk on Orion5x for various clock references.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-21 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 19:06 mvebu: Can we make the orion-mdio clock a requirement? Ezequiel Garcia
2014-07-21 19:06 ` Ezequiel Garcia
2014-07-21 19:28 ` Thomas Petazzoni
2014-07-21 19:28 ` Thomas Petazzoni
2014-07-21 20:12 ` Sebastian Hesselbarth
2014-07-21 20:12 ` Sebastian Hesselbarth
2014-07-21 20:23 ` Thomas Petazzoni [this message]
2014-07-21 20:23 ` Thomas Petazzoni
2014-07-22 23:46 ` Ezequiel Garcia
2014-07-22 23:46 ` Ezequiel Garcia
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=20140721222326.668db913@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.