08:27 <qschulz> diederik: if the m.2 e-key is always on the PCB, it probably should be in the main DTS

08:27 <qschulz> if there is a child node specific to some module connected to it, in an overlay likely yes

08:28 <qschulz> I vaguely remember naoki talking about specific WiFi+BT modules with some wifi/bt enable that may not be stable if you don't buy from Radxa directly (the m.2 spec doesn't say which pin is for which purpose)

08:30 <diederik> qschulz: yeah, I made a similar realization yesterday. Because according to that same logic, I would need to put the M.2 M-key (which I do use) in an overlay as well

08:36 <diederik> I guess I'll have to learn to ignore kernel errors ;-P

08:37 <diederik> On the bright side, I did learn how I could use DT-overlays :)

08:38 <qschulz> diederik: and I learned a few days ago to NOT use lhandles in overlays :)

08:38 <qschulz> lhandles is what's used in /aliases essentially

08:38 <qschulz> I don't know if lhandle is the proper term, the spec doesn't say anything about it

08:39 <qschulz> it's NOT a phandle as it's resolved to a string containing the path to the node you point at

08:39 <diederik> I hadn't seen that word/term before, but that says very little LOL

08:39 <qschulz> https://elixir.bootlin.com/linux/v6.14.7/source/arch/arm64/boot/dts/rockchip/px30.dtsi#L23 right hand part

08:40 <diederik> so a reference to a phandle?

08:42 <diederik> ... but only when used in /aliases?

08:42 <qschulz> it's not a phandle, not in <>

08:58 <qschulz> if you use it in an overlay, you get something local to the overlay

08:58 <qschulz> e.g. I had /aliases/ethernet2 = &lan2

08:58 <qschulz> and it resolved to something like

08:59 <qschulz> /fragment@2/__overlay__/switch@5f/ethernet-ports/port@0

08:59 <qschulz> which obviously isn't useful :)

09:03 <qschulz> since this doesn't exist after application of the overlay

10:12 <mmind00> qschulz: though that actually sounds like some error in dtc

10:13 <mmind00> qschulz: i.e. dtc resolves all that for regular phandles, so that you can use the regular &sdmmc in the overlay and all the other fragment-voodoo just happens behind the curtain by magic

10:14 <mmind00> or not dtc, but the logic doing the apply

10:21 <qschulz> the thing is

10:21 <qschulz> how do you know if it's a proper string or if it's a string that you should modify?

10:22 <qschulz> so I think there needs to be an additional mechanism in dtc for lhandles (or whatever the name of that &thing is) that would make it work the same way it does for phandles

10:22 <qschulz> with symbols and all