netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Woojung.Huh@microchip.com, netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] net: phy: Support for non-HW interrupt devices
Date: Fri, 8 Jan 2016 12:27:02 -0800	[thread overview]
Message-ID: <56901B96.8020606@gmail.com> (raw)
In-Reply-To: <20160108192436.GB26321@lunn.ch>

Hello Andrew,

Le 08/01/2016 11:24, Andrew Lunn a écrit :
>> That seems like an elegant way to solve the problem, without adding code
>> in the PHY library that does not use the interrupt API, but it also
>> seems to me like there are some other potential issues associated with
>> doing that:
> 
> Hi Florian
> 
> I don't want to hijack this thread with DSA stuff. Plus you gave me
> some ideas for improvements :-)
> 
> Lets come back to this in a couple of weeks once i have the DSA
> proposal patches rebased on mdio device, and i've played a bit more.

Sounds good, I will send some patches shortly which really fix the PHY
state machine not to poll PHYs configured with PHY_IGNORE_INTERRUPT and
fixing phy_mac_interrupt() to be callable in hard IRQ context (finally).

Maybe these patches can help Woojung get what he needs for his driver.
-- 
Florian

  reply	other threads:[~2016-01-08 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 23:14 [PATCH] net: phy: Support for non-HW interrupt devices Woojung.Huh
2016-01-08  0:42 ` Andrew Lunn
2016-01-08  2:08   ` Florian Fainelli
2016-01-08  3:25     ` Woojung.Huh
2016-01-08 15:51       ` Andrew Lunn
2016-01-08 15:58         ` Woojung.Huh
2016-01-08 19:24     ` Andrew Lunn
2016-01-08 20:27       ` Florian Fainelli [this message]
2016-01-08 20:30         ` Woojung.Huh
2016-01-08 21:36         ` Andrew Lunn

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=56901B96.8020606@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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).