All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: anthony tonitch <d.tonitch@gmail.com>
Cc: "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
	MANAGEM..." <alsa-devel@alsa-project.org>
Subject: Re: No sound on gpd pocket 3
Date: Tue, 25 Jan 2022 09:41:07 -0600	[thread overview]
Message-ID: <de932fa4-516e-c7d7-c3cd-388fa199bf23@linux.intel.com> (raw)
In-Reply-To: <CAAEBy7f8z1LRr_EjRZtsFhj7c9hkfEkm+kGAw-yhCA-j0TvYOA@mail.gmail.com>



On 1/25/22 03:07, anthony tonitch wrote:
> Le lun. 24 janv. 2022 à 20:02, Pierre-Louis Bossart
> <pierre-louis.bossart@linux.intel.com> a écrit :
>> ah, now it's starting to make sense.
>>
>> I am afraid you have the ES8316 codec, or one of its variants.
>> /sys/bus/acpi/devices/ESSX8326:00/status         15
>>
>> so no you don't want to use options snd-intel-dspcfg dsp_driver=1 but
>>
>> options snd-intel-dspcfg dsp_driver=3
>>
>> The auto-detection don't work because we use a different codec HID for
>> the driver selection
>>
>>
>>         {
>>                 .flags = FLAG_SOF,
>>                 .device = 0x5a98,
>>                 .codec_hid = "ESSX8336",
>>         },
>>
>> as well as the machine driver selection
>>
>>         {
>>                 .id = "ESSX8336",
>>                 .drv_name = "sof-essx8336",
>>                 .sof_tplg_filename = "sof-glk-es8336.tplg",
>>         },
>>
>> This is really a problematic set of devices, where absolutely all
>> possible I2S links have been used, along with GPIO settings and DMICs.
>>
>> Please file a bug on https://github.com/thesofproject/linux/issues so
>> that we can keep track of this and suggest solution.
>>
>> Thanks!
> 
> I will file the bug issue later in the day but I have two question here,
> 
> 1. does the dsp_driver=3 is supposed to work then because it doesn't
> seems to ^^ maybe I did it wrong but here is the alsa info again if
> you see anything
> http://alsa-project.org/db/?f=847cdba9058170337515f57b460ed7bcae964af7
> 
> 2. Because it works for everyone else and not for me, does this mean
> the chip is different and then that I have a "faulty one"? I will
> obviously still try to make the sound work if I can but at least I can
> contact gpd hk for an explaination
> 
> Thanks a lot for your quick response!

All the solutions we suggested will not work because of a change in your
BIOS. We've only see "ESSX8336" so far and hard-coded this value, now
the BIOS writers in their infinite wisdom chose a different HID
(ESSX8326) which breaks all the existing matching.

if you can install a new kernel, please try and provide feedback on
https://github.com/thesofproject/linux/pull/3338, where I added support
for more BIOS variations of the same device. I don't have any hardware
to test so have to crowd-source the tests to the community, thanks for
your understanding if this isn't a turn-key solution.

  reply	other threads:[~2022-01-25 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 16:52 No sound on gpd pocket 3 anthony tonitch
2022-01-24 18:11 ` Pierre-Louis Bossart
     [not found]   ` <CAAEBy7exurcqZ+7Js27O7bWHsJQ9tQ_2yWXDeA3_smr5BDc5RA@mail.gmail.com>
2022-01-24 19:02     ` Pierre-Louis Bossart
2022-01-25  9:07       ` anthony tonitch
2022-01-25 15:41         ` Pierre-Louis Bossart [this message]
2022-01-25 17:12           ` anthony tonitch
2022-01-26 14:30             ` anthony tonitch

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=de932fa4-516e-c7d7-c3cd-388fa199bf23@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=d.tonitch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.