On 11/22/21 11:36, Ramon Fried wrote:
On Mon, Nov 22, 2021 at 9:40 AM Michal Simek wrote:
On 11/21/21 20:11, Ramon Fried wrote:
On Thu, Nov 18, 2021 at 2:06 PM Michal Simek wrote:
There are flying two configurations around.
Can you rephrase ? I don't understand.
The first configura
On Mon, Nov 22, 2021 at 9:40 AM Michal Simek wrote:
>
>
>
> On 11/21/21 20:11, Ramon Fried wrote:
> > On Thu, Nov 18, 2021 at 2:06 PM Michal Simek
> > wrote:
> >>
> >> There are flying two configurations around.
> > Can you rephrase ? I don't understand.
>
> The first configuration is
> eth {
>
On 11/21/21 20:11, Ramon Fried wrote:
On Thu, Nov 18, 2021 at 2:06 PM Michal Simek wrote:
There are flying two configurations around.
Can you rephrase ? I don't understand.
The first configuration is
eth {
phy-handle = <&phy0>;
phy0: ethernet-phy@21 {
...
On Thu, Nov 18, 2021 at 2:06 PM Michal Simek wrote:
>
> There are flying two configurations around.
Can you rephrase ? I don't understand.
> The first (already supported) has phy as subnode of gem node.
> The second has mdio subnode (with mdio name) which has phy subnode.
>
> This patch adds suppo
There are flying two configurations around.
The first (already supported) has phy as subnode of gem node.
The second has mdio subnode (with mdio name) which has phy subnode.
This patch adds support for the second case where mdio subnode
is found driver will look at its parent to find out which gem
5 matches
Mail list logo