[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200923.133147.842604978902817779.davem@davemloft.net>
Date: Wed, 23 Sep 2020 13:31:47 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: s.riedmueller@...tec.de
Cc: fugang.duan@....com, kuba@...nel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
c.hemp@...tec.de
Subject: Re: [PATCH] net: fec: Keep device numbering consistent with
datasheet
From: Stefan Riedmueller <s.riedmueller@...tec.de>
Date: Wed, 23 Sep 2020 16:25:28 +0200
> From: Christian Hemp <c.hemp@...tec.de>
>
> Make use of device tree alias for device enumeration to keep the device
> order consistent with the naming in the datasheet.
>
> Otherwise for the i.MX 6UL/ULL the ENET1 interface is enumerated as eth1
> and ENET2 as eth0.
>
> Signed-off-by: Christian Hemp <c.hemp@...tec.de>
> Signed-off-by: Stefan Riedmueller <s.riedmueller@...tec.de>
Device naming and ordering for networking devices was never, ever,
guaranteed.
Use udev or similar.
> @@ -3691,6 +3692,10 @@ fec_probe(struct platform_device *pdev)
>
> ndev->max_mtu = PKT_MAXBUF_SIZE - ETH_HLEN - ETH_FCS_LEN;
>
> + eth_id = of_alias_get_id(pdev->dev.of_node, "ethernet");
> + if (eth_id >= 0)
> + sprintf(ndev->name, "eth%d", eth_id);
You can't ever just write into ndev->name, what if another networking
device is already using that name?
This change is incorrect on many levels.
Powered by blists - more mailing lists