Hi Geert, On Mon, Jun 22, 2015 at 6:38 PM, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > Hi Magnus, > > On Sun, Jun 21, 2015 at 10:09 AM, Magnus Damm <magnus.damm@xxxxxxxxx> wrote: >> From: Magnus Damm <damm+renesas@xxxxxxxxxxxxx> >> >> Remove the sh7372 CMT compat string to reduce maintenance burden. >> >> It should be fine to break DT compatibility because: >> 1) The sh7372 SoC support has been removed from upstream >> 2) The sh7372 CMT DT binding was never part of upstream DTS >> 3) The CMT driver never matches on the sh7372 binding >> >> Signed-off-by: Magnus Damm <damm+renesas@xxxxxxxxxxxxx> >> --- >> >> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 2 -- >> 1 file changed, 2 deletions(-) >> >> --- 0001/Documentation/devicetree/bindings/timer/renesas,cmt.txt >> +++ work/Documentation/devicetree/bindings/timer/renesas,cmt.txt 2015-06-20 13:47:59.922366518 +0900 >> @@ -32,8 +32,6 @@ Required Properties: >> (CMT[234] on sh7372, sh73a0 and r8a7740) >> This is a fallback for the above renesas,cmt-32-fast-* entries. >> >> - - "renesas,cmt-48-sh7372" for the sh7372 48-bit CMT >> - (CMT1) > > You forgot to remove the reference to sh7372 in the "renesas,cmt-48" > fallback section, and the "renesas,cmt-32-sh7372" and > "renesas,cmt-32-fast-sh7372" bindings. Thanks, yeah, I noticed that after sending out the series. I couldn't find any DT users of the "fast" group though, so perhaps I need to extend my pruning a bit. First it would be good to see if we could reach an agreement about how to handle DT compat strings for these kind of devices though. (devices where instances within one particular SoC are quite different). Cheers, / magnus -- To unsubscribe from this list: send the line "unsubscribe devicetree" in
