From: Andrew Lunn <andrew@lunn.ch>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: netdev@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: ID of (former "National") TI's PHY DP83848
Date: Mon, 30 Apr 2018 14:22:26 +0200 [thread overview]
Message-ID: <20180430122226.GA10066@lunn.ch> (raw)
In-Reply-To: <201804271351.05091.jbe@pengutronix.de>
On Fri, Apr 27, 2018 at 01:51:04PM +0200, Juergen Borleis wrote:
> Hi,
>
> I have worked on a DP83848 variant without an interrupt line. While at it, I
> read through all datasheets of existing variants of the DP83848 phy.
>
> Here is what I've found so far:
>
> +--------------+--------------+--------+-----+
> | Variant | Phy ID | Note | IRQ |
> +--------------+--------------+--------+-----+
> | DP83848H | 0x20005c90 | MINI | NO |
> +--------------+--------------+--------+-----+
> | DP83848J | 0x20005c90 | MINI | NO |
> +--------------+--------------+--------+-----+
> | DP83848K | 0x20005c90 | MINI | NO |
> +--------------+--------------+--------+-----+
> | DP83848M | 0x20005c90 | MINI | NO |
> +--------------+--------------+--------+-----+
> | DP83848T | 0x20005c90 | MINI | NO |
> +--------------+--------------+--------+-----+
> | DP83848EP | 0x20005c90 | | YES |
> +--------------+--------------+--------+-----+
> | DP83848HT | 0x20005c90 | | YES |
> +--------------+--------------+--------+-----+
> | DP83848Q | 0x20005ca2 | MINI | NO |
> +--------------+--------------+--------+-----+
> | DP83848V | 0x20005ca2 | | YES |
> +--------------+--------------+--------+-----+
> | DP83848C | 0x20005ca2 | | YES |
> +--------------+--------------+--------+-----+
>
> "MINI" means a less pin count variant.
> "IRQ"-"YES" means, the device has a interrupt line,
> "IRQ"-"NO" means, the device has no interrupt line.
>
> How to deal with interrupts, if the device itself has no interrupt line (and
> uses the same phy ID)? How to deal with the same Phy ID used for different
> devices and different features?
Hi Juergen
Interrupts are always in two parts. One part is the PHY driver side,
saying it supports interrupts, providing the functions to configure
interrupts, check if an interrupt did happen, and acknowledge it. The
second part is somehow specifying which specific interrupt is used,
via device tree, or platform data. Only when both are supplied will
PHYLIB try to use the interrupts.
So it should be safe if they PHY driver always says it supports
interrupts. The platform then must not provide an interrupt number
when there is not one.
As for other features, you probably need to take same approach. How
does a mini differ? Less LEDs? Only RGMII, not GMII?
Andrew
prev parent reply other threads:[~2018-04-30 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 11:51 ID of (former "National") TI's PHY DP83848 Juergen Borleis
2018-04-30 12:22 ` Andrew Lunn [this message]
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=20180430122226.GA10066@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=jbe@pengutronix.de \
--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).