From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takashi Iwai <tiwai@suse.de>
Subject: Re: Right internal speaker and internal microphone
	doesn't seem to work
Date: Sun, 28 Apr 2019 09:34:27 +0200
Message-ID: <s5h7ebemvlo.wl-tiwai@suse.de>
References: <CACxsoGr1we7usowgT6zReJWSu9=AfhMYQgRjHJD-ja1zCSz3rQ@mail.gmail.com>
 <20190425164657.GA22452@xn--80adja5bqm.su>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mx1.suse.de (mx2.suse.de [195.135.220.15])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by alsa1.perex.cz (Postfix) with ESMTPS id B94E6F896EC
 for <alsa-devel@alsa-project.org>; Sun, 28 Apr 2019 09:34:28 +0200 (CEST)
In-Reply-To: <20190425164657.GA22452@xn--80adja5bqm.su>
List-Unsubscribe: <https://mailman.alsa-project.org/mailman/options/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel/>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <https://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Errors-To: alsa-devel-bounces@alsa-project.org
Sender: "Alsa-devel" <alsa-devel-bounces@alsa-project.org>
To: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
Cc: alsa-devel@alsa-project.org, Drago Praznik <dragopraznik@gmail.com>
List-Id: alsa-devel@alsa-project.org

On Thu, 25 Apr 2019 18:46:57 +0200,
Sergey 'Jin' Bostandzhyan wrote:
> 
> Hi Drago,
> 
> On Thu, Apr 25, 2019 at 05:07:55PM +0200, Drago Praznik wrote:
> > Originally I submitted a post on forum:
> > https://forums.linuxmint.com/viewtopic.php?f=49&t=292732
> > 
> > ... since it didn't help, I ended up here.
> 
> I almost fear we're on the wrong list here, I have a similar problem on
> a different notebook, but did not get any answer. I think this list is
> much more technical/low-level and not end user oriented.
> 
> That being said - it was suggested on the Alsa Project page, thats how I
> got here, so not really sure what the right place for such requests would be.
> 
> Perhaps we should try via the kernel bugtracker, but I'd appreciate if
> someone could hint users like us to a place where problems like these
> could be addressed.

Well, the ML itself is right, but there is not many things the
developers can help remotely.  This is a very vendor-specific stuff,
no generic problem, hence it's only the hardware vendor who knows how
to fix the problem (most likely some missing extra initialization).
Alternatively, you can do trial-and-error by yourself, e.g. applying
the existing quirks via model option or fiddling with the pin
configurations via hdajackretask.


thanks,

Takashi