On 20.03.2023 21:02, Krzysztof Kozlowski wrote:
On 20/03/2023 18:57, Arınç ÜNAL wrote:
All of these are at the end the
way we can properly match compatible-data to write a proper driver.
The current ralink dtsi files which are in tree now
are totally incomplete and not documented so we are planning to align
Nothing like this was said in commit msg, so how can we know?
all of this with openWRT used files and others soon. That's the reason
we are not touching
'arch/mips/boot/dts' at all now. I don't think anybody is using any of
this but mt7621 which is properly completed and documented.
Anyway, none of this explains exception from naming convention - vendor,
device or family name.
Would mediatek,mtmips-clock.yaml make sense?
More, except:
1. This is not clock, but sysc.
Sergio, beware.
2. mips sounds redundant. Do you have rt2xxx and mt7xxx chips which are ARM?
All of the SoCs, RTXXXX, MT7620, MT7621, MT7628, MT7688 are MIPS. So I
decided to call this platform MTMIPS as I've seen MediaTek use this on
other projects like U-Boot. This is what I did on my pinctrl patch
series as well.
Arınç
