From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Xander Huff <xander.huff@ni.com>, f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
brad.mouring@ni.com, Nathan Sullivan <nathan.sullivan@ni.com>
Subject: Re: [PATCH] phy: request shared IRQ
Date: Wed, 24 Aug 2016 21:41:07 +0300 [thread overview]
Message-ID: <e2248086-6087-0fcd-1338-8f6463943c62@cogentembedded.com> (raw)
In-Reply-To: <1472061216-11111-1-git-send-email-xander.huff@ni.com>
Hello.
On 08/24/2016 08:53 PM, Xander Huff wrote:
> From: Nathan Sullivan <nathan.sullivan@ni.com>
>
> On hardware with multiple PHY devices hooked up to the same IRQ line, allow
> them to share it.
Note that it had been allowed until my (erroneous?) commit
33c133cc7598e60976a069344910d63e56cc4401 ("phy: IRQ cannot be shared"), so I'd
like this commit just reverted instead...
I'm not sure now what was the reason I concluded that the IRQ sharing was
impossible... most probably I thought that the kernel IRQ handling code exited
the loop over the IRQ actions once IRQ_HANDLED was returned -- which is
obviously not so in reality...
> Signed-off-by: Nathan Sullivan <nathan.sullivan@ni.com>
> Signed-off-by: Xander Huff <xander.huff@ni.com>
> Acked-by: Ben Shelton <ben.shelton@ni.com>
> Acked-by: Jaeden Amero <jaeden.amero@ni.com>
[...]
MBR, Sergei
next prev parent reply other threads:[~2016-08-24 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 17:53 [PATCH] phy: request shared IRQ Xander Huff
2016-08-24 18:41 ` Sergei Shtylyov [this message]
2016-08-24 21:15 ` Xander Huff
2016-08-24 21:47 ` [PATCH v2] Revert "phy: IRQ cannot be shared" Xander Huff
2016-08-25 23:54 ` 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=e2248086-6087-0fcd-1338-8f6463943c62@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=brad.mouring@ni.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan.sullivan@ni.com \
--cc=netdev@vger.kernel.org \
--cc=xander.huff@ni.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).