From: Ladislav Michl <ladis@linux-mips.org>
To: Petr Nosek <petr.nosek@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: hda/realtek: Enable internal speaker of ASUS UX362FA with ALC294
Date: Sun, 28 Apr 2019 09:33:16 +0200 [thread overview]
Message-ID: <20190428073316.GA25138@lenoch> (raw)
In-Reply-To: <CAAqJ6B9oWkpiXypV7UN-wqh9=YdAD-c-376GkcrHyXVsqqeBtw@mail.gmail.com>
Hi Petr,
please keep list Cced.
On Sun, Apr 28, 2019 at 12:48:06AM +0100, Petr Nosek wrote:
> Hi Ladislav,
>
> it repairs both. Inernal speaker and headphones.
Ok, will adjust commit message.
> I'm sending output of dmesg - I think it helps you to see information,
> when is computer booting. Your patch looks like good.
Assuming this part of your boot log comes from patched kernel, right?
snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
snd_hda_codec_realtek hdaudioC0D0: inputs:
snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19
snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
> Can I do something else to help with repair? I'm not sure, what you mean
> by the last sentence. If I have anything else to do.
I'll send v2 shortly,
Thank you,
ladis
prev parent reply other threads:[~2019-04-28 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 15:07 no sound in laptop ASUS UX362FA - repair Petr Nosek
2019-04-27 17:54 ` [PATCH] ALSA: hda/realtek: Enable internal speaker of ASUS UX362FA with ALC294 Ladislav Michl
[not found] ` <CAAqJ6B9oWkpiXypV7UN-wqh9=YdAD-c-376GkcrHyXVsqqeBtw@mail.gmail.com>
2019-04-28 7:33 ` Ladislav Michl [this message]
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=20190428073316.GA25138@lenoch \
--to=ladis@linux-mips.org \
--cc=alsa-devel@alsa-project.org \
--cc=petr.nosek@gmail.com \
/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