[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdXy0Y2NtPzL9RuhPnu2qPd1-Ft75xfNOmj1EN0Rbq3Jsg@mail.gmail.com>
Date: Wed, 24 Feb 2016 08:36:38 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Simon Horman <horms+renesas@...ge.net.au>
Cc: Wolfgang Grandegger <wg@...ndegger.com>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Magnus Damm <magnus.damm@...il.com>, linux-can@...r.kernel.org,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
linux-renesas-soc@...r.kernel.org
Subject: Re: [PATCH can-next v2 1/2] CAN: rcar: add gen[12] fallback
compatibility strings
On Wed, Feb 24, 2016 at 2:56 AM, Simon Horman
<horms+renesas@...ge.net.au> wrote:
> Add fallback compatibility string for R-Car Gen 1 and Gen2.
>
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, e.g. Gen 1 and Gen 2. But beyond that its not clear what the
> relationship between IP blocks might be. For example, I believe that
> r8a7779 is older than r8a7778 but that doesn't imply that the latter is a
> descendant of the former or vice versa.
>
> We can, however, by examining the documentation and behaviour of the
> hardware at run-time observe that the current driver implementation appears
> to be compatible with the IP blocks on SoCs within a given generation.
>
> For the above reasons and convenience when enabling new SoCs a
> per-generation fallback compatibility string scheme being adopted for
> drivers for Renesas SoCs.
>
> Signed-off-by: Simon Horman <horms+renesas@...ge.net.au>
> Acked-by: Rob Herring <robh@...nel.org>
Acked-by: Geert Uytterhoeven <geert+renesas@...der.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists