From: "Aurélien Croc" <aurelien@ap2c.com>
To: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] No sound with Realtek ALC298 on a Samsung Galaxy book
Date: Wed, 19 Feb 2020 10:05:36 +0100 [thread overview]
Message-ID: <3375274.Es2tsrqsTZ@antimony.ap2c.org> (raw)
In-Reply-To: <s5h1rqsc1kd.wl-tiwai@suse.de>
Hi,
> Aha, so the input works but only the output doesn't?
> Then it's not about the basic stuff like pin configuration but rather
> the missing COEF setup or such that is specific to Realtek codec
> (and/or the Samsung platform).
>
> Kailang, do you have any clue?
While waiting for Kailang's answer (and I hope he'll get the solution!!),
isn't it possible to grab information from Windows? I'm sorry I don't know
very well how Realtek chip works but if the problem would comes from some
registers which are not well initialized isn't it possible to dump the state
of the realtek chip and its registers under Windows and compare it with the
one under Linux?
Because I'm not sure that revers engineer the Windows driver would really
easily lead to the solution.
Thank you again for your help.
Aurélien
prev parent reply other threads:[~2020-02-19 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 16:56 [alsa-devel] No sound with Realtek ALC298 on a Samsung Galaxy book Aurélien Croc
2020-02-17 8:00 ` Takashi Iwai
2020-02-17 14:03 ` Aurélien Croc
2020-02-17 16:19 ` Takashi Iwai
2020-02-17 19:01 ` Aurélien Croc
2020-02-17 22:05 ` Takashi Iwai
2020-02-19 8:48 ` Kailang
2020-02-29 12:37 ` Aurélien Croc
[not found] ` <3045783.YgvgG0t98J@antimony.ap2c.org>
2020-03-02 7:00 ` Kailang
2020-02-19 9:05 ` Aurélien Croc [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=3375274.Es2tsrqsTZ@antimony.ap2c.org \
--to=aurelien@ap2c.com \
--cc=alsa-devel@alsa-project.org \
/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