From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH] dt-bindings: timer: renesas: tmu: document R8A779{7|8}0 bindings References: <72db4d8d-7b3d-7368-02a4-f652a7bc810d@cogentembedded.com> From: Sergei Shtylyov Message-ID: Date: Tue, 11 Sep 2018 21:26:27 +0300 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-MW Content-Transfer-Encoding: 7bit To: Geert Uytterhoeven Cc: Rob Herring , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Thomas Gleixner , Daniel Lezcano , Mark Rutland , Linux-Renesas List-ID: On 09/10/2018 05:24 PM, Geert Uytterhoeven wrote: >> Document the R-Car V3{M|H} (R8A779{7|8}0) SoC in the Renesas TMU bindings; >> the TMU hardware in those is the Renesas standard 3-channel timer unit. >> >> Signed-off-by: Sergei Shtylyov > > Thanks for your patch! > > Not all channels seem to be identical, but the driver just matches against > the "renesas,tmu" fallback? The only difference between TMUs is the input capture capability on the 3rd channel in each TMU -- that includes TCPR register and extra interrupt output TICPI (perhaps has to do with 4th TMU IRQ?). The driver is blissfully unaware of this extra capability. :-) > In addition, the V3H TMU seems to differ from the TMU in other R-Car Gen3 > variants? Yes, but they only differ in the number of channels capable of input capture. > How is this handled? Nohow. And I'm not sure we should care about this difference... > Gr{oetje,eeting}s, > > Geert MBR, Sergei