#include #include "screen.h" WINDOW *screen_init(bool israw) { WINDOW *screen = initscr(); if (israw) raw(); noecho(); cbreak(); nodelay(screen, TRUE); keypad(stdscr, TRUE); refresh(); wrefresh(screen); return screen; } void screen_end(void) { endwin(); } href='https://git.distanz.ch/cgit.cgi/linux/net-next.git/atom/?h=nds-private-remove' type='application/atom+xml'/>
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2016-12-12 10:49:35 +0100
committerMark Brown <broonie@kernel.org>2016-12-14 17:38:18 +0000
commit4286db8456f4fa0c6af2b6b9abc5991a7e7da69c (patch)
treecd75a7ae69486439143d1811515c5d1cdebf02c5
parentfafd67940774733fa97f4b09412aea6981b82e0a (diff)
spi: sh-msiof: Add R-Car Gen 2 and 3 fallback bindings
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 <horms+renesas@verge.net.au> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat