All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org, Kailang Yang <kailang@realtek.com>,
	Ryan Prescott <ryan@cousinscomputers.net>
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for Lenovo Ideapad S740
Date: Fri, 16 Apr 2021 10:52:24 +0200	[thread overview]
Message-ID: <s5hwnt2r4qf.wl-tiwai@suse.de> (raw)
In-Reply-To: <be178038-8e42-34db-3804-f27240b2d488@perex.cz>

On Fri, 16 Apr 2021 10:47:32 +0200,
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).

Indeed.  Already a few drivers need the initialization of the chip
behind HD-audio, and it'd be good if we have some standard interface
for that.


thanks,

Takashi

  reply	other threads:[~2021-04-16  8:53 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 [this message]
2021-04-16 16:05   ` Pierre-Louis Bossart
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=s5hwnt2r4qf.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kailang@realtek.com \
    --cc=perex@perex.cz \
    --cc=ryan@cousinscomputers.net \
    /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.