Dear Grant Likely,
On Fri, 12 Jul 2013 23:44:21 +0100, Grant Likely wrote:
> I think this discussion is going in the wrong direction. The concept
> of a dummy phy is really a Linux kernel internal detail. Creating some
> kind of dummy MDIO bus node does not describe the hardware.
This is exactly
Le 13/07/2013 00:44, Grant Likely a écrit :
On Wed, Jul 10, 2013 at 6:23 PM, Florian Fainelli wrote:
Hello Thomas,
2013/7/10 Thomas Petazzoni :
Dear Florian Fainelli,
On Wed, 10 Jul 2013 17:29:44 +0100, Florian Fainelli wrote:
[snip]
};
phy1: ethernet-
On Wed, Jul 10, 2013 at 6:23 PM, Florian Fainelli wrote:
> Hello Thomas,
>
> 2013/7/10 Thomas Petazzoni :
>> Dear Florian Fainelli,
>>
>> On Wed, 10 Jul 2013 17:29:44 +0100, Florian Fainelli wrote:
> [snip]
>
>>
>>> > };
>>> >
>>> > phy1: ethernet-phy@1 {
>>> >
Dear Florian Fainelli,
On Fri, 12 Jul 2013 13:05:59 +0100, Florian Fainelli wrote:
> I am talking about scanning the MDIO bus DT nodes, not the entire DT.
> That job is already done by of_mdiobus_probe() to register PHY
> devices, so having a central point where the knowledge of how to treat
> PH
Hello Thomas,
2013/7/12 Thomas Petazzoni :
>> Why not? Since we are already have to scan the entire MDIO bus we are
>> attached to, when we encounter such a PHY node with the special
>> "fixed" properties, we just call fixed_phy_add() with the right
>> parameters and voila. Which is also the reas
Dear Florian Fainelli,
On Wed, 10 Jul 2013 18:23:30 +0100, Florian Fainelli wrote:
> >> - declare all PHY nodes in the system as sub nodes of their belonging
> >> real hardware MDIO bus node
> >> - flag specific PHY nodes as "fixed" with a "fixed-link" boolean for
> >> instance
> >> - if we see
Hello Thomas,
2013/7/10 Thomas Petazzoni :
> Dear Florian Fainelli,
>
> On Wed, 10 Jul 2013 17:29:44 +0100, Florian Fainelli wrote:
[snip]
>
>> > };
>> >
>> > phy1: ethernet-phy@1 {
>> > ... all the properties you listed ...
>> >
Dear Florian Fainelli,
On Wed, 10 Jul 2013 17:29:44 +0100, Florian Fainelli wrote:
> > Should we have something like:
> >
> > mdio-fixed {
> > compatible = "generic,mdio-fixed";
> > phy0: ethernet-phy@0 {
> > ... all the properties y
Hello Thomas,
2013/7/10 Thomas Petazzoni :
[snip]
>> >
>> > It has the same properties as the binding described in:
>> > Documentation/devicetree/bindings/net/fsl-tsec-phy.txt but expressed in a
>> > more explicit way instead of using an array of integers.
>
> And so the fixed-phy driver would l
Dear Florian Fainelli,
On Tue, 09 Jul 2013 19:02:05 +0100, Florian Fainelli wrote:
> > > We have a case of an hardware platform that uses the mvneta network
> > > driver, but instead of the SoC being connected to a PHY, it's connected
> > > directly to a switch, so my understanding is that there'
Widening audience
FlorianLe mardi 9 juillet 2013 17:44:55 Fainelli a écrit :
> Hello Thomas,
>
> 2013/7/9 Thomas Petazzoni :
> > Hello,
> >
> > We have a case of an hardware platform that uses the mvneta network
> > driver, but instead of the SoC being connected to a PHY, it's connected
> > dir
11 matches
Mail list logo
