From: Tom Rini <trini@konsulko.com> To: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Cc: linux-kernel@vger.kernel.org, John Keeping <john@metanate.com>, 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: Fri, 25 Aug 2017 10:24:26 -0400 [thread overview] Message-ID: <20170825142426.GN2827@bill-the-cat> (raw) In-Reply-To: <1503669407.25945.102.camel@linux.intel.com> [-- Attachment #1: Type: text/plain, Size: 1507 bytes --] On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote: > +John > > 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. > > Tom, one more question. > > Apparently you are the one who tested the commit > 89128534f925 ("ASoC: rt5677: Add ACPI support") > year ago. Yes. > The commit states that ACPI properties that are used in Chromebook Pixel > 2015 is non-standard (not the same as for DT). > > However, DSDT shows the opposite! Interesting. I'm not an ACPI person, I just tested what John came up with. > I would like to ask yuo and John what is the status of that currently? > Do we have any publicly available laptop with non-standard properties? Is there any sort of "build date" or similar in the dump I provided yesterday? Every once in a while my laptop accidentally books into ChromeOS and then it might grab and apply some updates and it's not impossible that Google updated things in the interim. I'm quite happy to test patches or provide further dumps / etc from my system. You might want to start by talking with the person behind https://github.com/raphael/linux-samus to see if they know more about different versions of the hardware or at least point you towards more testers. Thanks! -- Tom [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tom Rini <trini@konsulko.com> To: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Cc: Oder Chiou <oder_chiou@realtek.com>, alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>, Takashi Iwai <tiwai@suse.com>, linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>, John Keeping <john@metanate.com>, Bard Liao <bardliao@realtek.com>, Linus Torvalds <torvalds@linux-foundation.org> Subject: Re: [PATCH] ASoC: rt5677: Reintroduce I2C device IDs Date: Fri, 25 Aug 2017 10:24:26 -0400 [thread overview] Message-ID: <20170825142426.GN2827@bill-the-cat> (raw) In-Reply-To: <1503669407.25945.102.camel@linux.intel.com> [-- Attachment #1.1: Type: text/plain, Size: 1507 bytes --] On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote: > +John > > 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. > > Tom, one more question. > > Apparently you are the one who tested the commit > 89128534f925 ("ASoC: rt5677: Add ACPI support") > year ago. Yes. > The commit states that ACPI properties that are used in Chromebook Pixel > 2015 is non-standard (not the same as for DT). > > However, DSDT shows the opposite! Interesting. I'm not an ACPI person, I just tested what John came up with. > I would like to ask yuo and John what is the status of that currently? > Do we have any publicly available laptop with non-standard properties? Is there any sort of "build date" or similar in the dump I provided yesterday? Every once in a while my laptop accidentally books into ChromeOS and then it might grab and apply some updates and it's not impossible that Google updated things in the interim. I'm quite happy to test patches or provide further dumps / etc from my system. You might want to start by talking with the person behind https://github.com/raphael/linux-samus to see if they know more about different versions of the hardware or at least point you towards more testers. Thanks! -- Tom [-- Attachment #1.2: Digital signature --] [-- Type: application/pgp-signature, Size: 819 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2017-08-25 14:25 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 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 [this message] 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=20170825142426.GN2827@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=john@metanate.com \ --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: linkBe 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.