[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5Bsy8DLNBKR77JFcihrrZp5mxN6BOJmte5uCXkwOfbzcg@mail.gmail.com>
Date: Mon, 1 Feb 2016 19:34:15 -0200
From: Fabio Estevam <festevam@...il.com>
To: "Maciej S. Szmigiero" <mail@...iej.szmigiero.name>
Cc: Mark Brown <broonie@...nel.org>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
Timur Tabi <timur@...i.org>,
Nicolin Chen <nicoleotsuka@...il.com>,
Xiubo Li <Xiubo.Lee@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: fsl_ssi: remove explicit register defaults
On Mon, Feb 1, 2016 at 7:30 PM, Maciej S. Szmigiero
<mail@...iej.szmigiero.name> wrote:
> So can regcache initialization be changed to use register by register read
> in case raw read fails?
>
> Since other option for drivers like SSI which are memory mapped and
> don't offer ability to reset their register values to default would be to
> explicitly write driver hardcoded defaults also by doing
> register by register write on probe time.
Yes, I had to do the same for sgtl5000:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/sound/soc/codecs/sgtl5000.c?id=af8ee11209e749c75eabf32b2a4ca631f396acf8
Would this approach work here too?
Powered by blists - more mailing lists