From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Dag B <dag@bakke.com>, ALSA development <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH] Enable SPDIF output on Intel Hades Canyon
Date: Mon, 23 May 2022 15:30:35 -0500 [thread overview]
Message-ID: <3526166d-15ce-5260-200e-5c1650388956@linux.intel.com> (raw)
In-Reply-To: <5d5924ee-a52a-04f0-5080-2b8d91bce5ba@bakke.com>
On 5/23/22 15:20, Dag B wrote:
> Without the attached patch, the s/pdif output on the Hades Canyon NUC
> does not work.
>
> "Well known" issue, less known fix. As far as I can tell, there is no
> risk of any averse side-effects. But a bonus fix is enabling on-wire
> headset microphone, by chaining the right 'model' choice for the hardware.
>
> If I should Cc: someone directly for this patch to be picked up, please
> let me know.
>
>
> I have been running with this patch for half a year or so.
>
> Patch passes checkpatch.pl
>
> Patch is based on what 'cyber4o' posted on the insanelymac forum [1].
> All the glory to this person, any error is likely mine.
Thanks for the patch.
You would need a Signed-off-by tag for this patch, and CC: Takashi (added)
+ [ALC700_FIXUP_NUC_SPDIF] = {
Maybe use HC_NUC, there are multiple versions of those devices?
+ .type = HDA_FIXUP_FUNC,
+ .v.func = alc700_fixup_nuc_spdif,
alc700_fixup_hc_nuc_spdif ?
+ .chained = true,
+ .chain_id = ALC269_FIXUP_DELL1_MIC_NO_PRESENCE,
that chain_id doesn't seem quite right?
>
> Some other users with issues: [2] [3]
>
>
> Dag Bakke
>
>
> [1]
> https://www.insanelymac.com/forum/topic/339291-guide-hac-mini-osx-mojave-on-intel-hades-canyon-nuc8i7hvknuc8i7hnk/page/8/
>
>
> 2] https://bbs.archlinux.org/viewtopic.php?id=270917
>
> [3]
> https://www.reddit.com/r/intelnuc/comments/9ft9x8/any_linux_users_got_the_spdif_toslink_to_work_on/
>
>
>
next prev parent reply other threads:[~2022-05-23 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 20:20 [PATCH] Enable SPDIF output on Intel Hades Canyon Dag B
2022-05-23 20:30 ` Pierre-Louis Bossart [this message]
2022-05-23 21:29 ` Dag B
2022-05-23 21:53 ` Pierre-Louis Bossart
2022-05-24 6:58 ` Dag B
2022-05-27 14:50 ` Takashi Iwai
2022-05-27 14:51 ` Takashi Iwai
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=3526166d-15ce-5260-200e-5c1650388956@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=dag@bakke.com \
--cc=tiwai@suse.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