linux-kernel - Re: [PATCH 0/4] ASoC: fsl_asrc: allow selecting arbitrary clocks

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <041b4f2f-b6cf-1403-7a6b-5d77b818ce4d@collabora.com>
Date:   Thu, 16 Jul 2020 11:54:38 +0200
From:   Arnaud Ferraris <arnaud.ferraris@...labora.com>
To:     Nicolin Chen <nicoleotsuka@...il.com>
Cc:     alsa-devel@...a-project.org, Timur Tabi <timur@...nel.org>,
        Xiubo Li <Xiubo.Lee@...il.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Takashi Iwai <tiwai@...e.com>,
        Rob Herring <robh+dt@...nel.org>, linux-kernel@...r.kernel.org,
        Mark Brown <broonie@...nel.org>, kernel@...labora.com,
        Fabio Estevam <festevam@...il.com>
Subject: Re: [PATCH 0/4] ASoC: fsl_asrc: allow selecting arbitrary clocks



Le 15/07/2020 à 22:46, Nicolin Chen a écrit :
>> Calculations are indeed good, but then the clock selection setting in
>> the ASRCSR register would also use SSI1 as the input clock, which
>> doesn't work in our case.
> 
> Could you please elaborate why it doesn't work?
> 

Hmm, actually it was a userspace issue, kernel-wise it could work fine
with SSI1 as input clock, so please ignore this latest comment.

Regards,
Arnaud