Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
Cc: alsa-devel@alsa-project.org
Subject: Re: Surround speaker connection on Acer 8951G
Date: Thu, 22 Aug 2019 16:17:51 +0200	[thread overview]
Message-ID: <s5hef1dthbk.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190819195714.GA2737@xn--80adja5bqm.su>

On Mon, 19 Aug 2019 21:57:14 +0200,
Sergey 'Jin' Bostandzhyan wrote:
> 
> Hi Takashi,
> 
> On Sat, Jul 20, 2019 at 06:54:35PM +0200, Sergey 'Jin' Bostandzhyan wrote:
> > On Fri, Jul 19, 2019 at 04:44:52PM +0200, Takashi Iwai wrote:
> > > It might be some other external stuff like an external amp that is
> > > missing.  Often it's managed via GPIO or EAPD (that is controlled by
> > > HD-audio itself), but sometimes via a vendor-specific verb, or even
> > > over a completely different i2c...
> > > 
> > > In the case of vendor verbs, you can take a look at other quirks for
> > > similar models that touches lots of COEF stuff.
> > 
> > thanks for the pointers, does not sound simple, let's see if I get anywhere,
> > I will for sure try.
> 
> I am going at a slow pace, but I did not give up and I'd be happy if you or
> anyone else from the list would find the time to answer some questions from 
> time to time.
> 
> Right now I am mostly studying patch_realtek.c, as a first step I want to
> make sure that at least my known pins get set up by the driver without
> having to go via hdajackretask.
> 
> I got my build set up, I also dug up hda-decode-pincfg from the hda-emu
> sources and made it compile (very useful if one wants to understand and
> compare the pin configurations in patch_realtek.c), so now I am trying
> things out every other evening.
> 
> One part that is not quite clear to me: what the heck is ALC669X?

It's just a name string :)  Realtek seems to give a different chip
name for the certain variant for Dell or whatever big vendors.
AFAIK, basically it's the very same chip as ALC670, which is almost
compatible with ALC662 variant.

> Could someone please explain the meaning of alc_codec_rename_pci_table ?
> 
> Entry for my vendor id looks like this:
>     { 0x10ec0670, 0x1025, 0, "ALC669X" },
> 
> If I search for that vendor id further in the code, I see that it gets
> patched as ALC662?
> 
>     HDA_CODEC_ENTRY(0x10ec0670, "ALC670", patch_alc662),
> 
> At the same time the documentation in models.rst lists those numbers
> together:
> 
> ALC66x/67x/892
> 
> I already looked at the hda-audio specification from Intel to get a general
> understanding, but I was also pulling some Realtek specs which do describe
> implemented verbs and things like that (my hope was to see something
> vendor related which could hint me how to enable the subwoofer).
> 
> I was not able to find any 669 Realtek datasheets, I did however find
> the ones for ALC665 and ALC892. How specific is all of this, i.e. should I
> keep looking for the exact one or am I on the wrong path here?

The datasheet of ALC662 and similar chips should be available.
In general, there is no big difference among Realtek chips; one has
more I/O pins available, while one has less.

The vendor-specific stuff like COEF isn't found in the datasheet in
details, unfortunately.  Also, the GPIO pin connection isn't covered
by the codec datasheet, as it's rather device-specific, of course.


HTH,

Takashi

  reply	other threads:[~2019-08-22 14:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 19:24 Surround speaker connection on Acer 8951G Sergey 'Jin' Bostandzhyan
2019-07-19 11:12 ` Sergey 'Jin' Bostandzhyan
2019-07-19 14:44   ` Takashi Iwai
2019-07-20 16:54     ` Sergey 'Jin' Bostandzhyan
2019-08-19 19:57       ` Sergey 'Jin' Bostandzhyan
2019-08-22 14:17         ` Takashi Iwai [this message]
2019-08-22 20:30           ` Sergey 'Jin' Bostandzhyan
2019-08-29  9:30             ` Takashi Iwai
2019-08-29 10:38               ` Sergey 'Jin' Bostandzhyan
2019-08-29 11:29                 ` Takashi Iwai
2019-08-30 11:45                   ` Sergey 'Jin' Bostandzhyan
2019-08-30 11:45                     ` [alsa-devel] " Sergey 'Jin' Bostandzhyan
2019-08-30 12:22                     ` Takashi Iwai
2019-08-30 12:22                       ` [alsa-devel] " Takashi Iwai
2019-09-01 19:27                       ` Sergey 'Jin' Bostandzhyan
2019-09-01 19:27                         ` [alsa-devel] " Sergey 'Jin' Bostandzhyan
2019-09-02  6:41                         ` Takashi Iwai
2019-09-02  6:41                           ` [alsa-devel] " Takashi Iwai
2019-09-02 21:39                           ` Sergey 'Jin' Bostandzhyan
2019-09-05 15:07                             ` Takashi Iwai
2019-09-06  9:33                               ` [alsa-devel] [PATCH] Add Acer Aspire Ethos 8951G model quirk Sergey Bostandzhyan
2019-09-06 12:13                                 ` Takashi Iwai
2019-11-25 17:39                     ` [alsa-devel] Surround speaker connection on Acer 8951G Sergey 'Jin' Bostandzhyan
2019-11-27 11:28                       ` Takashi Iwai
2019-11-27 16:17                         ` Sergey 'Jin' Bostandzhyan
2019-11-27 16:41                           ` Takashi Iwai
2019-11-28 15:46                             ` Sergey 'Jin' Bostandzhyan

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=s5hef1dthbk.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jin@mediatomb.cc \
    /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