linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: PM regression in next
Date: Fri, 12 Jan 2018 21:38:45 +0000	[thread overview]
Message-ID: <20180112213845.GJ21458@sirena.org.uk> (raw)
In-Reply-To: <20180112210706.GE4821@atomide.com>

On Fri, Jan 12, 2018 at 01:07:06PM -0800, Tony Lindgren wrote:

> Tturns out just adding back .read = twl4030_read fixes it..
> I added a dummy function for read and am now seeing a bunch
> of reads that now don't happen:

What's supposed to happen here is that you end up with a
component->regmap set and snd_soc_component_read() uses that to do the
read.  That normally gets retrieved via dev_get_regmap() but it looks
like this is broken here by the rather novel chip design confusing the
assumptions that code makes.  I *think* that setting the regmap to
twl_get_regmap(TWL4030_MODULE_AUDIO_VOICE) using
snd_soc_codec_init_regmap() in twl4030_soc_probe ought to do the trick
(assuming my guesses about what's going on are right) but can't test.

I'd check twl6040 too, I bet it's got the same issue.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180112/b340cdc0/attachment.sig>

      parent reply	other threads:[~2018-01-12 21:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12  0:01 PM regression in next Tony Lindgren
2018-01-12  0:18 ` Andrew Morton
2018-01-12  0:23   ` Tony Lindgren
2018-01-12  0:45     ` Andrew Morton
2018-01-12  1:20       ` Tony Lindgren
2018-01-12  1:32         ` Tony Lindgren
2018-01-12 12:23           ` Rafael J. Wysocki
2018-01-12 12:30             ` Rafael J. Wysocki
2018-01-12 13:01               ` Lars-Peter Clausen
2018-01-12 13:16                 ` Andrew Lunn
2018-01-12 13:52                   ` Tony Lindgren
2018-01-12 13:55                     ` Andrew Lunn
2018-01-12 14:14                       ` Tony Lindgren
2018-01-12 19:00         ` Tony Lindgren
2018-01-12 19:12           ` Mark Brown
2018-01-12 21:07             ` Tony Lindgren
2018-01-12 21:15               ` Mark Brown
2018-01-12 21:50                 ` Tony Lindgren
2018-01-12 22:11                   ` Mark Brown
2018-01-12 22:49                     ` Tony Lindgren
2018-01-12 22:59                       ` Mark Brown
2018-01-15  1:45                         ` Kuninori Morimoto
2018-01-15 16:50                           ` Tony Lindgren
2018-01-15 17:19                             ` Mark Brown
2018-01-15 17:52                               ` Tony Lindgren
2018-01-15 17:56                                 ` Mark Brown
2018-01-15 18:06                                   ` Tony Lindgren
2018-01-15 18:13                                     ` Mark Brown
2018-01-15 18:55                                       ` Tony Lindgren
2018-01-16  0:38                                         ` Kuninori Morimoto
2018-01-17  9:47                                         ` Peter Ujfalusi
2018-01-15 23:22                             ` Kuninori Morimoto
2018-01-16  0:36                               ` Tony Lindgren
2018-01-12 21:38               ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180112213845.GJ21458@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).