linux-kernel - Re: [PATCH linux-next v3 1/1] ASoC: rsnd: ssi: Request dedicated dma channels for busif0 to 7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <871s8wcatk.wl-kuninori.morimoto.gx@renesas.com>
Date:   Thu, 11 Oct 2018 23:47:39 +0000
From:   Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To:     <jiada_wang@...tor.com>
Cc:     <lgirdwood@...il.com>, <broonie@...nel.org>, <perex@...ex.cz>,
        <tiwai@...e.com>, <alsa-devel@...a-project.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH linux-next v3 1/1] ASoC: rsnd: ssi: Request dedicated dma channels for busif0 to 7


Hi

> Currently ssi driver only requests dma channel for SSI_0, with
> naming of 'rxu/txu', which is used to transfer data to/from busif0.
> But for GEN2/GEN3, there are also busif1 ~ busif7, which need to
> be used when SSI works in TDM Split/Ex-Split mode.
> 
> This patch adds support to firstly try to request busif indexed
> dma channel with naming "rxu[busif]/txu[busif]", if these dma channel
> don't exist, then try to request 'rxu/txu' dma channel to keep
> compatibility with platform hasn't had device-tree updated.
> 
> Signed-off-by: Jiada Wang <jiada_wang@...tor.com>
> ---

In my understanding, we agreed that we will have new "ssiu" on DT.
This means "ssi" side expansion is no longer needed.

Of course we need to consider about compatibility then.

Best regards
---
Kuninori Morimoto