Re: [PATCH v2 4/5] mx6cuboxi: fixup dtb ethernet phy nodes before booting an OS

2022-06-16 Thread Stefano Babic
On 16.06.22 10:44, Josua Mayer wrote: Hi Stefano, Thank you for applying this patchset. This patch had a functional flaw that I was intending to address in v3. Instead I have now followed up with a separate patch: [PATCH] mx6cuboxi: fix board detection while patching device-tree phy nodes Pl

Re: [PATCH v2 4/5] mx6cuboxi: fixup dtb ethernet phy nodes before booting an OS

2022-06-16 Thread Josua Mayer
Hi Stefano, Thank you for applying this patchset. This patch had a functional flaw that I was intending to address in v3. Instead I have now followed up with a separate patch: [PATCH] mx6cuboxi: fix board detection while patching device-tree phy nodes Please make sure this one is added too. sin

[PATCH v2 4/5] mx6cuboxi: fixup dtb ethernet phy nodes before booting an OS

2022-06-15 Thread sbabic
> SoM revision 1.9 has replaced the ar8035 phy address 0 with an adin1300 > at address 1. Because early SoMs had a hardware flaw, the ar8035 can > also appear at address 4 - making it a total of 3 phy nodes in the DTB. > To avoid confusing Linux with probe errors, fixup the dtb to only enable > the

Re: [PATCH v2 4/5] mx6cuboxi: fixup dtb ethernet phy nodes before booting an OS

2022-05-19 Thread Josua Mayer
Hold off on this one, I found a mistake in the switch case below. While fully functional, it does enable both phy nodes for addresses 0 and 4 unconditionally. Cubox requires both, as do potentially any derivate devices - but the HummingBoards do not. Am 19.05.22 um 12:31 schrieb Josua Mayer:

[PATCH v2 4/5] mx6cuboxi: fixup dtb ethernet phy nodes before booting an OS

2022-05-19 Thread Josua Mayer
SoM revision 1.9 has replaced the ar8035 phy address 0 with an adin1300 at address 1. Because early SoMs had a hardware flaw, the ar8035 can also appear at address 4 - making it a total of 3 phy nodes in the DTB. To avoid confusing Linux with probe errors, fixup the dtb to only enable the phy node