X86 platform drivers
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 215993] Serial Bus Multi Instantiate driver fails to allocate SPI device CSC3551:00
Date: Mon, 11 Jul 2022 15:25:55 +0000	[thread overview]
Message-ID: <bug-215993-215701-E9BNWl4tfc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215993-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215993

--- Comment #20 from Supasak Sutha (blur.3rd@gmail.com) ---
Actually I have been try this patch 

https://lore.kernel.org/all/20220703053225.2203-1-xw897002528@gmail.com/

and get pass this line 

https://elixir.bootlin.com/linux/v5.19-rc4/source/sound/pci/hda/cs35l41_hda.c#L423

but still got error (below).

So, I revert that patch and try yours (remove those 2 lines and replace
cs35l41->index = id).

And still got same result which is:

[15.94] cs35l41-hda spi0-CSC3551:00-cs35l41-hda.1: Failed waiting for
OTP_BOOT_DONE: -110.

from 

https://elixir.bootlin.com/linux/v5.19-rc4/source/sound/pci/hda/cs35l41_hda.c#L488


**
I also inspect the out put of this line.

https://elixir.bootlin.com/linux/v5.19-rc4/source/sound/pci/hda/cs35l41_hda.c#L320

and got -22, but seem the section "no_acpi_dsd" said it's normal.

**
And I also tried this quirk and not working.

SND_PCI_QUIRK(0x1043, 0x1e02, "Asus Zenbook UX3402ZA",
ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED),

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-07-11 15:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 21:46 [Bug 215993] New: Serial Bus Multi Instantiate driver fails to allocate SPI device CSC3551:00 bugzilla-daemon
2022-07-05 17:19 ` [Bug 215993] " bugzilla-daemon
2022-07-05 17:37 ` bugzilla-daemon
2022-07-05 18:12 ` bugzilla-daemon
2022-07-07  5:39 ` bugzilla-daemon
2022-07-08  7:40 ` bugzilla-daemon
2022-07-08 10:59 ` bugzilla-daemon
2022-07-08 17:10 ` bugzilla-daemon
2022-07-08 17:58 ` bugzilla-daemon
2022-07-08 20:05 ` bugzilla-daemon
2022-07-08 20:52 ` bugzilla-daemon
2022-07-08 20:53 ` bugzilla-daemon
2022-07-08 21:58 ` bugzilla-daemon
2022-07-08 23:19 ` bugzilla-daemon
2022-07-09 16:44 ` bugzilla-daemon
2022-07-09 16:45 ` bugzilla-daemon
2022-07-09 18:01 ` bugzilla-daemon
2022-07-11 13:51 ` bugzilla-daemon
2022-07-11 13:55 ` bugzilla-daemon
2022-07-11 14:10 ` bugzilla-daemon
2022-07-11 15:25 ` bugzilla-daemon [this message]
2022-07-11 15:41 ` bugzilla-daemon
2022-07-11 18:29 ` bugzilla-daemon
2022-07-11 19:55 ` bugzilla-daemon

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=bug-215993-215701-E9BNWl4tfc@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.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