From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: dts: vf610-zii-dev-rev-b: add interrupts for 88e1545 PHY
Date: Thu, 21 Dec 2017 10:06:26 +0100 [thread overview]
Message-ID: <20171221090626.GC6683@lunn.ch> (raw)
In-Reply-To: <E1eRnWr-0006VS-1m@rmk-PC.armlinux.org.uk>
On Wed, Dec 20, 2017 at 11:12:01PM +0000, Russell King wrote:
> The 88e1545 PHY has its interrupts wired to the VF610, so we might as
> well use them.
>
> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> ---
> This is certainly not correct, as all PHYs on this device share the
> same interrupt line, but we can't specify the pinmux settings
> individually on each PHY. How should this be handled?
Hi Russell
You could put it as a hog on the gpio controller node. However, i
don't think that is much better.
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2017-12-21 9:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 23:11 [PATCH 0/4] vf610-zii-dev updates Russell King - ARM Linux
2017-12-20 23:11 ` [PATCH 1/4] ARM: dts: vf610-zii-dev: enable edma1 Russell King
2017-12-20 23:11 ` [PATCH 2/4] ARM: dts: vf610-zii-dev-rev-b: fix interrupt for GPIO expander Russell King
2017-12-21 9:00 ` Andrew Lunn
2017-12-20 23:11 ` [PATCH 3/4] ARM: dts: vf610-zii-dev-rev-b: add PHYs for switch2 Russell King
2017-12-21 9:01 ` Andrew Lunn
2017-12-21 12:15 ` Linus Walleij
2017-12-20 23:12 ` [PATCH 4/4] ARM: dts: vf610-zii-dev-rev-b: add interrupts for 88e1545 PHY Russell King
2017-12-21 9:06 ` Andrew Lunn [this message]
2017-12-21 12:32 ` Linus Walleij
2017-12-21 13:40 ` Andrew Lunn
2017-12-21 17:32 ` Russell King - ARM Linux
2017-12-21 22:53 ` Linus Walleij
2017-12-22 0:14 ` Russell King - ARM Linux
2017-12-22 0:20 ` Florian Fainelli
2017-12-22 11:21 ` Russell King - ARM Linux
2017-12-22 14:16 ` [PATCH 0/4] vf610-zii-dev updates Russell King - ARM Linux
2017-12-24 18:47 ` Stefan Agner
2017-12-26 8:48 ` Shawn Guo
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=20171221090626.GC6683@lunn.ch \
--to=andrew@lunn.ch \
--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 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).