From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Kailang Yang <kailang@realtek.com>
Cc: Ryan Prescott <ryan@cousinscomputers.net>
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for Lenovo Ideapad S740
Date: Fri, 16 Apr 2021 11:05:17 -0500 [thread overview]
Message-ID: <a5fee517-c12e-1cb0-755f-453d6bb47795@linux.intel.com> (raw)
In-Reply-To: <be178038-8e42-34db-3804-f27240b2d488@perex.cz>
On 4/16/21 3:47 AM, Jaroslav Kysela wrote:
> Dne 16. 04. 21 v 10:12 Takashi Iwai napsal(a):
>> Lenovo Ideapad S740 requires quite a few COEF setups to make its
>> speakers working. The verb table was provided from Ryan Prescott as
>> the result of investigation via qemu:
>> https://github.com/ryanprescott/realtek-verb-tools/wiki/How-to-sniff-verbs-from-a-Windows-sound-driver
>
> [Cc: to Kailang / Realtek]
>
> I believe that this sequence contains I2C writes to amplifier chips. It would
> be really helpful, if Realtek can provide more information for the I2C master
> interface for their codecs (describe basic I2C I/O).
The biggest problem is to figure what address/value pairs to write with
I2C into the amplifiers, and here the catch is that those I2C/I2S
amplifiers may or may not be sourced from Realtek, and it'd be difficult
for Realtek to provide documentation on their competition, wouldn't it?
next prev parent reply other threads:[~2021-04-16 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 8:12 [PATCH] ALSA: hda/realtek: Add quirk for Lenovo Ideapad S740 Takashi Iwai
2021-04-16 8:47 ` Jaroslav Kysela
2021-04-16 8:52 ` Takashi Iwai
2021-04-16 16:05 ` Pierre-Louis Bossart [this message]
2021-04-16 16:25 ` Takashi Iwai
2021-04-16 17:21 ` Jaroslav Kysela
2021-04-16 18:30 ` Pierre-Louis Bossart
2021-04-16 16:35 ` [External] " Mark Pearson
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=a5fee517-c12e-1cb0-755f-453d6bb47795@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=kailang@realtek.com \
--cc=perex@perex.cz \
--cc=ryan@cousinscomputers.net \
--cc=tiwai@suse.de \
/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.