All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Takashi Iwai <tiwai@suse.de>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
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 19:21:46 +0200	[thread overview]
Message-ID: <b04b5f9b-1b19-e216-793a-dde9c3d66371@perex.cz> (raw)
In-Reply-To: <s5h5z0mgpsu.wl-tiwai@suse.de>

Dne 16. 04. 21 v 18:25 Takashi Iwai napsal(a):
> On Fri, 16 Apr 2021 18:05:17 +0200,
> Pierre-Louis Bossart wrote:
>>
>>
>>
>> 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?
> 
> Sure, that's another problem.  But currently it's not clear even how
> to communicate via I2C/whatever to the underlying chip, as it's done
> via the vendor-specific COEF verb.  At least this could be opened, I
> hope.

The nice thing if we know the I2C master communication is that we can create
I2C bus in the HDA driver and do run i2cdetect to detect the connected chips.
Yes, it's partial information, but it's far more better than this unreadable
coef implementation.

						Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

  reply	other threads:[~2021-04-16 17:23 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
2021-04-16 16:25     ` Takashi Iwai
2021-04-16 17:21       ` Jaroslav Kysela [this message]
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=b04b5f9b-1b19-e216-793a-dde9c3d66371@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=kailang@realtek.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --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.