> > What about simply dropping r9a06g033 which cannot run Linux (no RAM
> > controller, only 6MB internal RAM) and there hasn't been any upstreaming
>
> You can run Linux on 6 MiB of RAM, if you try hard ;-)
Whoever tries that hard will have zero problems upstreaming the bindings
then again. I will happily ack them. But it will not happen.
>
> > effort for other OS in the last 7 years? And making the remaining
>
> ... which does not mean there are no users.
And these mysterious users will complain about a removed UART binding
while there is not even a clk binding upstream?
> We don't allow "everything". Valid compatible values are checked by
> the normal rules below.
Why don't we use '{}' with all the bindings then? Would simplify so
much. From the watchdog driver:
- items:
- enum:
- renesas,r8a7742-wdt # RZ/G1H
- renesas,r8a7743-wdt # RZ/G1M
- renesas,r8a7744-wdt # RZ/G1N
- renesas,r8a7745-wdt # RZ/G1E
- renesas,r8a77470-wdt # RZ/G1C
- renesas,r8a7790-wdt # R-Car H2
- renesas,r8a7791-wdt # R-Car M2-W
- renesas,r8a7792-wdt # R-Car V2H
- renesas,r8a7793-wdt # R-Car M2-N
- renesas,r8a7794-wdt # R-Car E2
- const: renesas,rcar-gen2-wdt # R-Car Gen2 and RZ/G1
- items:
- enum:
- renesas,r8a774a1-wdt # RZ/G2M
- renesas,r8a774b1-wdt # RZ/G2N
- renesas,r8a774c0-wdt # RZ/G2E
- renesas,r8a774e1-wdt # RZ/G2H
- renesas,r8a7795-wdt # R-Car H3
- renesas,r8a7796-wdt # R-Car M3-W
- renesas,r8a77961-wdt # R-Car M3-W+
- renesas,r8a77965-wdt # R-Car M3-N
- renesas,r8a77970-wdt # R-Car V3M
- renesas,r8a77980-wdt # R-Car V3H
- renesas,r8a77990-wdt # R-Car E3
- renesas,r8a77995-wdt # R-Car D3
- const: renesas,rcar-gen3-wdt # R-Car Gen3 and RZ/G2
- items:
- enum:
- renesas,r8a779a0-wdt # R-Car V3U
- renesas,r8a779f0-wdt # R-Car S4-8
- renesas,r8a779g0-wdt # R-Car V4H
- renesas,r8a779h0-wdt # R-Car V4M
- const: renesas,rcar-gen4-wdt # R-Car Gen4
Attachment:
signature.asc
Description: PGP signature
