From: Nishanth Menon <nm@ti.com>
To: "Roger Quadros" <rogerq@ti.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
"Florian Fainelli" <f.fainelli@gmail.com>
Cc: kernel@pengutronix.de, "Andrew F . Davis" <afd@ti.com>,
Sekhar Nori <nsekhar@ti.com>, Suman Anna <s-anna@ti.com>
Subject: Re: [PATCH] phy: add support for a reset-gpio specification
Date: Thu, 12 May 2016 09:05:15 -0500 [thread overview]
Message-ID: <57348D9B.2080200@ti.com> (raw)
In-Reply-To: <57348D05.905@ti.com>
On 05/12/2016 09:02 AM, Roger Quadros wrote:
[...]
>> This looks like the right approach to me at least: I see that TI EVMs
>> will also benefit with this approach.
>>
>
> Agreed. Although on some of our boards we actually need a RESET pulse
> to get the PHY in a sane state. I can send a patch on top for that.
>
> Reviewed-by: Roger Quadros <rogerq@ti.com>
There is an interesting thread starting up on Linux-arm[1] as well - I
guess Uwe can comment on direction.
[1] http://marc.info/?t=146303744800003&r=1&w=2
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2016-05-12 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 10:00 [PATCH] phy: add support for a reset-gpio specification Uwe Kleine-König
2016-05-12 13:50 ` Nishanth Menon
[not found] ` <57348A2A.8070806-l0cyMroinI0@public.gmane.org>
2016-05-12 14:02 ` Roger Quadros
2016-05-12 14:05 ` Nishanth Menon [this message]
2016-05-12 14:16 ` Roger Quadros
2016-05-12 14:25 ` Sergei Shtylyov
2016-05-12 16:14 ` Uwe Kleine-König
2016-05-12 21:41 ` Sergei Shtylyov
2016-05-13 6:26 ` Uwe Kleine-König
2016-05-13 19:10 ` Sergei Shtylyov
2016-05-16 15:33 ` Rob Herring
2016-05-16 17:23 ` David Miller
2016-05-16 17:29 ` Florian Fainelli
[not found] ` <573A0388.2010002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-05-16 18:04 ` David Miller
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=57348D9B.2080200@ti.com \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rogerq@ti.com \
--cc=s-anna@ti.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).