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: Wed, 23 Aug 2017 20:05:25 -0400 [thread overview]
Message-ID: <20170824000525.GY17193@bill-the-cat> (raw)
In-Reply-To: <20170823173912.GN17193@bill-the-cat>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
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:
>
> > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote:
> > > Not all devices with ACPI and this combination of sound devices will
> > > have the required information provided via ACPI. Reintroduce the I2C
> > > device ID to restore sound functionality on on the Chromebook 'Samus'
> > > model.
> >
> > > This is a regression from v4.12 on my laptop (a Chromebook 'Samus'
> > > that's not running ChromeOS). My fault for getting out of the habit
> > > of
> > > trying -rc1 when it comes out and not spotting this sooner. I'm not
> > > 100% sure if this fix is correct for all cases as I'm only able to
> > > test
> > > my hardware here, and this does fix my laptop.
> >
> > 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? 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!
--
Tom
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-08-24 0:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
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 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 [this message]
2017-08-24 7:39 ` Andy Shevchenko
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
2017-08-24 14:28 ` [alsa-devel] " Takashi Iwai
2017-08-24 14:31 ` Takashi Iwai
2017-08-24 14:41 ` Tom Rini
2017-08-24 15:42 ` Takashi Iwai
2017-08-24 15:52 ` Mark Brown
2017-08-24 15:54 ` Takashi Iwai
2017-08-24 15:54 ` Tom Rini
2017-08-24 16:06 ` Takashi Iwai
2017-08-24 16:08 ` Tom Rini
2017-08-24 17:16 ` Andy Shevchenko
2017-08-24 17:44 ` Takashi Iwai
2017-08-25 13:48 ` Mark Brown
2017-08-25 13:09 ` Mark Brown
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:49 ` Andy Shevchenko
2017-08-25 16:05 ` John Keeping
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=20170824000525.GY17193@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®