From mboxrd@z Thu Jan 1 00:00:00 1970 From: ben.hutchings@codethink.co.uk (Ben Hutchings) Date: Tue, 10 Apr 2018 18:33:40 +0100 Subject: [cip-dev] [PATCH 1/4] spi: sh-msiof: Add R-Car Gen 2 and 3 fallback bindings In-Reply-To: <1520530089-4988-2-git-send-email-fabrizio.castro@bp.renesas.com> References: <1520530089-4988-1-git-send-email-fabrizio.castro@bp.renesas.com> <1520530089-4988-2-git-send-email-fabrizio.castro@bp.renesas.com> Message-ID: <1523381620.2654.194.camel@codethink.co.uk> To: cip-dev@lists.cip-project.org List-Id: cip-dev.lists.cip-project.org On Thu, 2018-03-08 at 17:28 +0000, Fabrizio Castro wrote: > From: Simon Horman > > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, e.g. Gen 2 and Gen 3. But beyond that it's not clear what the > relationship between IP blocks might be. For example, I believe that > r8a7790 is older than r8a7791 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 is being adopted for > drivers for Renesas SoCs. > > Also: > * Deprecate renesas,sh-msiof. It seems poorly named as it is only > ? compatible with SH-Mobile. It also appears unused in mainline. > > Signed-off-by: Simon Horman > Reviewed-by: Geert Uytterhoeven > Signed-off-by: Mark Brown > (cherry picked from commit 4286db8456f4fa0c6af2b6b9abc5991a7e7da69c) > Signed-off-by: Fabrizio Castro > (cherry picked from commit 77f252646eb0ec1e78847fe5725c98ee9e70b39e) I deleted this second commit reference, which I assume refers to some private branch. Ben. > (removed "renesas,rcar-gen3-msiof") > Signed-off-by: Fabrizio Castro [...] -- Ben Hutchings Software Developer, Codethink Ltd.