From: Enrico Mioso <mrkiko.rs@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: hui.wang@canonical.com, alsa-devel@alsa-project.org, kailang@realtek.com
Subject: Re: Intel HDA audio on EEE PC 1101HGo
Date: Sat, 14 Jan 2017 23:43:53 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.20.1701142343340.3772@localhost.localdomain> (raw)
In-Reply-To: <s5hr346ht46.wl-tiwai@suse.de>
Thank you very much to all of you, Takashi.
Enrico Mioso
Mobile Phone Number: +393807096934 ( +Telegram :) )
My Tox ID is: 7C593F402A3C8632D87AB4B948D492294C39A6A614464ECF843CA3429FB023284180472C7475
I like / recommend the usage of open messaging standards.
On Sat, 14 Jan 2017, Takashi Iwai wrote:
> Date: Sat, 14 Jan 2017 10:46:01
> From: Takashi Iwai <tiwai@suse.de>
> To: Enrico Mioso <mrkiko.rs@gmail.com>
> Cc: hui.wang@canonical.com, alsa-devel@alsa-project.org, kailang@realtek.com
> Subject: Re: [alsa-devel] Intel HDA audio on EEE PC 1101HGo
>
> On Sat, 14 Jan 2017 10:20:16 +0100,
> Enrico Mioso wrote:
>>
>> Hello Takashi,
>> thank you very much again for your kindness and patience...
>>
>> I'll enable the tracepoint.
>> Discrepancies in the single_cmd value are derived from the fact that I am still using the hackish version of the patch, since I didn't reboot... otherwise I should have started from scratch some very-long operations.
>> But the value has remained to 0, and the fallback didn't happen, as expected.
>>
>> Ok, reading note.rst now.
>> I was wondering, but I may well be wrong: in the past that fallback code brought my system to single cmd mode after polling... Now it crashes, and as I said before, the switching from polling to last_cmd is kind-of immediate most of the times these days (e.g.: on this kernel).
>> May be something goes wrong in the fallback path? Or is this caused by an invalid verb ?
>> Guessing verb = something like a command...
>
> Yes, maybe the fallback to single cmd got broken somehow. I'd need to
> check with a fault injection.
>
> In anyway, the verb is DIGI_CONVERT_2, and the only possible place is
> the beep setup.
>
> Could you try the below to see whether it makes any difference?
>
>
> Takashi
>
> ---
> diff --git a/sound/pci/hda/hda_beep.c b/sound/pci/hda/hda_beep.c
> index c397e7da0eac..07930e69812a 100644
> --- a/sound/pci/hda/hda_beep.c
> +++ b/sound/pci/hda/hda_beep.c
> @@ -228,9 +228,11 @@ int snd_hda_attach_beep_device(struct hda_codec *codec, int nid)
> return -ENOMEM;
> snprintf(beep->phys, sizeof(beep->phys),
> "card%d/codec#%d/beep0", codec->card->number, codec->addr);
> +#if 0
> /* enable linear scale */
> snd_hda_codec_write_cache(codec, nid, 0,
> AC_VERB_SET_DIGI_CONVERT_2, 0x01);
> +#endif
>
> beep->nid = nid;
> beep->codec = codec;
>
next prev parent reply other threads:[~2017-01-14 22:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 19:40 Intel HDA audio on EEE PC 1101HGo Enrico Mioso
2015-04-08 20:25 ` Enrico Mioso
2015-04-09 15:59 ` Takashi Iwai
2015-04-09 16:02 ` Enrico Mioso
2015-04-09 20:02 ` Enrico Mioso
2015-04-11 8:13 ` Enrico Mioso
2015-04-12 6:01 ` Takashi Iwai
2015-04-13 20:25 ` Enrico Mioso
2016-11-22 13:09 ` Enrico Mioso
2016-11-22 15:55 ` Mrkiko Rs
2016-11-22 16:41 ` Enrico Mioso
2016-11-23 8:19 ` Enrico Mioso
2016-12-01 10:12 ` Takashi Iwai
2016-12-01 13:50 ` Enrico Mioso
2016-12-01 13:57 ` Takashi Iwai
2016-12-02 9:20 ` Enrico Mioso
2017-01-03 13:49 ` Enrico Mioso
2017-01-10 10:52 ` Takashi Iwai
2017-01-10 13:32 ` Enrico Mioso
2017-01-10 13:34 ` Enrico Mioso
2017-01-12 14:05 ` Enrico Mioso
2017-01-12 16:10 ` Enrico Mioso
2017-01-12 16:20 ` Takashi Iwai
2017-01-12 18:11 ` Enrico Mioso
2017-01-12 20:26 ` Enrico Mioso
2017-01-13 19:42 ` Enrico Mioso
2017-01-14 8:44 ` Takashi Iwai
2017-01-14 9:20 ` Enrico Mioso
2017-01-14 9:46 ` Takashi Iwai
2017-01-14 22:43 ` Enrico Mioso
2017-01-14 22:43 ` Enrico Mioso [this message]
2017-01-15 13:14 ` Enrico Mioso
2017-01-20 13:00 ` Enrico Mioso
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=alpine.LNX.2.20.1701142343340.3772@localhost.localdomain \
--to=mrkiko.rs@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=hui.wang@canonical.com \
--cc=kailang@realtek.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).