All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Bard Liao <bardliao@realtek.com>,
	Oder Chiou <oder_chiou@realtek.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs
Date: Thu, 24 Aug 2017 09:47:37 -0400	[thread overview]
Message-ID: <20170824134737.GB17193@bill-the-cat> (raw)
In-Reply-To: <1503577560.25945.84.camel@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2757 bytes --]

On Thu, Aug 24, 2017 at 03:26:00PM +0300, Andy Shevchenko wrote:
> On Thu, 2017-08-24 at 07:15 -0400, Tom Rini wrote:
> > On Thu, Aug 24, 2017 at 10:39:09AM +0300, Andy Shevchenko wrote:
> > > On Wed, 2017-08-23 at 20:05 -0400, Tom Rini wrote:
> > > > On Wed, Aug 23, 2017 at 01:39:12PM -0400, Tom Rini wrote:
> > > > > On Wed, Aug 23, 2017 at 05:29:33PM +0300, Andy Shevchenko wrote:
> > > > > 
> > > > > > Are you sure the commit ddc9e69b9dc2 ("ASoC: rt5677: Hide
> > > > > > platform
> > > > > > data
> > > > > > in the module sources") does not fix your issue?
> > > > > 
> > > > > As that's not in master yet I can't tell.  Can you give me a
> > > > > pointer
> > > > > to
> > > > > somewhere?
> > > 
> > > It's in ASoC next at least.
> > > 
> > > > >   Thanks!
> > > > 
> > > > OK, my bad, it has a different hash upstream, but no, that change
> > > > doesn't fix things as I see the problem on top of Linus'
> > > > tree.  Thanks!
> > > 
> > > Interesting...
> > > 
> > > The only bug so far I saw is the following one
> > > 
> > > https://bugzilla.kernel.org/show_bug.cgi?id=196397
> > > 
> > > ...and above commit fixes it.
> > > 
> > > Can you place somewhere the bundle of the following:
> > > 
> > > 1. Output file (tables.dat) of
> > > 	% acpidump -o tables.dat
> > 
> > https://gist.github.com/trini/b9a9a547e37cb812506a22e18cd2aff5
> > 
> > > 2. Output of
> > > 	% cat /proc/interrupts
> > 
> > https://gist.github.com/trini/39a5d88a5ecb9b71336ff5fe9da7c720
> > 
> > > 3. Output of
> > > 	% lspci -vv -xx
> > 
> > https://gist.github.com/trini/e81ab21909eeaa05ea50dc0596d23c14
> > 
> > > 4. Output of
> > > 	% grep -H 15 /sys/bus/acpi/devices/*/status
> > 
> > https://gist.github.com/trini/698dc284634ad9e1cfbafad8e705de5f
> 
> Thanks!
> 
> I have checked those files and found that device is in the table and
> pretty much properly defined ACPI I2C slave.
> 
> The change in the driver you referred to makes the change to modalias.
> 
> Thus, I'm suspecting that your user space helper either has some hard
> coded values for previous case, or just broken.
> 
> Can you also check is the codec module loaded (lsmod) and, if it's not,
> load it manually and check if sound works again.
> 
> P.S. In any case you need the patch mentioned in bug #196397

I've applied "ASoC: rt5677: Hide platform data in the module sources"
manually to Linus' tree and still see the same problem.  Perhaps there's
now some missing alias information that really needs to still be
provided?  snd-soc-sst-bdw-rt5677-mach is not loaded and I can't
manually load it later on.  What user space helper configuration am I
supposed to need to have now, for this to work?  Thanks!

-- 
Tom

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2017-08-24 13:47 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23  1:51 [PATCH] ASoC: rt5677: Reintroduce I2C device IDs Tom Rini
2017-08-23  1:51 ` Tom Rini
2017-08-23  9:28 ` Mark Brown
2017-08-23 22:35   ` Tom Rini
2017-08-23 22:47     ` Mark Brown
2017-08-23 22:54       ` Tom Rini
2017-08-23 22:54         ` Tom Rini
2017-08-23 23:15         ` Mark Brown
2017-08-23 23:02       ` Mark Brown
2017-08-23 14:29 ` Andy Shevchenko
2017-08-23 17:39   ` Tom Rini
2017-08-24  0:05     ` Tom Rini
2017-08-24  7:39       ` Andy Shevchenko
2017-08-24  7:39         ` Andy Shevchenko
2017-08-24 11:15         ` Tom Rini
2017-08-24 11:15           ` Tom Rini
2017-08-24 12:26           ` Andy Shevchenko
2017-08-24 13:41             ` Mark Brown
2017-08-24 13:47             ` Tom Rini [this message]
2017-08-24 14:28       ` [alsa-devel] " Takashi Iwai
2017-08-24 14:31         ` Takashi Iwai
2017-08-24 14:31           ` Takashi Iwai
2017-08-24 14:41           ` Tom Rini
2017-08-24 14:41             ` Tom Rini
2017-08-24 15:42             ` [alsa-devel] " Takashi Iwai
2017-08-24 15:52               ` Mark Brown
2017-08-24 15:52                 ` Mark Brown
2017-08-24 15:54                 ` [alsa-devel] " Takashi Iwai
2017-08-24 15:54                 ` Tom Rini
2017-08-24 16:06                   ` Takashi Iwai
2017-08-24 16:06                     ` Takashi Iwai
2017-08-24 16:08                     ` [alsa-devel] " Tom Rini
2017-08-24 17:16                     ` Andy Shevchenko
2017-08-24 17:44                       ` Takashi Iwai
2017-08-24 17:44                         ` Takashi Iwai
2017-08-25 13:48                         ` [alsa-devel] " Mark Brown
2017-08-25 13:48                           ` Mark Brown
2017-08-25 13:09                     ` [alsa-devel] " Mark Brown
2017-08-25 13:09                       ` Mark Brown
2017-08-25 13:17                       ` [alsa-devel] " Takashi Iwai
2017-08-25 13:17                         ` Takashi Iwai
2017-08-25 13:56 ` Andy Shevchenko
2017-08-25 14:24   ` Tom Rini
2017-08-25 14:24     ` Tom Rini
2017-08-25 14:49     ` Andy Shevchenko
2017-08-25 16:05     ` John Keeping
2017-08-25 16:05       ` John Keeping
2017-08-25 16:42       ` Andy Shevchenko
2017-08-25 16:42         ` Andy Shevchenko
2017-08-25 17:09         ` John Keeping
2017-08-25 19:33         ` Tom Rini

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=20170824134737.GB17193@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bardliao@realtek.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oder_chiou@realtek.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.