summaryrefslogtreecommitdiffstats
path: root/security/yama
diff options
context:
space:
mode:
authorKuninori Morimoto <kuninori.morimoto.gx@renesas.com>2017-10-02 09:37:32 +0200
committerMark Brown <broonie@kernel.org>2017-10-03 18:51:40 +0200
commit9e9e95df06433b4f89cfeef0003af091ee0ebc86 (patch)
tree3ccfd176bd400cbbc5efe0660e794b2e0eaee4af /security/yama
parentASoC: rsnd: fix ADG flags (diff)
downloadlinux-9e9e95df06433b4f89cfeef0003af091ee0ebc86.tar.xz
linux-9e9e95df06433b4f89cfeef0003af091ee0ebc86.zip
ASoC: rcar: skip disabled-SSI nodes
The current device tree representation of the R-Car SSI assumes that they are numbered consecutively, starting from 0. Alas, this is not the case with the R8A77995 (D3) SoC which SSI1/SSI2 aren't present. In order to keep the existing device trees working, I'm suggesting to use a disabled node for SSI0/SSI1. Teach the SSI probe to just skip disabled nodes. Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Tested-by: Hiroyuki Yokoyama <hiroyuki.yokoyama.vx@renesas.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'security/yama')
0 files changed, 0 insertions, 0 deletions